stut Posted February 3, 2023 Posted February 3, 2023 (edited) I was dumb enough to try and update uboot on this little box and then it got sort of bricked. When connected using serial I could see it loop trying to boot from EMMC so I tried the reset button recovery to no avail. Shorting the EMMC pins works putting the device in recovery mode but the usb burn tool is stuck on formatting at 7% after it seems to sucesfull removed (and maybe flashed) uboot but the serial connection still shows it looping on EMMC. So I tried the next thing, shorting EMMC while connected using serial and I could the looping change to include sd and usb. So I made a sd recovery card using the burn card tool and it can boot from it, I can see uboot scroll by but it also gets stuck restoring (see log below). I've left it connected like this for an hour but it never progresses beyond whats shown in the log. Is there a way to bring this back to live? I don't mind if the internal EMMC is fried as I was using sd cards with Arabian anyways. I build the latest Arabian from source for the s9xx target and it all worked perfectly fine. Until I messed with uboot. I really have no clue as to why this is so hard to recover. I messed up before and shorting EMMC always made the usb burn tool recover it back to Android so my guess is that the EMMC is really gone for some reason. Is there a thing I can do to always make it both from sd card? I'm unable to boot Arabian when it cycling between EMMC/sd/usb, only the card made with the card burning tool will boot. I can't interrupt the booting process to get into a uboot shell, I've tried mashing the keyboard many times but it always continues to boot and tries to recover using the sd card as seen in the log. I hope someone can help me bring this back to life as it would be a shame to throw it away. It's a nice little board with working wireless in Armbian and 2gb ram and 16gb internal storage. Thanks for reading and I'll leave you with the log from the serial console (as you can see it only tried to boot from EMMC until I shorted the pins): GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0;GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0; no sdio debug board detected TE: 120589 BL2 Built : 20:32:17, Sep 8 2017. gxl g6296b83 - xiaobo.gu@droid12 set vcck to 1120 mv set vddee to 1000 mv Board ID = 2 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0 16bit @ 792MHz Rank0: 2048MB(auto)-2T-11 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: 0x01100000, size: 0x0000d600 Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x0002c600 Load bl32 from SD, src: 0x00050200, des: 0x05300000, size: 0x00036600 Load bl33 from SD, src: 0x00088200, des: 0x01000000, size: 0x00066400 NOTICE: BL3-1: v1.0(release):a625749 NOTICE: BL3-1: Built : 11:25:15, Aug 25 2017 [BL31]: GXL CPU setup! NOTICE: BL31: BL33 decompress pass mpu_config_enable:ok [Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07] OPS=0xa4 38 66 40 cf a6 83 88 53 30 85 f5 8 [0.544834 Inits done] secure task start! high task start! low task start! INFO: BL3-2: ATOS-V2.0.2-g4bffb3e #1 Wed Sep 27 19:06:53 CST 2017 arm INFO: BL3-2: Chip: GXL Rev: D (21:D - A0:2) INFO: BL3-2: crypto engine DMA INFO: BL3-2: secure time TEE INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e U-Boot 2015.01 (Apr 21 2018 - 13:07:25) DRAM: 2 GiB Relocation Offset is: 76eb2000 board_init sm1628. register usb cfg[0][1] = 0000000077f5a1b8 [CANVAS]canvas init 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 = 0x0000000073eb26b0 aml_priv->desc_buf = 0x0000000073eb49d0 SDIO Port B: 0, SDIO Port C: 1 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 [mmc_init] mmc init success dtb magic 38315245 Amlogic multi-dtb tool Cannot find legal dtb! start dts,buffer=0000000073eb7200,dt_addr=0000000073eb7200 check_valid_dts: FDT_ERR_BADMAGIC get_partition_from_dts: -9 get_ptbl_from_dtb()-259: get partition table from dts faild mmc_device_init()-1081: get partition table from dtb failed get_ptbl_rsv()-483: magic faild MPT, ER1 mmc_device_init()-1108: dtb&rsv are not exist, no LPT source _find_partition_by_name()-188: do not find match in table env get partition info failed !! Using default environment In: serial Out: serial Err: serial reboot_mode=cold_boot [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _verify_dtb_checksum()-917: calc 62a48a00, store 0 dtb_read()-1034: cpy 1 is not valid _verify_dtb_checksum()-917: calc 62a48a00, store 0 dtb_read()-1034: cpy 0 is not valid dtb_read()-1039: total valid 0 Amlogic multi-dtb tool Cannot find legal dtb! [store]Err:do_store_dtb_ops,L330: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] _verify_dtb_checksum()-917: calc 62a48a00, store 0 dtb_read()-1034: cpy 1 is not valid _verify_dtb_checksum()-917: calc 62a48a00, store 0 dtb_read()-1034: cpy 0 is not valid dtb_read()-1039: total valid 0 Amlogic multi-dtb tool Cannot find legal dtb! [store]Err:do_store_dtb_ops,L330:Fail in fdt check header board_late_init(): store dtb read 1000000 fail vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: clk_level = 7 vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300) vpu: vpu_clk_gate_init_off vpp: vpp_init hpd_state=0 cvbs performance type = 6, table = 0 card in init_part() 278: PART_TYPE_DOS [mmc_init] mmc init success Device: SDIO Port B Manufacturer ID: 74 OEM: 4a60 Name: USDU1 Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 29.8 GiB mmc clock: 40000000 Bus Width: 4-bit [MSG]ini sz 0x256B [fat]Filesize is 0x256B[0M] [fat]0x:leftSz 256 < BPS 4000, gotSz 256 =========sdc_burn_paras=====>>> [common] erase_bootloader = 1 erase_flash = 2 reboot = 0x0 key_overwrite = 0x0 [burn_ex] package = aml_upgrade_package.img media = [burn_parts] burn_num = 0 <<<<=====sdc_burn_paras====== [fat]Filesize is 0x4737a458B[1139M] [fat]0x:leftSz 2c40 < BPS 4000, gotSz 6c40 [MSG]image version [0x00000002] [MSG]cfg10=0xADFC318C [fat]Seek 0xf28c0 from 0x6c40 [MSG]itemSizeNotAligned 0x1740 [MSG]align 4 mmc read... [fat]0x:leftSz c0 < BPS 4000, gotSz 15800 [MSG]Down(mem) part(dtb) sz(0x15800) fmt(normal) [MSG]Burn Start... [MSG]load dt.img to 0x0000000001000000, sz=0x15800 [MSG]Burn complete Err imgread(L587):Logo header err. _find_partition_by_name()-188: do not find match in table logo 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 store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read logo 0xba20000 0x0 0x100000] Err imgread(L361):Fail to read 0x100000B from part[logo] at offset 0 [MSG]Use upgrade res in pkg [WRN]Can't find item [logo, aml_sdc_burn] [MSG]logo for sdc UPGRADE[PARTITION] [fat]Seek 0xb39dac from 0x1080c0 [MSG]itemSizeNotAligned 0x2254 [MSG]align 4 mmc read... [fat]0x:leftSz adc < BPS 4000, gotSz 6cad30 [MSG]echo video prepare for upgrade hpd_state=0 [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=5760, height=2160 cvbs performance type = 6, table = 0 [MSG]dw,dh[1920, 1080] [MSG]w,h[4,14] [MSG]Exit before re-init command: store exit dtb magic 5f4c4d41 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 start dts,buffer=0000000001000000,dt_addr=000000000100b000 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 parts: 10 00: logo 0000000002000000 1 01: recovery 0000000002000000 1 02: rsv 0000000000800000 1 03: tee 0000000000800000 1 04: crypt 0000000002000000 1 05: misc 0000000002000000 1 06: boot 0000000002000000 1 07: system 0000000080000000 1 08: cache 0000000020000000 2 09: data ffffffffffffffff 4 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 [mmc_init] mmc init success _calculate_offset()-349: too large partition table for current emmc, overflow! switch to partitions #0, OK mmc1(part 0) is current device Device: SDIO Port C Manufacturer ID: 65 OEM: 646f Name: M MOR Tran Speed: 52000000 Rd Block Len: 512 MMC version 4.41 High Capacity: No Capacity: 128 MiB mmc clock: 40000000 Bus Width: 8-bit [store]amlmmc erase 1emmckey_is_protected : protect start = 0,end = 29359616 start = 113246208,end = 134216704 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 [burn_parts] burn_num = 5 burn_part0 = _aml_dtb burn_part1 = boot burn_part2 = logo burn_part3 = recovery burn_part4 = system [MSG]=====>To burn part [_aml_dtb] [MSG]itemSizeNotAligned 0x1740 [MSG]Down(store) part(_aml_dtb) sz(0x15800) fmt(normal) [MSG]totalSlotNum = 0, nextWriteBackSlot 2 [MSG]itemSizeNotAligned 0x1740 [fat]0x:leftSz c0 < BPS 4000, gotSz 40c0 [MSG]Burn Start... [MSG]optimus_download_dtb_image:dataSzReceived=0x15800 start erase dtb...... start = 41943040,end = 42466816 dev # 1, , several blocks erased OK [store]To run cmd[emmc dtb_write 0x00000000076fe8c0 0x40000] dtb_write()-1140: valid 0 dtb_write()-1160: new stamp 0, checksum 0x4487cea3, version 1, magic A~D Edited February 3, 2023 by stut
SteeMan Posted February 3, 2023 Posted February 3, 2023 16 minutes ago, stut said: Is there a thing I can do to always make it both from sd card? If your emmc is not working, I don't think you can. My understanding is that these amlogic boxes basically are hard coded to look for uboot on emmc. That is why the aml-s9xx-box builds use the emmc uboot to then chain load the distribution from sd/usb/etc. It is always using the emmc uboot initially. If your emmc is working, you should use recovery to reinstall the android uboot and then you could move on from there. But in your case you have already tried that, and it didn't work (likely indicating that your emmc is not working). Based on your comments, it sounds like you have previously reinstalled the android firmware, so you know that process used to work (the reason I am stating this, is that sometimes different boards/firmware combinations require specific versions of the amlogic burning tool) 1
stut Posted February 3, 2023 Author Posted February 3, 2023 (edited) Yes, I've done recovery to Android many times on many of these little boxes. What I'm stumped by is that seemingly my nand is no longer functioning properly despite only using some software trying to update uboot. Usually software doesn't break hardware but it seems this box is unrecoverable now. When it's turned on there's no uboot showing, it just shows this one line where is loops trying to boot from EMMC. Only after shorting EMMC pins it tries to boot from usb or sd in the loop. Once I connect the sd card made with the card burning tool it boots. Nothing on other usb sticks boots (both Android recovery and Armbian) and only sd card booting works made with the card burning tool. LOOP:18;EMMC:0;READ:0;CHK:A7;READ:0;CHK:A7;READ:0;CHK:A7;SD:800;USB:8;LOOP:19;EMMC:0;READ:0;CHK:A7;READ:0;CHK:A7;READ:0;CHK:A7;SD:800;USB:8;LOOP:1A;EMMC:0;READ:0;CHK:A7;READ:0;CHK:A7;READ:0;CHK:A7;SD:800;USB:8;LOOP:1B;EMMC:0;READ:0;CHK:A7;READ:0;CHK:A7;READ:0;CHK:A7;SD:0;READ:0;0.0;CHK:0; There are entries in the log about the partition table and some kind of overflowing? I guess somehow when trying to update uboot the partition table got messed up and eight usb burning tool as sd card burning tool can fix it. Really amazing a software update can just convert this little box into a paperweight. I think you're right about the booting but I'm still temped to desolder the nand chip and see what happens, can't get much worse than it is now right? Haha. Edited February 3, 2023 by stut
SteeMan Posted February 3, 2023 Posted February 3, 2023 Another factor is that at least as far as the armbian builds go, there is no uboot suitable for your box available. It isn't feasible/possible to build uboots for the hundreds of different tv box hardware configurations out there (and the tv box manufacturers don't release their source for their android uboots), so the uboot on the armbian build sd card is basically just a place holder (generic uboot that 100% is guaranteed not to work for your box). The whole armbian amlogic tv box strategy is to use the uboot that comes with the tv box on emmc. So if you are trying to get something working from sd, it isn't going to be armbian unless you can get your emmc working again. 1
stut Posted February 3, 2023 Author Posted February 3, 2023 (edited) Alright, so in order to boot Armbian I need to be able to put the original uboot on the internal storage which is seemingly impossible as all recovery methods fail. I guess it goes into the bin and I'll order some Raspberry Zero W2 to replace it. Thanks for your time! After desoldering the nand chip it now always tried to boot from all 3, EMMC, sd and usb. So if I manage to somehow compile a compatible uboot I should be able to boot it right? I might give it a go before throwing it out. It'll be educational if anything. Obviously the restore sd card can't restore but it still boots, maybe the uboot can be taken from there and used on an Armbian sd card. I'll give that a go too. It's funny to see it try to restore to a non-existing chip, it even tries to unlock it haha. GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0; no sdio debug board detected TE: 2445339 BL2 Built : 20:32:17, Sep 8 2017. gxl g6296b83 - xiaobo.gu@droid12 set vcck to 1120 mv set vddee to 1000 mv Board ID = 2 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0 16bit @ 792MHz Rank0: 2048MB(auto)-2T-11 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: 0x01100000, size: 0x0000d600 Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x0002c600 Load bl32 from SD, src: 0x00050200, des: 0x05300000, size: 0x00036600 Load bl33 from SD, src: 0x00088200, des: 0x01000000, size: 0x00066400 NOTICE: BL3-1: v1.0(release):a625749 NOTICE: BL3-1: Built : 11:25:15, Aug 25 2017 [BL31]: GXL CPU setup! NOTICE: BL31: BL33 decompress pass mpu_config_enable:ok [Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 qiufang.dai@droid07] OPS=0xa4 38 66 40 cf a6 83 88 53 30 85 f5 8 [2.869655 Inits done] secure task start! high task start! low task start! INFO: BL3-2: ATOS-V2.0.2-g4bffb3e #1 Wed Sep 27 19:06:53 CST 2017 arm INFO: BL3-2: Chip: GXL Rev: D (21:D - A0:2) INFO: BL3-2: crypto engine DMA INFO: BL3-2: secure time TEE INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e U-Boot 2015.01 (Apr 21 2018 - 13:07:25) DRAM: 2 GiB Relocation Offset is: 76eb2000 board_init sm1628. register usb cfg[0][1] = 0000000077f5a1b8 [CANVAS]canvas init 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 = 0x0000000073eb26b0 aml_priv->desc_buf = 0x0000000073eb49d0 SDIO Port B: 0, SDIO Port C: 1 MMC init failed Using default environment In: serial Out: serial Err: serial reboot_mode=watchdog_reboot [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _dtb_init()-956: mmc init failed Amlogic multi-dtb tool Cannot find legal dtb! [store]Err:do_store_dtb_ops,L330: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] _dtb_init()-956: mmc init failed Amlogic multi-dtb tool Cannot find legal dtb! [store]Err:do_store_dtb_ops,L330:Fail in fdt check header board_late_init(): store dtb read 1000000 fail vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: clk_level = 7 vpu: set clk: 666667000Hz, readback: 666660000Hz(0x300) vpu: vpu_clk_gate_init_off vpp: vpp_init hpd_state=0 cvbs performance type = 6, table = 0 card in init_part() 278: PART_TYPE_DOS [mmc_init] mmc init success Device: SDIO Port B Manufacturer ID: 74 OEM: 4a60 Name: USDU1 Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 29.8 GiB mmc clock: 40000000 Bus Width: 4-bit [MSG]ini sz 0x256B [fat]Filesize is 0x256B[0M] [fat]0x:leftSz 256 < BPS 4000, gotSz 256 =========sdc_burn_paras=====>>> [common] erase_bootloader = 1 erase_flash = 4 reboot = 0x1 key_overwrite = 0x0 [burn_ex] package = aml_upgrade_package.img media = [burn_parts] burn_num = 0 <<<<=====sdc_burn_paras====== [fat]Filesize is 0x4737a458B[1139M] [fat]0x:leftSz 2c40 < BPS 4000, gotSz 6c40 [MSG]image version [0x00000002] [MSG]cfg10=0xADFC318C [fat]Seek 0xf28c0 from 0x6c40 [MSG]itemSizeNotAligned 0x1740 [MSG]align 4 mmc read... [fat]0x:leftSz c0 < BPS 4000, gotSz 15800 [MSG]Down(mem) part(dtb) sz(0x15800) fmt(normal) [MSG]Burn Start... [MSG]load dt.img to 0x0000000001000000, sz=0x15800 [MSG]Burn complete Err imgread(L587):Logo header err. 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 store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read logo 0xba20000 0x0 0x100000] Err imgread(L361):Fail to read 0x100000B from part[logo] at offset 0 [MSG]Use upgrade res in pkg [WRN]Can't find item [logo, aml_sdc_burn] [MSG]logo for sdc UPGRADE[PARTITION] [fat]Seek 0xb39dac from 0x1080c0 [MSG]itemSizeNotAligned 0x2254 [MSG]align 4 mmc read... [fat]0x:leftSz adc < BPS 4000, gotSz 6cad30 [MSG]echo video prepare for upgrade hpd_state=0 [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=5760, height=2160 cvbs performance type = 6, table = 0 [MSG]dw,dh[1920, 1080] [MSG]w,h[4,14] [MSG]Exit before re-init command: store exit dtb magic 5f4c4d41 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 start dts,buffer=0000000001000000,dt_addr=000000000100b000 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 parts: 10 00: logo 0000000002000000 1 01: recovery 0000000002000000 1 02: rsv 0000000000800000 1 03: tee 0000000000800000 1 04: crypt 0000000002000000 1 05: misc 0000000002000000 1 06: boot 0000000002000000 1 07: system 0000000080000000 1 08: cache 0000000020000000 2 09: data ffffffffffffffff 4 [MSG]run cmd [store disprotect key; store disprotect hynix] [store]disprotect key disprotect hynix Device: SDIO Port B Manufacturer ID: 74 OEM: 4a60 Name: USDU1 Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 29.8 GiB mmc clock: 40000000 Bus Width: 4-bit [store]amlmmc key emmc disprotect key [store]amlmmc erase 1emmckey_is_protected : disprotect blkcnt = 0 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 [burn_parts] burn_num = 5 burn_part0 = _aml_dtb burn_part1 = boot burn_part2 = logo burn_part3 = recovery burn_part4 = system [MSG]=====>To burn part [_aml_dtb] [MSG]itemSizeNotAligned 0x1740 [MSG]Down(store) part(_aml_dtb) sz(0x15800) fmt(normal) [MSG]totalSlotNum = 0, nextWriteBackSlot 2 [MSG]itemSizeNotAligned 0x1740 [fat]0x:leftSz c0 < BPS 4000, gotSz 40c0 [MSG]Burn Start... [MSG]optimus_download_dtb_image:dataSzReceived=0x15800 start erase dtb...... dev # 1, , several blocks erased OK [store]To run cmd[emmc dtb_write 0x00000000076fe8c0 0x40000] _dtb_init()-956: mmc init failed dtb magic 5f4c4d41 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 start dts,buffer=00000000076fe8c0,dt_addr=00000000077098c0 dtb magic 5f4c4d41 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 start dts,buffer=00000000076fe8c0,dt_addr=00000000077098c0 Amlogic multi-dtb tool Multi dtb detected Multi dtb tool version: v2 . Support 2 dtbs. aml_dt soc: gxl platform: p212 variant: 2g dtb 0 soc: gxl plat: p212 vari: 1g dtb 1 soc: gxl plat: p212 vari: 2g Find match dtb: 1 parts: 10 00: logo 0000000002000000 1 01: recovery 0000000002000000 1 02: rsv 0000000000800000 1 03: tee 0000000000800000 1 04: crypt 0000000002000000 1 05: misc 0000000002000000 1 06: boot 0000000002000000 1 07: system 0000000080000000 1 08: cache 0000000020000000 2 09: data ffffffffffffffff 4 _dtb_init()-956: mmc init failed "Synchronous Abort" handler, esr 0x96000210 ELR: 77efda10 LR: 77efd9b0 x0 : 0000000000400000 x1 : 0000000077f618f8 x2 : 0000000000000001 x3 : 0000000000000004 x4 : 0000000004000000 x5 : 0000000077f618d0 x6 : 0000000077f618f8 x7 : 0000000000000020 x8 : 0000000000000034 x9 : 0000000000000000 x10: 000000000000000f x11: 0000000077f384d0 x12: 0000000000000000 x13: 0000000000004000 x14: 0000000000000000 x15: 0000000000000000 x16: 0000000000000000 x17: 0000000000000000 x18: 0000000073ea1e28 x19: 0000000077f618d0 x20: 0000000002400000 x21: 0000000073ea1250 x22: 0000000000000090 x23: 0000000077f42da1 x24: 0000000077fbb000 x25: 0000000000000000 x26: 0000000000000000 x27: 0000000073eac6e0 x28: 0000000000000090 x29: 0000000073ea11c0 Resetting CPU ... resetting ... Oh, I just noticed it is also trying to boot from SPI now, that wasn't in the list before! Edited February 3, 2023 by stut
hexdump Posted February 4, 2023 Posted February 4, 2023 @stut - here i wrote down quite a bit of information about how to build mainline u-boot for amlogic s905x/w devices - see: https://github.com/hexdump0815/u-boot-misc/blob/master/readme.gxl - you might try the ones i built (see the july 18 2020 releases of that github repo) - gunzip all the files with boot-amlogic_gxl_*.gz and then dd them to an sd card and try to boot them one by one with serial console and a hdmi monitor connected (some have serial console and some hdmi) - if you are lucky one of them maybe gives you a working mainline u-boot you can boot from sd card good luck and best wishes - hexdump 1
Recommended Posts