Wetek Play 2 can boot LE9 from SDcard without eMMC?

diagus · February 25, 2024 at 9:15 AM

Hi all.

I was using a Wetek Play 2 with internal tuner with the dtech LE 9.2.8 image installed on the emmc but it suddenly stopped booting. I think it is a hardware failure of the emmc chip.

I have tried booting from the SD card with different LE9 images with no success.
Booting from SD card with LE11 and L12 nighly images works but I can't use the internal tuner.

Is there a way to boot LE9 on WP2 from the SD card without a working emmc?

Thanks in advance.

**chewitt** · February 25, 2024 at 11:00 AM

Random guessing: image this to an SD card: https://github.com/LibreELEC/Libr…/bootloader.img

Then write the LE 9.2.8 image to a USB stick, connect both SD and USB devices, boot and see what happens. If you're lucky it will find u-boot on the SD card, boot it, and then u-boot will find the LE 9.2 image on USB and boot the LE kernel.

If that doesn't work, try the process again with https://github.com/LibreELEC/Libr…es/recovery.img written to the SD card instead.

If you can connect the serial UART cable to the board to literally 'see' the boot process it will help you (else you are blind to what actually happens). WeTek did ship one with the box.

The primary challenge you have is that S905 boards look for a signed boot header in different locations on SD/USB and eMMC boot media, hence an image of the factory Android image on eMMC (which we have) will not boot from SD as the SoC cannot find the signature. The LE 9.2.8 image does not include u-boot at all as LE relies on the factory u-boot being installed to eMMC. The LE12 image boots as this does include u-boot and the .img is specially built to have the signed boot header in both eMMC and SD/USB locations; but I doubt modern u-boot can boot the legacy images (have never tried). In theory it's possible to create your own Amlogic u-boot binary then sign it using the FIP sources in https://github.com/LibreELEC/amlo…ter/wetek-play2 .. but there's no guides for that kind of thing.

diagus · February 26, 2024 at 9:25 AM

Thanks chewitt.

I have tried both options with the same result: no boot from sdcard

Attached the serial cable, console shows a boot loop:

Code

GXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:1;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:2;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:3;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:4;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:5;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;LOOP:6;EMMC:800;NAND:81;SD:0;READ:0;CHK:F3;USB:8;

