Bricked Wetek Hub ... now what

thegooddoctor · July 31, 2023 at 1:29 AM

Wetek Hub was running 8.2.5 (aarch) and I attempted an update to 11.0.3.

Using this information here https://wiki.libreelec.tv/hardware/amlogic/wetek-hub-play2 as my guide, I did the following.
-downloaded LibreELEC-AMLGX.arm-11.0.1-box.img and transferred the image to a microsd card via Rufus

-the editing of the uEnv.ini file caused the microsd card to boot then hang at the Wetek boot screen

-took the meson-gxbb-wetek-hub.dtb and renamed it to dtb.img and moved it to the root of the filesystem and rebooted and this worked

then still following the directions

-enabled SSH, and SSH'd into the wetek

-ran these commands

cd /storage

wget https://releases.libreelec.tv/LibreELEC-AMLG…etek-hub.img.gz

emmctool w LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img.gz

-i'll paste the output below
-shutdown the wetek using the remote

-removed the microsd card

-plugged in the wetek and NOTHING ... just blue light with black screen; no DHCP entries on my router ... just nothing

-rebooting again results in the same outcome (bricked).

Solutions anyone?

Many thanks in advance.

Code

C:\Users\Admin\Desktop>ssh root@192.168.0.210
The authenticity of host '192.168.0.210 (192.168.0.210)' can't be established.
ECDSA key fingerprint is SHA256:
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.0.210' (ECDSA) to the list of known hosts.
root@192.168.0.210's password:
##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################


