The bootloader of your device does not contain a Suspend FW. Use the Branch libretech-cc or Amlogic and compile the uboot with the appropriate remote code. Replace the uboot binary.
Posts by bumerc
-
-
Quote
"[0x10103005] Romcode / Initialize DDR / Download buffer / Read item data failed"
Your problem starts much earlier. Apparently you are using wrong bootloader.
-
Please post original dtb file and if possible bootloader log and PCB photo.
-
Apparently the update went wrong and you deleted the bootloader. If you have a UART to USB converter then we can try to revive your box and install LE.
-
Hi "bumerc", I was browsing through the u-boot sources of this ghuba uboot-amlogic/gxm_q201_v1.h at master · Stane1983/uboot-amlogic · GitHub but how to compile it so that it's okay is not a clue. I have a request to you or if you have time, you would prepare an u-boat for me.
At the weekend, when I'm back home.
Edit: For u-boot questions please use this Thread.
-
The CEC_WAKEUP Function is hard-coded in u-boot.
You must disable this before compiling u-boot.
See Line:
Code#define CONFIG_CEC_WAKEUPin u-boot/board/amlogic/configs/gxm_q201_v1.h
Disable or remove this line and recompile u-boot.
-
in your u-boot the CEC Wake_UP is activated. There are two ways to get around this:
1. Disable HDMI-CEC Driver in Kodi settings.
2. Disable CEC Wake_up in the uboot.
-
Where exactly did you find the info? Open the case and check the CPU name. Do you have photos of the PCB?
-
Both versions freezes after some minutes running, I have no more idea and give up. Maybe something is broken and i get another device.
Yesterday I flashed two other devices with it, both work perfectly. It looks like you have a hardware error.
-
Before i do another test, is there any way to create a backup of the entire Android system including working u-boot, that i can easily flash with Burning tool? Would save much time.
Small instructions - backup with TWRP
1. Download this file (#76) and copy it to the FAT32 partition of the SD card.
2. Start your box and abort the autoboot by uart connection. (The steps have already been described here.)
3. Now load recovery.img into the RAM and then start it:
Codemmcinfo fatload mmc 0 ${loadaddr} recovery.img bootm ${loadaddr}4. TWRP Recovery menu should now appear on the display, make a backup of your system.
good luck
P.S. Whether the TWRP backup method includes the bootloader, I can not say.
Edit: Of course you can use the method with hold the reset button.
-
I do not like Android and have never been interested, sorry. Replacing the Bootloader via uart takes on average 5 minutes.
-
are this new versions and are they for my H96p+ CZ-S32-v5 ?
These can be installed on v5 and v6 boards with LPDDR3 memory and are built for testing TheChief. It brings none Advantages for you, it is that you have problems with waking up the box with the activated HDMI-CEC Driver ..?
-
-
Ok, I'm still doing a build, then it should work again. Currently I do not have a H96pp device for testing anymore
-
What can change the DTB file, if Android also crashes? Cable lenght is maybe 1 or 2 meter, gigabit connection is no problem (AVM 7490)
...
q200 and q201 dtb are different. Decompile these and just look.
-
From the uboot side it can only guess .. that this error could be caused by the switching between rmii and rgmii interface. Otherwise, I have no ideas ..
Small update
- forced rgmii mode
not tested, please try it.
-
For me the uboot fix does not work. Don't know why. My system then always crashes/hangs, but power on/off works.
You forgot to mention that it just does not work for you
. What is the length of your network cable? Does the router have 1Gbit connection, or only 100Mbit? If you have CE installed, try this dtb -
Working on my CZ-S32-v2.2 DDR3 Board
Whats the DDR4 Clocks on this uboot just out of interest
This u-boot was compiled with RAM auto-detection. This can be used for devices with DDR3 and also DDR4, if the DDR timing and clk rate allow this.
-
hi bumerc
is there a fix for this hdmi-cec jam issue..
exactly the same issue as described here.
thanks
Yes.
Either disable HDMI CEC drivers in the GUI and have this task done by the u-boot, or vice versa. Both at the same time is a bad solution. The solution with u-boot does not fit with all concepts. For the systems like CE I would simply deactivate the HDMI CEC function in the u-boot