I also tried flashing your testing u-boot on sdcard (https://chewitt.libreelec.tv/testing/u-boot…bin-wetek-play2). The system boots, detect the USB but can't boot de LE 9.2.8, as expected.

Code

GXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
no sdio debug board detected
TE: 437761

BL2 Built : 09:01:42, Oct 11 2016.
gxb g88b04d6 - haixiang.bao@droid05

set vcck to 1100 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1536MHz
DDR chl: Rank0+1 diff @ 912MHz
DDR0: 1024MB(auto)-2T-13
DDR1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK.
Run bl30...
Load bl31 from SD, src: 0x00020000, des: 0x101000[00, size: 0x00018190
Image: gxb_v1.1.3135-18177fc 2016-06-24 11:00:09 yun.cai@droid06]
OPS=0x13
82 23 84 47 b5 54 7c 27 cb 26 69 12 [0.536598 Inits done]
secure task start!
high task start!
low task start!
Load bl33 from SD, src: 0x0003c000, des: 0x01000000, size: 0x0008f7a0
NOTICE:  BL3-1: v1.0(debug):bc3419d
NOTICE:  BL3-1: Built : 14:16:22, Aug 15 2016
INFO:    BL3-1: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9

<debug_uart>


U-Boot 2023.10 (Nov 25 2023 - 16:55:39 +0000) wetek-play2

Model: WeTek Play 2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (13:1)
DRAM:  1 GiB (effective 2 GiB)
Core:  163 devices, 26 uclasses, devicetree: separate
MMC:   mmc@70000: 2, mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    usbkbd,serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   Could not get PHY for ethernet@c9410000: addr -1
No ethernet found.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Card did not respond to voltage select! : -110
starting USB...
Bus usb@c9000000: USB DWC2
Bus usb@c9100000: USB DWC2
scanning bus usb@c9000000 for devices... 2 USB Device(s) found
scanning bus usb@c9100000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

Device 0: Vendor: SanDisk Rev: 1.00 Prod: Cruzer Snap
            Type: Removable Hard Disk
            Capacity: 29340.0 MB = 28.6 GB (60088320 x 512)
... is now current device
Scanning usb 0:1...
Could not get PHY for ethernet@c9410000: addr -1
Could not get PHY for ethernet@c9410000: addr -1
Could not get PHY for ethernet@c9410000: addr -1
...

Display More

**chewitt** · February 26, 2024 at 11:24 AM

The UART output at least confirms the box finds nothing to boot, which is a much better starting point for recovery activities than when u-boot is broken/half-working. And the upstream u-boot binaries in my testing share have no knowledge of boot files like kernel.img and dtb.img so it won't find and use them. However I'm wondering what happens if you simply rename stuff to files that it does know about?

For kicks, create an SD card from the LE12 image for WP2 in my testing share and delete everything except the extlinux/extlinux.conf folder/file. Then copy kernel.img file from the 9.2.8 image (rename to KERNEL) and the SYSTEM file (leave as-is) and then dtb.img (rename to meson-gxbb-wetek-play2.dtb) and see what happens when it tries to boot (share the UART output and/or dmesg should it make it that far). I'll be surprised if it works, but you have nothing to loose.

diagus · February 26, 2024 at 5:01 PM

No surprises chewitt, tested following the instructions with no success: Bad Linux ARM64 Image magic!

This is the console output (lines about PHY for ethernet removed):

Code

GXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
no sdio debug board detected
TE: 1208891

BL2 Built : 09:01:42, Oct 11 2016.
gxb g88b04d6 - haixiang.bao@droid05

set vcck to 1100 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1536MHz
DDR chl: Rank0+1 diff @ 912MHz
DDR0: 1024MB(auto)-2T-13
DDR1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK.
Run bl30...
Load bl31 from SD, src: 0x00020000, des: 0x101000[0, size: 0x00018190
Image: gxb_v1.1.3135-18177fc 2016-06-24 11:00:09 yun.cai@droid06]
OPS=0x13
82 23 84 47 b5 54 7c 27 cb 26 69 12 [1.307718 Inits done]
secure task start!
high task start!
low task start!
Load bl33 from SD, src: 0x0003c000, des: 0x01000000, size: 0x0009c550
NOTICE:  BL3-1: v1.0(debug):bc3419d
NOTICE:  BL3-1: Built : 14:16:22, Aug 15 2016
INFO:    BL3-1: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9

<debug_uart>


U-Boot 2024.01 (Feb 24 2024 - 15:14:17 +0000) wetek-play2

Model: WeTek Play 2
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (13:1)
DRAM:  1 GiB (effective 2 GiB)
Core:  170 devices, 28 uclasses, devicetree: separate
MMC:   mmc@70000: 2, mmc@72000: 0, mmc@74000: 1
Loading Environment from nowhere... OK
In:    usbkbd,serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   
No ethernet found.

Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1:      LibreELEC
Retrieving file: /KERNEL
append: boot=LABEL=LIBREELEC disk=LABEL=STORAGE quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0
Retrieving file: /meson-gxbb-wetek-play2.dtb
Bad Linux ARM64 Image magic!
EXTLINUX FAILED: continuing...
Card did not respond to voltage select! : -110
starting USB...
Bus usb@c9000000: USB DWC2
Bus usb@c9100000: USB DWC2
scanning bus usb@c9000000 for devices... 1 USB Device(s) found
scanning bus usb@c9100000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
Could not get PHY for ethernet@c9410000: addr -1
...
No ethernet found.

missing environment variable: pxeuuid

Retrieving file: /extlinux/pxelinux.cfg/00000000
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/0000000
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/000000
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/00000
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/0000
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/000
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/00
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/0
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/default-arm-meson-p200
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/default-arm-meson
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: /extlinux/pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
=>

Display More

**chewitt** · February 27, 2024 at 4:57 AM

u-boot.bin.sd.bin

This is u-boot.bin.sd.bin (u-boot for SD card boot) built from WeTek WP2 sources. It needs to be written to the SD card using the following recipe: https://github.com/LibreELEC/Libr…r/mkimage#L8-L9

diagus · February 27, 2024 at 8:34 PM

Flashed u-boot to SDcard with LE9.2.8.13.

The console output:

Code

GXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:800;NAND:81;SD:0;READ:0;CHK:0;
no sdio debug board detected
TE: 318096

BL2 Built : 09:01:42, Oct 11 2016.
gxb g88b04d6 - haixiang.bao@droid05

set vcck to 1100 mv
set vddee to 1000 mv
Board ID = 4
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 912MHz
DDR0: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010200, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK.
Run bl30...
Load bl31 from SD, src: 0x00020200, des: 0x101000[00, size: 0x00018190
Image: gxb_v1.1.3135-18177fc 2016-06-24 11:00:09 yun.cai@droid06]
OPS=0x13
82 23 84 47 b5 54 7c 27 cb 26 69 12 [0.414361 Inits done]
secure task start!
high task start!
low task start!
Load bl32 from SD, src: 0x0003c200, des: 0x05300000, size: 0x00035760
Load bl33 from SD, src: 0x00074200, des: 0x01000000, size: 0x000a7790
NOTICE:  BL3-1: v1.0(debug):bc3419d
NOTICE:  BL3-1: Built : 14:16:22, Aug 15 2016
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Initializing BL3-2
INFO:    BL3-2: ATOS-V1.5-g3e467d9 #1 Mon Aug 22 17:11:43 CST 2016 arm
INFO:    BL3-2: chip version = RevC (1F:C - 0:0)
INFO:    BL3-2: crypto engine BLKMV
INFO:    BL3-2: secure time REE
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address = 0x1000000
INFO:    BL3-1: Next image spsr = 0x3c9


U-Boot 2015.01-g4c46c50-dirty (Dec 29 2019 - 07:22:01)

DRAM:  1 GiB
Relocation Offset is: 36ecb000
register usb cfg[0][1] = 0000000037f60920
register usb cfg[0][2] = 0000000037f60940
register usb cfg[2][0] = 0000000037f60960
[CANVAS]canvas init
vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters
vpu: clk_level = 7
vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300)
boot_device_flag : 1
Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
init bus_cycle=6, bus_timing=7, system=5.0ns
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
MMC:   aml_priv->desc_buf = 0x0000000033ecb770
aml_priv->desc_buf = 0x0000000033ecda90
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
emmc/sd response timeout, cmd1, status=0x3ff2800
MMC init failed
Using default environment