LibreELEC (official): 11.0.1 (AMLGX.arm)
LibreELEC:~ # cd /storage
LibreELEC:~ # wget https://releases.libreelec.tv/LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img.gz
Connecting to releases.libreelec.tv (164.92.230.217:443)
Connecting to ftp.acc.umu.se (194.71.11.163:443)
Connecting to gemmei.ftp.acc.umu.se (194.71.11.137:443)
saving to 'LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img.gz'
LibreELEC-AMLGX.arm- 100% |************************************************************************|  121M  0:00:00 ETA
'LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img.gz' saved
LibreELEC:~ # emmctool w LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img.gz
info: writing LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img.gz to /dev/mmcblk1
0+14777 records in
0+14777 records out
575668224 bytes (549.0MB) copied, 70.485111 seconds, 7.8MB/s
info: resizing partition /dev/mmcblk1p2 to 100%
Warning: Partition /dev/mmcblk1p2 is being used. Are you sure you want to continue?
Warning: Partition /dev/mmcblk1p2 is being used. Are you sure you want to continue?
info: unmounting /dev/mmcblk1p2
info: unmounting /dev/mmcblk1p1
info: checking filesystem
e2fsck 1.46.6 (1-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
STORAGE: 12/8192 files (0.0% non-contiguous), 6938/32768 blocks
info: resizing filesystem
resize2fs 1.46.6 (1-Feb-2023)
The filesystem is already 32768 (1k) blocks long.  Nothing to do!


info: remounting /dev/mmcblk1p2 to /var/media/STORAGE
Model: MMC 8WPD3R (sd/mmc)
Disk /dev/mmcblk1: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:


Number  Start   End    Size    Type     File system  Flags
1      4194kB  541MB  537MB   primary  fat16        boot, lba
2      541MB   575MB  33.6MB  primary  ext4


info: using boot=LABEL=BOOT and disk=LABEL=DISK
info: unmounting /dev/mmcblk1p2
info: changing label values on partitions
info: remounting /dev/mmcblk1p1 to /var/media/BOOT
info: remounting /dev/mmcblk1p2 to /var/media/DISK
info: changing label values in extlinux.conf


/dev/mmcblk1p1: SEC_TYPE="msdos" LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="1507-4017" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="a3d75ebf-01"
/dev/mmcblk1p2: LABEL="DISK" UUID="f426ba96-ae14-42f3-8d9f-269a100f407b" BLOCK_SIZE="1024" TYPE="ext4" PARTUUID="a3d75ebf-02"


LABEL LibreELEC
LINUX /KERNEL
FDT /meson-gxbb-wetek-hub.dtb
APPEND boot=LABEL=BOOT disk=LABEL=DISK quiet systemd.debug_shell=ttyAML0 console=ttyAML0,115200n8 console=tty0


LibreELEC:~ #
Broadcast message from root@LibreELEC (Mon 2023-07-31 00:10:01 UTC):


The system will power off now!

Display More

thegooddoctor · July 31, 2023 at 2:30 AM

tried booting microsd from these images with no success (no changes on the screen - no boot logo ... nothing)

LibreELEC-AMLGX.arm-11.0.1-box.img (with dtb.img at root)
LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img

saw this thread
Wetek Hub semi-bricked, NAND wiped but now I need correct .IMG file to restore via aml_usb_burn_tool V2

copied the 3 files to a fat32 (then fat16) microsd card and with the wetwk hub off, press the recessed UPGRADE button, plugged in the power, and held the button for 8 seconds then released ... with no change still

it looks like I'm on #3 of the referenced thread by Chewitt where

"If eMMC is not wiped but vendor u-boot cannot recover things (is broken some way) the worst case scenario is to open up the box (screws are behind the foot pads) and short pins on the emmc chip to disable it. This prevents vendor u-boot (or whatever remains of it) from interfering in boot and effectively forces SD or USB boot; so you can use the AMLGX image I linked above. It works but most users feel uncomfortable about sticking screwdrivers on memory chips to short pins and it's best done with UART access so you can see what's happening.

In all cases, having the UART cable that WeTek shipped in the box connected so you can see what's actually happening and/or where things are failing is always a good move."

Does anyone have a UART cable pinout that I could reference?

ok ... found this

Wetek Play 2 RS 232 Cable Pinouts

Here are the RS232 cable Pinouts for wetek Play 2 ..it works with many other Boxes tested it with KOQkit K1 mini [ATTACH] [ATTACH]

jb8a8f8.com

thegooddoctor · July 31, 2023 at 3:20 AM

Verify pinout --- above images are correct

I have my UART cable

thegooddoctor · 2023-07-30 21 10 47.png

115200 8n1 off off was some settings that I saw for a similar chipset

unfortunately this is my output

(see image)

edit: tried a bunch of different settings; switched RX and TX (reduced output); and even another UART device,
checked my wires for connectivity and shorts (all good); went to manufacturer's website to download new drivers ... no change

any ideas?

**dtech** · July 31, 2023 at 7:15 AM

Quote from thegooddoctor

took the meson-gxbb-wetek-hub.dtb and renamed it to dtb.img and moved it to the root of the filesystem and rebooted and this worked

^ This step was completely unnecessary. With the mainline kernel-based versions, you no longer need to rename anything.

Anyway, that's not what's causing your problem...

Quote from thegooddoctor

Verify pinout --- above images are correct
I have my UART cable

The factory UART cable uses a 4-pin Jack. Although I suddenly don't remember the wiring, I also have a DIY version that I built.

But if you need it, I can measure the correct wiring when I'm home.

By the way, the WP2 uses a 2.5 mm jack, which is not compatible just because of its size.

Quote from thegooddoctor

edit: tried a bunch of different settings; switched RX and TX (reduced output); and even another UART device,
checked my wires for connectivity and shorts (all good); went to manufacturer's website to download new drivers ... no change

It's not a TTL-level thing, so it has to be connected directly to a serial port with a DB9 connector. Do not use an RS232-TTL converter.

Regardless, under LE11 the UART doesn't work on the Hub for some reason. I also only get static noise, and if the serial cable is plugged in, the image does not start. However, under LE 9.2 I can see everything on UART perfectly.

So, if you're testing an LE11 image, please don't use UART, the Jack connector should be empty.

Questions:

Does the Hub logo appear on startup?
If you put the SD card back in does it boot?

**chewitt** · July 31, 2023 at 9:29 AM

I'm wondering if this is the "disturbed dry solder joints cause UART noise that u-boot interprets as keyboard input" problem I've seen on my own Hub; and has been reported here in the forum with at least one other user. The (fake) keyboard input interrupts boot and drops you into the u-boot local console. If a UART cable is connected and working (which can be a challenge due to the same dry joints) it's fairly obvious when this happens. If no working UART connected the box didn't reach the point where kernel/initramfs (which loads the LE boot splash) was booted so nothing appears on screen .. hence users claim the device is bricked etc.

For the record: I've seen some Amlogic devices with boot states that were challenging to recover from but I've never encountered a device that was truly bricked. And since we (me) have working u-boot for the box, recovery is possible.

The first step is really to get normal UART output to see what happened. Again, if the UART socket joints are dry that might require cable wiggling, patience, and many attempts.

**dtech** · July 31, 2023 at 11:07 AM

chewitt

IIRC that the UART on my Hub still works during uboot loading, and it only starts producing random output when the kernel is loaded.

But I'll check in the afternoon because I'm not sure I remember correctly.

thegooddoctor

Maybe the standard 3-pin ("stereo") 3.5 mm Jack will also be good, because the inner ring on the sleeve side is not connected anywhere:

Edit: Confirmed, so it works with the 3-pin Jack, and there produces UART output with the LE v11.0.3 box image.

A simple 3.5 mm to 2.5 mm Jack adapter was used with Play's factory RS232 cable:

However, something is wrong with the Hub image, because it refuses to boot for me either.

thegooddoctor · August 1, 2023 at 3:24 AM

Quote from dtech

Questions:
Does the Hub logo appear on startup?
If you put the SD card back in does it boot?

No Hub/Wetek logo; does not boot with SD card (unresponsive black screen)

Thanks everyone for the great info!!!
I have ordered a DB9 serial connector and will wire it according to the specification and see what the output states.

Since UART does not work on LE11, should I stay with LE10?

**dtech** · August 1, 2023 at 5:37 AM

Quote from thegooddoctor

Since UART does not work on LE11, should I stay with LE10?

It also works under LE11:

Quote from dtech

Confirmed, so it works with the 3-pin Jack, and there produces UART output with the LE v11.0.3 box image.

I probably confused it with another box.

thegooddoctor · August 5, 2023 at 4:19 AM

Yes, the three pin output works with UART (plugged into pins 2,3,5 on the serial port; GND to GND; TX to RX, and RX to TX; 115200 8n1 off off).

Here is the output. At the end I still had a viable prompt.

Code

GXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
no sdio debug board detected
TE: 131411

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 = 1
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 912MHz
DDR0: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK.
Run bl30...
Load bl31 from eMMC, src: 0x00020000, des: 0x10100[00, size: 0x00018190
Image: gxb_v1.1.3135-18177fc 2016-06-24 11:00:09 yun.cai@droid06]
OPS=0x13
43 40 9f e0 a5 56 b9 1f 31 54 6 bf [0.216532 Inits done]
secure task start!
high task start!
low task start!
Load bl33 from eMMC, src: 0x0003c000, des: 0x01000000, size: 0x0008ecf0
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 2022.10 (Jul 15 2023 - 10:05:02 +0000) wetek-hub

Model: WeTek Hub
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (13:1)
DRAM:  1 GiB
Core:  161 devices, 25 uclasses, devicetree: separate
MMC:   mmc@70000: 0, mmc@72000: 1, mmc@74000: 2
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
=> _<INTERRUPT>
=>

(it hung here; then when I pressed Ctrl-C to copy this output the following output was received)


=> GXBB:BL1:08af:a89;FEATDF18;POC;RCY:0;MC;READ;CHK0;
Unknown command 'GXBB:BL1:08af:a89' - try 'help'
Unknown command 'FEATDF18' - try 'help'
Unknown command 'POC' - try 'help'
Unknown command 'RCY:0' - try 'help'
Unknown command 'MC' - try 'help'
▒oknown command 'CHK0' - try 'help'
                                   => o e@``lmrc:0`x0, p40fi@ d `B,x000x sx460`.. .. ,.( l,▒30m eMe: d:mage6f 0@6],
Unknown command 'o' - try 'help'
=> O 2▒ts done
Unknown command 'O' - try 'help'
=> securetask oadl33 fom eC, s: 0x3c000es: 01000, ze0x00▒0
Unknown command 'secureta▒▒j▒▒▒'help'
▒▒j▒▒▒'help' 0:22, tg5 204NF  BL-1: itialing rtimservi▒▒5)U▒▒▒▒ݹ▒▒▒▒▒▒▒▒▒▒9=Q
=> WAG: Nn T ror itializinruntime svice oeed_fast
Unknown command 'WAG:' - try 'help'
=> I@`world
Unknown command 'I@`world' -▒▒▒ 'help'
=> I:  1: d= 0`rt>
Unknown command 'I:' - try 'help'
=> vek-hub
Unknown command 'vek-hub' - try 'help'
=>  WeTisio▒ 1f:c3:1)DRM   i
Unknon command 'WeTision' - try 'help'
=> Cr:11`LM mm70000" -m@72001, m@700: Loding Enronment fronowhere..
> In: ialut: ▒rial
> serial
> Btee sie: 0H:  `0: ernet@c1000
> n ey t stoautoboot:  => _<INTP>
> =>

Display More

thegooddoctor · August 5, 2023 at 5:11 AM

well this is interesting ... after reading the 'help' output, I typed 'boot' and got this

it looks like it booted off of the internal storage ~~sd card~~; libreelec 11.0.1

i'll try to flash the nand

Code

=> boot
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1: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-hub.dtb
## Booting kernel from Legacy Image at 08080000 ...
   Image Name:
   Image Type:   AArch64 Linux Kernel Image (lzo compressed)
   Data Size:    11569379 Bytes = 11 MiB
   Load Address: 01c80000
   Entry Point:  01c80000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 08008000
   Booting using the fdt blob at 0x8008000
   Uncompressing Kernel Image
   Loading Device Tree to 000000003bf51000, end 000000003bf5d2a3 ... OK

Starting kernel ...

[    0.000000] OF: reserved mem: failed to allocate memory for node 'linux,cma': size 896 MiB
[BL31]: tee size: 0
LibreELEC:/ # ls
bin      etc      lib      proc     sbin     sys      usr
dev      flash    media    run      storage  tmp      var
LibreELEC:/ # [   33.794393] reboot: Restarting system
INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON
bl31 reboot reason: 0xd
bl31 reboot reason: 0x0
system cmd  1.
ERROR:   gxbb System R▒GXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
no sdio debug board detected
TE: 112172

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 = 1
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 912MHz
DDR0: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK.
Run bl30...
Load bl31 from eMMC, src: 0x00020000, des: 0x1010[000, size: 0x00018190
Image: gxb_v1.1.3135-18177fc 2016-06-24 11:00:09 yun.cai@droid06]
OPS=0x13
43 40 9f e0 a5 56 b9 1f 31 54 6 bf [0.197291 Inits done]
secure task start!
high task start!
low task start!
Load bl33 from eMMC, src: 0x0003c000, des: 0x01000000, size: 0x0008ecf0
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 2022.10 (Jul 15 2023 - 10:05:02 +0000) wetek-hub

Model: WeTek Hub
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (13:1)
DRAM:  1 GiB
Core:  161 devices, 25 uclasses, devicetree: separate
MMC:   mmc@70000: 0, mmc@72000: 1, mmc@74000: 2
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1: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-hub.dtb
## Booting kernel from Legacy Image at 08080000 ...
   Image Name:
   Image Type:   AArch64 Linux Kernel Image (lzo compressed)
   Data Size:    11569379 Bytes = 11 MiB
   Load Address: 01c80000
   Entry Point:  01c80000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 08008000
   Booting using the fdt blob at 0x8008000
   Uncompressing Kernel Image
   Loading Device Tree to 000000003bf51000, end 000000003bf5d2a3 ... OK

Starting kernel ...

[    0.000000] OF: reserved mem: failed to allocate memory for node 'linux,cma': size 896 MiB
[BL31]: tee size: 0
LibreELEC:/ # [BL31]: tee size: 0
[BL31]: tee size: 0

LibreELEC:/ #

Display More

thegooddoctor · August 5, 2023 at 6:04 AM

ok --- it boots to the nand, and there are some errors.

why does it have that interrupt and stops the boot process?

how do I (in u-boot) use the usbboot command to boot from a usb device so I can attempt to flash the nand again?

ran 'reset' in u-boot; here is the output

Code

=> reset
resetting ...
INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State OFF
INFO:      AffInst: Level 0, MPID 0x2, State OFF
INFO:      AffInst: Level 0, MPID 0x3, State OFF
bl31 reboot reason: 0xd
bl31 reboot reason: 0x0
system cmd  1.
ERROR:   gxbb System RGXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:0;RE                    AD:0;CHK:0;
no sdio debug board detected
TE: 125210

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 = 1
CPU clk: 1536MHz
DDR chl: Rank0+1 same @ 912MHz
DDR0: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
-s
Load fip header from eMMC, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from eMMC, src: 0x00010000, des: 0x01000000, size: 0x0000d460
Sending bl30......................................................OK.
Run bl30...
Load bl31 from eMMC, src: 0x00020000, des: 0x1010[0000, size: 0x00018190
Image: gxb_v1.1.3135-18177fc 2016-06-24 11:00:09 yun.cai@droid06]
OPS=0x13
43 40 9f e0 a5 56 b9 1f 31 54 6 bf [0.210730 Inits done]
secure task start!
high task start!
low task start!
Load bl33 from eMMC, src: 0x0003c000, des: 0x01000000, size: 0x0008ecf0
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 2022.10 (Mar 18 2023 - 15:22:02 +0000) wetek-hub

Model: WeTek Hub
SoC:   Amlogic Meson GXBB (S905) Revision 1f:c (13:1)
DRAM:  1 GiB
Core:  161 devices, 25 uclasses, devicetree: separate
MMC:   mmc@70000: 0, mmc@72000: 1, mmc@74000: 2
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
[BL31]: tee size: 0
Net:   eth0: ethernet@c9410000
Hit any key to stop autoboot:  0
=>

Display More

gonp · August 5, 2023 at 10:42 AM

looks like the same issue I had some time ago, see:

Thread

Wetek Hub LE11 AMLGX, uboot stops half way...

Dear LE team,

So happy to get LE11 support for our good/old Wetek Hub, I installed AMLGX wetek Hub box image to flash.

Following the wiki page, I booted the 'box' image from SD card, then used emmctool to write the 'wetek-hub board' image to eMMC.
(I had to first 'zero' the eMMC because emmctool did not like the labels on it).

But now on boot, I can see from the serial port that the boot process stops halfway (console log below).

if I type 'boot' on the uboot prompt, it will continue and complete…

gonp

March 11, 2023 at 9:36 AM

There seem to be some noise/random characters on the Hub serial input line that stops the initial booting process.

You should be able to boot from nand too, just remove the sdcard. Once you reach the uboot prompt you can manually complete booting (type 'boot' on prompt).

After that initial boot completes ok, you should be able to use the remote to 'sleep' and 'wakeup' normally, and all should work fine.

The only way I managed to prevent the blocking of the initial booting process was to disable the RX serial line, by forcing it 'high' to 3.3V with a soldered wire.

**dtech** · August 5, 2023 at 10:51 AM

I'm not sure if the kernel in the WeTek Hub LE11 image is working. I tried booting from an SD card with it and it didn't work either.

Code

## Booting kernel from Legacy Image at 01080000 ...
   Image Name:
   Image Type:   AArch64 Linux Kernel Image (lzo compressed)
   Data Size:    11576293 Bytes = 11 MiB
   Load Address: 01c80000
   Entry Point:  01c80000
   Verifying Checksum ... OK
      Amlogic multi-dtb tool
      Single dtb detected
load dtb from 0x1000000 ......
"Synchronous Abort" handler, esr 0x96000010
ELR:     37ef1760
LR:      37ef167c
x0 : 0000000000000000 x1 : 0000000000000000
x2 : 0000000033ec8c18 x3 : 0000000000000016
x4 : 0000000037f73a40 x5 : 0000000037f73b40
x6 : 0000000037f73b48 x7 : 0000000000000020
x8 : 0000000000000031 x9 : 0000000000000000
x10: 000000000000000f x11: 0000000037f45f58
x12: 0000000000000000 x13: 0000000000000000
x14: 0000000000000000 x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 0000000033ec2e28 x19: 0000000037f73a40
x20: 0000000000000000 x21: 0000000033ec8c18
x22: 0000000037f73b40 x23: 0000000037f73b48
x24: 0000000000000016 x25: 0000000037f73b40
x26: 0000000000000000 x27: 0000000037f49f20
x28: 0000000000000000 x29: 0000000033ec2030

Resetting CPU ...

resetting ...

Display More

However, the box image boots flawlessly from the SD card.

chewitt Is it possible that the Hub image is not compatible with the WeTek factory u-boot?

**chewitt** · August 5, 2023 at 4:37 PM

The last kernel patchset I personally tested was merged for 11.0.1 so I can't speak for what issues may have been introduced with bumps others have done to newer kernels for 11.0.3 .. but historically the only issue I've seen on a Hub that caused boot issues is the UART noise problem I've flagged above (which the logs shared seem to point to). I'm not sure why newer u-boot is super-sensitive on the serial line or if anything can be done in u-boot device-tree to workaround that (my u-boot knowledge isn't awesome). I did previously experiment with a tweaked u-boot that basically disables the UART keyboard and (as expected) this sidesteps the problem. That proved the theory; but as the u-boot sources we build from are used with all AMLGX boards it's not possible to patch only the Hub at bulk-compile time.

The following may be useful:

factory_update_param.aml

Shared with Dropbox

www.dropbox.com

recovery.img

Shared with Dropbox

www.dropbox.com

https://www.dropbox.com/s/7wi5vhrgqsle6ug/dtb.img?dl=0 <= ^ these three can be copied to a FAT formatted SD to use with vendor u-boot recovery mode to restore the original factory image.

https://www.dropbox.com/s/v46jogn3rk4i…hub.tar.gz?dl=0 <= this is a dd backup of the factory image on emmc.

thegooddoctor · August 5, 2023 at 7:12 PM

Quote from gonp

looks like the same issue I had some time ago, see:

Thread

Wetek Hub LE11 AMLGX, uboot stops half way...

Dear LE team,

So happy to get LE11 support for our good/old Wetek Hub, I installed AMLGX wetek Hub box image to flash.

Following the wiki page, I booted the 'box' image from SD card, then used emmctool to write the 'wetek-hub board' image to eMMC.
(I had to first 'zero' the eMMC because emmctool did not like the labels on it).

But now on boot, I can see from the serial port that the boot process stops halfway (console log below).

if I type 'boot' on the uboot prompt, it will continue and complete…

gonp

March 11, 2023 at 9:36 AM

There seem to be some noise/random characters on the Hub serial input line that stops the initial booting process.
You should be able to boot from nand too, just remove the sdcard. Once you reach the uboot prompt you can manually complete booting (type 'boot' on prompt).
After that initial boot completes ok, you should be able to use the remote to 'sleep' and 'wakeup' normally, and all should work fine.
The only way I managed to prevent the blocking of the initial booting process was to disable the RX serial line, by forcing it 'high' to 3.3V with a soldered wire.

Yes, this looks to be the identical problem as per matching logs.

I did already try the 'boot' command and saw that it indeed continued the boot process.

How do I set the RX serial line to high with 3.3V (where did you find 3.3V on the board?)

Quote from chewitt

The last kernel patchset I personally tested was merged for 11.0.1 so I can't speak for what issues may have been introduced with bumps others have done to newer kernels for 11.0.3 .. but historically the only issue I've seen on a Hub that caused boot issues is the UART noise problem I've flagged above (which the logs shared seem to point to). I'm not sure why newer u-boot is super-sensitive on the serial line or if anything can be done in u-boot device-tree to workaround that (my u-boot knowledge isn't awesome). I did previously experiment with a tweaked u-boot that basically disables the UART keyboard and (as expected) this sidesteps the problem. That proved the theory; but as the u-boot sources we build from are used with all AMLGX boards it's not possible to patch only the Hub at bulk-compile time.
The following may be useful:
https://www.dropbox.com/s/ybsfx6xjttu2…_param.aml?dl=0
https://www.dropbox.com/s/kf5aakutmclgfho/recovery.img?dl=0
https://www.dropbox.com/s/7wi5vhrgqsle6ug/dtb.img?dl=0 <= ^ these three can be copied to a FAT formatted SD to use with vendor u-boot recovery mode to restore the original factory image.
https://www.dropbox.com/s/v46jogn3rk4i…hub.tar.gz?dl=0 <= this is a dd backup of the factory image on emmc.

Display More

thanks for the files, however the hub only boots to internal nand in this state

thegooddoctor · August 5, 2023 at 11:16 PM

Quote from chewitt

The following may be useful:
https://www.dropbox.com/s/ybsfx6xjttu2…_param.aml?dl=0
https://www.dropbox.com/s/kf5aakutmclgfho/recovery.img?dl=0
https://www.dropbox.com/s/7wi5vhrgqsle6ug/dtb.img?dl=0 <= ^ these three can be copied to a FAT formatted SD to use with vendor u-boot recovery mode to restore the original factory image.
https://www.dropbox.com/s/v46jogn3rk4i…hub.tar.gz?dl=0 <= this is a dd backup of the factory image on emmc.

how does one do this "u-boot recovery mode"?
I have access to the prompt but I can't seem to find any instructions.

**chewitt** · August 6, 2023 at 7:33 PM

IIRC the "toothpick" method should drop you into an Android restore GUI, but I'm fuzzy about it since it's years since I used it.

Bricked Wetek Hub ... now what

Wetek Hub LE11 AMLGX, uboot stops half way...

Wetek Hub LE11 AMLGX, uboot stops half way...

Similar Threads

[LE 11] Wetek play 2

Wetek Play, what to do with it?