it isn't bricked ...
I have a pretty good idea of what is happening and have to build an appropriate image to restore it so the older u-boot loader is installed on the NAND chip (the new u-boot loader is what is faulty --- and I don't know why it is being used if it is known to be problematic [what advantages does it provide? if any])
i have lots on my plate right now so this is a low priority item that I will eventually provide a solution for
I apreciate your help! Thanks in advance!!!
Hi! I've read this thread and it seems that i am in the same situation. Can't boot my wetek hub after a proper emmctool write with LibreELEC-AMLGX.arm-11.0.3-wetek-hub.img.gz image.
here is my uart log from boot:
GXBB:BL1:08dafd:0a8993;FEAT:EDFD718C;POC:3;RCY:0;EMMC:0;READ:0;CHK:0;
no sdio debug board detected
TE: 131424
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
5e 6f 6f 84 2d d9 3a f9 46 82 f2 52 [0.216829 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
=> Error initialing rntime erce optd_fasINFO: L31: ing onormH BHe@d`x H -1:@ps"P
> <@t>
>
>
> U-` H5 202310:002 0) 7tekub
> Mo Tek HboC: logic eson G (S9) evision 1(13:1)DM: GiBC: 1 devces25 uasses, dceree seprae
> MMC*@@ 00, mm20001mmc@740 2
> L Enronment from owhere..K
> In: @haut: erialrr <INTERRUPT>
=> hze 0et: h0:thernt@c0000
Unknown command 'hze' - try 'help'
=> z<INTERRUPT>
=> boot
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc2(part 0) is current device
Scanning mmc 2:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1: LibreELEC
Retrieving file: /KERNEL
append: boot=LABEL=BOOT disk=LABEL=DISK 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: 11576293 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: 0I'm prepared to shorted the pins to force a boot from mSD. But i need assistance for that. Wich pins to i have to shorted. I've attached an image of my hub.
Do i need to disassemble the hub more? How do i do that? How can i take the wifi antenna connector?
Thanks in advance!