CEC Wake up Amlogic S912 device

Hi Portisch, I followed the wiki procedure but when I inserted the card and I wrote in ssh “reboot update” the device did not started. now I don’t know what to do anymore, I tried also with reset button. the boot log now is this: https://pastebin.com/zkY4vhfj ; the boot files I compiled are bootfiles.tar.gz (1.4 MB)

thank you

Insert the bootable SD card in the slot. Press and hold the reset button on the box. Plug in power connector. Hold the reset button until CE logo appears.

nothing, device led turn on but no CE logo appears.
to be sure, this is lsblk:

sdb 8:16 1 14,9G 0 disk
├─sdb1 8:17 1 512M 0 part /media/fs/COREELEC
└─sdb2 8:18 1 32M 0 part /media/fs/STORAGE
sr0 11:0 1 1024M 0 rom

and fdisk -l is:

Disk /dev/sdb: 15.9 GB, 15931539456 bytes
4 heads, 32 sectors/track, 243096 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x57a3744e
Device Boot Start End Blocks Id System
/dev/sdb1 * 8192 1056767 524288 c W95 FAT32 (LBA)
/dev/sdb2 1056768 1122303 32768 83 Linux

I wrote binary with sdb instad sdc

There is something wrong:

Rank0: 2048MB(auto)-2T-3
Rank1: 2048MB(auto)-2T-3
DataBus test pass!
GXM:BL1:dc8b51:76f1a5;FEAT:ADFD318C:80;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;0.0;CHK:0;

u-boot get loaded put it reboots after DataBus test pass
You deleted the “old” u-boot stored in NAND like here, point 2?
If yes then the u-boot get loaded from the bootable sd card. So maybe your binarys are wrong.

EDIT: your log shows a wrong ram init. I compile a new u-boot for you!
EDIT: Attached a new u-boot.
u-boot.bin.sd.bin: for the bootable sd card
u-boot.bin: for the upgrade in eMMC

thank you for the help and the new u-boot but the problem is still there.
new log GXM:BL1:dc8b51:76f1a5;FEAT:ADFD318C:80;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;REA - Pastebin.com

You deleted the “old” u-boot stored in NAND like here , point 2?
If yes then the u-boot get loaded from the bootable sd card. So maybe your binarys are wrong.
yes, I deleted and restared as point 2.
maybe there something wrong in my execution of bootable sd card? did you see my previous post?

And when you do not have any SD card inserted?
Something on the log? The last log doesn’t show any difference. I will make you tomorrow another u-boot to see if there is different log.

I used the https://libreelec.tv/2016/08/usb-sd-creator/ to create the SD. When it is finished write the u-boot.bin.sd.bin to the unmounted SD card sector 0 like in the wiki described.

Log with no card inserted: https://pastebin.com/nhB5ECXN
Log with original CoreELEC card (exactly the same loop) https://pastebin.com/Uw2Lft5a

I renew a doubt of my old post # 17. I ran, a long time ago, the procedure of this link (https://forum.libreelec.tv/thread/9425-howto-boot-from-sd-card-use-internal-memory-for-data/): may have it changed something in the partition structure that prevents booting today?
thank you again for support

This log shows u-boot get loaded from sd card. So please try the new attached binaries!
Use the new u-boot.bin.sd.bin for the bootable sd card for sektor 0.

Otherwise you can bring back the box to life with a sd card from “burn card maker” by Amlogic. If this is not working you can use the USB tool from amlogic to restore the system. But for this you will need a USB male-male type A cable.

u-boot_BT1_1.zip (1.4 MB)

Dear Portisch, it works!!! Thank you!
I did some tests:
CEC wake up: test ok (log: https://pastebin.com/wE1v5Fd7). The only problem is aesthetic: when the device starts up, the beelink logo is distorted and very ugly, can we do something to eliminate it?
Wake on LAN: test ok with both stanby and power on off and the mix.
Standby: always crashes when restarting from a stanby. These are the logs: standby command via CEC https://pastebin.com/sjkDCsb1. Awakening with crash: https://pastebin.com/1C5ebqRz

This is no crash. You just catched a Kodi bug!
I don’t know where it comes from but I do have it also.

Add a remote.xml for Kodi if you don’t have already one and add these settings:

    <keyboard>
      <key id="61662"></key>
    </keyboard>

remote.xml (18.3 KB)

This also works! problem solved.

Hello

After you replaced the u-boot, is it possible to use “Reboot from internal/MMC” in the shtudown menu to boot Android from the internal memory?
I have a Beelink GT1 Ultimate SN starting with AX12, which defconfig should I use when I compile u-boot?
I would like to have standby mode on my device and the device should wake up for scheduled recordings. Will it work after replacing u-boot?

After you replaced the u-boot, is it possible to use “Reboot from internal/MMC” in the shtudown menu to boot Android from the internal memory?

Yes

I have a Beelink GT1 Ultimate SN starting with AX12, which defconfig should I use when I compile u-boot?

This guide and the source you will compile are now also tested for your GT1. GitHub - CoreELEC/u-boot

I would like to have standby mode on my device and the device should wake up for scheduled recordings. Will it work after replacing u-boot?

Yes

Thanks for your reply.

I’ve read the guide, but I’m not sure which defconfig should I use

Choose you desired defconfig like: kvim, kvim2, kvim2l, h96proplus_v2_2, h96proplus_v5_v6, …
`make h96proplus_v2_2_defconfig

I have noticed that the dtb image is called ‘gxm_q200_3g’ and there is a defconfig named ‘gxm_q200_v1_defconfig’. Should I use that?

I tried to compile with this defconfig on Windows Subsystem for Linux (Ubuntu 18.04.2 LTS), but I get this error:
…/include/linux/compiler-gcc.h:114:1: fatal error: linux/compiler-gcc7.h: No such file or directory

after the last coreelec update i need to reactivate wake on lan on my beelink gt1. unfortunately the old uboot wiki is no longer available. could you remember the ssh command or repost the old wiki in this post?

I activated the WoL switch in the coreelec settings but unfortunately it doesn’t work.
I tried to search the forum but all posts refer to the Coreelec / u-boot github link which has changed and no longer contains the instructions to enable WoL.
Can anyone help me?

Platforms before G12A/B maybe do not support such wake-up features. It’s a 10:90% chance you get a working implementation. There is no other way then to burn another bootloader to fix these issues. But the problem is that the source isn’t available for each individual device.

So my suggestion is to upgrade the hardware to a G12A/B (S922X, S905X2) or SM1 (S905X3) device to be able to use inject BL301, if needed.

Thank you for your answare. Just to make a try do you remember the ssh command ?
And what If I came back to 9.2.2 ? With this ce version all worked perfectly thanks to the uboot you compiled for this platform last year

I am sorry, it looks like the Wiki is lost.

Really? :cry:
If the wiki is lost, how can I manage it? it seems little credible that yesterday I managed the device with wol and today not. What do you suggest?