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 ..?
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.
I do not like Android and have never been interested, sorry. Replacing the Bootloader via uart takes on average 5 minutes.
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:
mmcinfo
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.
TWRP already running on my box. Will try to make a backup there. Didnt think on that. Thanks.
Both versions freezes after some minutes running, I have no more idea and give up. Maybe something is broken and i get another device.
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.
That could be. I just wonder, that the original bootloader works with no problem. I try to get another device.
For everybody what is using the H96Pro+ box:
Release u-boot for H96Pro+ boards · Portisch/u-boot · GitHub
Hi.
I'm very intersting to solve HDMI CEC problem also in Minix U9-H reported in this forum Kodi steals CEC device source when powering off. i think that the minix bug is the same than is solved in posted u-boot.
It is possible to adapt this u-boot to run in Minix U9-H?
What dtb file you are using?
EDIT: Google told me it is a gxm_q200 box.
So the U-Boot.bin should work already. The Android image not - for sure. You can use the CustomizeTool from Amlogic to exchange the U-Boot in your stock ROM. And then use BurncardManager.
But do it by your own risk!
In this thread there are the description how to flash the new u-boot using two SD cards and/or the method by the CustomizeTool.
Thanks for your suggestion.
But I think that ddr timings are different from your uboot.
In other hand, I also use dtb specific for minix u9 release but wrxtasy. It is based on gxm_q200.
If I flash wrong uboot, it is possible an easily recover of box?
Thanks
Make a log of the u-boot what is used right now. For this you will need have access to the uart of the box.
Recovery/flashing:
Hi.
Thanks. I'm trying to read u-boot log but I only get this message. What's wrong? I have CoreELEC installed.
balbes150 wrxtasy Can u help with this issue? Thanks
Regards.
--------------APROM-------------------
CPU @ 12000000Hz
Enter GET_ADC_DATE_PRO
GET_ADC_DATE_PRO : g_dataFlashAddr uData=0,date1_addr uData1= -1,Userdata_rtc_addr RTC_uData = 0
ADC_DATA1 = 0x18e
ADC_DATA2 = 0x18e
ADC_DATA3 = 0x18e
ADC_DATA4 = 0x18e
ADC_DATA5 = 0x18e
ADC_DATA6 = 0x18e
check power<=5v and (uData == 0)||(uData == -1) !(uData1 ==1 ) APROM ls clean don't power on
g_apromSize = 16384,g_dataFlashAddr=15872,g_dataFlashSize=512,date1_addr=15904,Userdata_rtc_addr=15936
Userdata_rtc_addr RTC_uData_pro= 0
----SYSTEM POWER ON----
POWER ON OF KEY BY P3.0 Hey there,
I tried to fix my u-Boot wit this guide: Remote power trouble
Unfortunatelly I cant boot from the uboot-recovery-sd with this error:
GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;REA D:0;0.0;CHK:0;
no sdio debug board detected
TE: 273123
BL2 Built : 13:27:37, Oct 25 2017. gxl g56b77aa - xiaobo.gu@droid12
set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 1
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
LPDDR3 chl: Rank0+1 @ 792MHz
Trxining Err PGSR0: 0xb18011bf.Retry...
DX0GSR0: 0x00bb2f20....
DX1GSR0: 0x00be2fa0....
DX2GSR0: 0x00bd2f20....
DX3GSR0: 0x00c03020....
DX0GSR2: 0x2f000001....
DX1GSR2: 0x2f800001....
DX2GSR2: 0x2f000001....
DX3GSR2: 0x30000001....
DX0GSR3: 0x00000000....
DX1GSR3: 0x00000000....
DX2GSR3: 0x00000000....
DX3GSR3: 0x00000000....
Trxining Err PGSR0: 0xb18011bf.Retry...
DX0GSR0: 0x00bb2f20....
DX1GSR0: 0x00be2fa0....
DX2GSR0: 0x00bd2f20....
DX3GSR0: 0x00bc2f20....
DX0GSR2: 0x2f000001....
DX1GSR2: 0x2f800001....
DX2GSR2: 0x2f000001....
DX3GSR2: 0x2f000001....
DX0GSR3: 0x00000000....
DX1GSR3: 0x00000000....
DX2GSR3: 0x00000000....
DX3GSR3: 0x00000000....
......As far as I understand it, the u-boot might use the wrong RAM-timing, right? Any suggestions how to fix it?
Thanks in advance!
Toxic
What PCB version you have? Blue v5 or v6?
I got some information from bumerc how to fix this.
Please try this u-boot:
@all:
Just create yourself a bootable SD card to test the u-boot before flashing:
I have done it this way:
sudo dd if=u-boot.bin.sd.bin of=/dev/sdb conv=fsync,notrunc bs=1 count=444
sudo dd if=u-boot.bin.sd.bin of=/dev/sdb conv=fsync,notrunc bs=512 skip=1 seek=1Hey Portisch,
Thank you very much! I fixed it with your "standard-fixed-uboot". I had to understand that the uboot-file is not loaded from the sd (so not the FILE u-boot.bin) but from sector 0 on the sd. after dd-ing the ...sd.bin on the sd it booted rightaway and I burned the u-boot.bin (from you) to the flash as discribed in the post from BUMERC
Is the new U-Boot you provided above any better?
The PCB was green and the lable said "CZ | 2G - 16G | 9377" (from memory since my case is already closed)! 
So thanks again, now I will test the Poweron-Issue! 
Toxic
Hey Portisch,
Please tell me where in your source is a line or file that responsible for the on / off button code, led indication and ddr4 memory frequency.
I want to configure the bootloader for my H96Pro+ 3/32 with a board DDR4 v0.2.