In:    serial
Out:   serial
Err:   serial
reboot_mode=cold_boot
hpd_state=0
cvbs performance type = 4, table = 0
[store]To run cmd[emmc dtb_read 0x1000000 0x40000]
read emmc dtb
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
emmc/sd response timeout, cmd1, status=0x3ff2800
mmc init failed
      Amlogic multi-dtb tool
      Cannot find legal dtb!
[store]Err:do_store_dtb_ops,L236:Fail in fdt check header
board_late_init(): [store dtb read $dtb_mem_addr] fail
load dtb to 1000000
[store]To run cmd[emmc dtb_read 1000000 0x40000]
read emmc dtb
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
emmc/sd response timeout, cmd1, status=0x3ff2800
mmc init failed
      Amlogic multi-dtb tool
      Cannot find legal dtb!
[store]Err:do_store_dtb_ops,L236:Fail in fdt check header
board_late_init(): store dtb read 1000000 fail
ret = 1 .[mmc_init] mmc init success
Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SC32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
Net:   Phy 0 not found
dwmac.c9410000
iubootVersion  = 1,pubootVersion = 1
uboot version is not the same, need to do defenv
## defenv_reserve
Saving Environment to aml-storage...
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
emmc/sd response timeout, cmd1, status=0x3ff2800
MMC init failed
wipe_data=successful
wipe_cache=successful
upgrade_step=0
## Error: "bootmode_check" not defined
Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SC32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
reading kernel.img
10379264 bytes read in 570 ms (17.4 MiB/s)
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters
[OSD]fb_addr for logo: 0x3d800000
[CANVAS]addr=0x3d800000 width=3840, height=2160
Cannot find dev.
amlmmc cmd <NULL> failed

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data:
        erase the area which is uboot or data
store erase partition <partition_name>:
        erase the area which partition in u-boot
store erase dtb
store erase key
store disprotect key
store rom_protect on/off
store scrub off|partition size
        scrub the area from offset and size
store dtb iread/read/write addr <size>
        read/write dtb, size is optional
store key read/write addr <size>
        read/write key, size is optional

cmd store failed
Err imgread(L333):Fail to read 0x2000B from part[logo] at offset 0
There is no valid bmp file at the given address
[KM]Error:f[keymanage_dts_parse]L282:not a fdt at 0x0000000001000000
gpio: pin GPIOAO_3 (gpio 122) value is 1
get_cpu_id flag_12bit=0
saradc - saradc sub-system

