Did you write the u-boot.bin.sd.bin to the secondary SD card and put it in the box before deleting the old bootloader and system reboot? Can you do a boot log? One of the Freaktab users wrote that his minix box works with the custom Android ROM. (Apparently the original bootloader was used).
I changed the “shutdown.sh” of “TVHeadend/PVR Recording & Power Manager”:
Calculate wake up time:
startdate=$1
aktdate=date +%s
delta=$((($startdate-$aktdate)*10))
Replace all RTC device accesses with:
devmem 0xc81000a8 32 $delta
This works fine if power off with remote, but not with timer end. This I have to check with add on.
Thanks a lot to Portisch for the fine patches and very useful information.
Hello,
at U-Boot I found this code:
if (irq[IRQ_ETH_PHY] == IRQ_ETH_PHY_NUM) { irq[IRQ_ETH_PHY] = 0xFFFFFFFF; exit_reason = ETH_PHY_WAKEUP; }
Is there any way to “Wake on LAN”?
Thanks
There is a Kodi addon called advanced wake on LAN
I use a phone app.
Obviously, WOL won’t work with wifi
I never tested it. But the feature is included…
Thanks @Portisch @bumerc. I finally could write u-boot into eMMC Minix U9-H with succes!!! and it is working perfectly! i can wake up minix with HDMI CEC and now in suspend mode all other HDMI CEC Devices are visible for TV!!
Great work!
I followed @Portisch guide in wiki (but modifiing one Command, (to delete actual u-boot this is the command * delete currently used u-boot: dd if=/dev/zero of=/dev/bootloader
) After delete u-boot, with a sd-card inserten, i rebooted the device with this command reboot update
. I could boot into sdcard mode and write again u-boot into emmc following wiki guide!
Thanks again!
This add on seems to wake on an other machine, e.g. NAS. Is it also useful to wake up the Kodi machine itself where it is installed?
Is there a special U-Boot environment necessary? “wakeonlan” with the MAC stored in U-Boot env. shows no effect.
Thanks for any advice
probably not. I got a wake on lan app for my phone, which could wake up a device
I found this here:
"wol_init="\ "kbi init;"\ "kbi powerstate;"\ "kbi trigger wol r;"\ "setenv bootargs ${bootargs} wol_enable=${wol_enable};"\ "if test ${power_state} = 1; then "\ "kbi trigger wol w 1;"\ "gpio set GPIODV_2;"\ "fi;"\ "\0"\
“run wol_init;”
So try to add these commands in the board config header file like it is in kvim2.h.
I did not tested it.
Hello,
I have my H96 Pro+ from Banggood (mainboard: ZH01-S912-TVBOX-V3.0). It is green with the specs 3gb+32gb. I have Coreelec on a seperate sdcard. The problem: Suspend dont work and when I shut down the box, I can only start it again by unplugging and plugging in the power supply. Now I have become aware of the uboot files from @Portisch. I used the wiki tutorial to install it.
Modifying the sdcard seems to work fine, but as soon as I delete the existing bootloader with ssh, dd gets an error:
dd: writing to `/dev/disk2': No space left on device
I ignored the mistake and restarted the box of good will. But now the box doesn’t give a signal anymore and the LED lights up blue permanently. So I have read the logs via ttl:
TE: 224953
BL2 Built : 16:32:58, Nov 3 2017.
gxl gb5491d8 - xiaobo.gu@droid12
set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 3
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 2048MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;0.0;CHK:0;
The log keeps repeating itself.
Maybe someone has an idea what the problem is. Thanks in advance!
There is the u-boot missing. Continue here:
-> Reboot to the bootable micro SD card by one of this method:
-> use method 1
Be sure your sd card is bootable:
Thanks for the answer! I took a new micro SDcard and followed the instructions (with Debian). There were no errors in the creation like with the previous ones. (I also changed the dtb.img file (I tested: gxm_q200_3g.img
and gxm_q201_3g_1gbit.img
)).
Nevertheless nothing has changed. The LED is permanently blue and I don’t get a signal via hdmi. I press and hold the reset button before connecting the power supply. How long do you have to wait until the coreelec logo comes? (I have waited up to 2min).
The log hasn’t changed either.
I hope you have another idea what I’m doing wrong.
You see on the UART live log when the booting of the SD card is starting. If this is not starting you don’t have U-Boot.bin.sd.bin in sector 0 of the SD card.
I don’t fully understand the log. But does the reading process start on this line, right?:
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
After that, the log starts all over again.
However, I don’t understand what I’m doing wrong about creating the sd card. Can this be a hardware problem with the micro sd adapter or is it due to the microsd itself?
Is there another way to write sector 0 without dd?
Check this how it should look like.
Thanks a lot for your answer.
Which TV box HW you are using?
This seems to be very specific to Khadas VIM2 HW. If I look to the schematics there are a Realtek PHY and something like a PIC. I have doubts this is also available with H96 Pro+
Thanks a lot for the info
Knut
Actually, just realised, I wake my nas from the app
Thanks for your help @Portisch!
I have now managed to get u-boot to load:
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl33 from SD, src: 0x00050200, des: 0x01000000, size: 0x00065c00
NOTICE: BL3-1: v1.0(release):35dd647
NOTICE: BL3-1: Built : 15:20:30, Feb 7 2018
Then nothing happens anymore.
Nevertheless the box has its phases. Sometimes it starts u-boot without problems one after the other. Sometimes, however, it starts only after multiple replugging of the power supply. By the way, it is completely irrelevant if I hold down the reset button or not at all.
Either way, it still didn’t bring me to the result: CoreELEC starts.
Everything stays the same, no matter if u-boot starts or not:
-blue LED
-no HDMI signal
By the way, I’m using your compiled u-boot files. Could that be a problem?
Wait, I take a look to my crystal ball… hmmm - I don’t see any log file…
- CL13 seems to be too much for the PE037-125. This RAM memory type requires/runs well with a CL value of 11. The Clk. Rate has to be lowered to 792Mhz (~ 800). You need another u-boot binary.
- The power supply may also be faulty.