Usage:
saradc saradc open <channel>            - open a SARADC channel
saradc close    - close the SARADC
saradc getval   - get the value in current channel
saradc get_in_range <min> <max> - return 0 if current value in the range of current channel

get_rebootmode = cold_boot
InUsbBurn
noSof
Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SC32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
reading kernel.img
10379264 bytes read in 570 ms (17.4 MiB/s)
key1 = ef18877
key2 = ef18877
time_out = 4c4b40
ir init
irkey - irkey key_value1 key_value2 time_value

Usage:
irkey
no_power_key_press
Hit any key to stop autoboot:  1                                              0
reading boot.ini
** Unable to read file boot.ini **
cfgload: no boot.ini or empty file
Cannot find dev.
amlmmc cmd <NULL> failed

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data:
        erase the area which is uboot or data
store erase partition <partition_name>:
        erase the area which partition in u-boot
store erase dtb
store erase key
store disprotect key
store rom_protect on/off
store scrub off|partition size
        scrub the area from offset and size
store dtb iread/read/write addr <size>
        read/write dtb, size is optional
store key read/write addr <size>
        read/write key, size is optional

cmd store failed
Err imgread(L132):Fail to read 0x100000B from part[boot] at offset 0
InUsbBurn
noSof
Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SC32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SC32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
reading aml_autoscript
** Unable to read file aml_autoscript **
reading recovery.img
** Unable to read file recovery.img **
(Re)start USB...
USB0:   dwc_usb driver version: 2.94 6-June-2012
USB (0) peri reg base: c0000000
USB (0) use clock source: XTAL input, div: 1
USB (0) base addr: 0xc9000000
Force id mode: Host
dwc_otg: No USB device found !
lowlevel init failed
USB1:   dwc_usb driver version: 2.94 6-June-2012
USB (1) peri reg base: c0000020
USB (1) use clock source: XTAL input, div: 1
USB (1) base addr: 0xc9100000
Force id mode: Host
dwc_otg: Highspeed device found !

scanning bus 1 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
Cannot find dev.
amlmmc cmd <NULL> failed

store - STORE sub-system

Usage:
store store init flag
store read name addr off|partition size
    read 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store write name addr off|partition size
    write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
store rom_write add off size.
        write uboot to the boot device
store erase boot/data:
        erase the area which is uboot or data
store erase partition <partition_name>:
        erase the area which partition in u-boot
store erase dtb
store erase key
store disprotect key
store rom_protect on/off
store scrub off|partition size
        scrub the area from offset and size
store dtb iread/read/write addr <size>
        read/write dtb, size is optional
store key read/write addr <size>
        read/write key, size is optional

cmd store failed
Err imgread(L132):Fail to read 0x100000B from part[recovery] at offset 0
wetek_hub#

Display More

**chewitt** · February 28, 2024 at 10:46 AM

The last line contains the clue .. that's the Hub u-boot binary not the WP2 one. I'll see if I can regenerate the WP2 one (needs some setup as those files were last built on some other machine).

diagus · March 2, 2024 at 9:26 AM

Quote from chewitt

The last line contains the clue .. that's the Hub u-boot binary not the WP2 one. I'll see if I can regenerate the WP2 one (needs some setup as those files were last built on some other machine).

I would appreciate if you can do it to test if could boot LE9 from SD.

Watching TV on the WP2 with LE11 and an external USB DVB stick is painful, after a few minutes the artifacts begin and tvheadend shows a lot of continuity counter errors, making it unusable.

Perhaps the best solution is to buy new hardware.

ricopt5 · March 12, 2024 at 12:45 PM

diagus

Here's a Play 2 u-boot that will boot by default from sd card (unless you press the remote power button, in which case it will try to boot from eMMC, which in your case and mine, doesn't work).
Just write is to the sdcard where you have LE9 and it should work.

Just one note, the screen will be black for a few seconds on bootup in case u-boot cannot find the boot splash image in eMMC

u-boot.bin.sd.bin

diagus · March 14, 2024 at 4:39 PM

Quote from ricopt5

diagus

Here's a Play 2 u-boot that will boot by default from sd card (unless you press the remote power button, in which case it will try to boot from eMMC, which in your case and mine, doesn't work).
Just write is to the sdcard where you have LE9 and it should work.

Just one note, the screen will be black for a few seconds on bootup in case u-boot cannot find the boot splash image in eMMC

u-boot.bin.sd.bin

Display More

Thank you very much ricopt5. It works!!! My WP2 boots LE9 form sdcard.