laibsch Posted 15 hours ago Posted 15 hours ago The latest Armbian IoT image for Khadas VIM4 does not boot. sha256sum: 69b10797369fd572d590aeb0dd7b28a4ebc5882cec8db8daf592db7b158bf141 Here is the log from the serial debug console. Spoiler [...] Hit any key to stop autoboot: 0 Setting bus to 6 _find_partition_by_name()-200: do not find match in table boot _find_partition_by_name()-200: do not find match in table boot error partition name! 4096 bytes read in 1 ms (3.9 MiB/s) _find_partition_by_name()-200: do not find match in table boot _find_partition_by_name()-200: do not find match in table boot error partition name! 4194304 bytes read in 2 ms (2 GiB/s) avb2: 1 active_slot is normal ab_suffix is _find_partition_by_name()-200: do not find match in table vbmeta _find_partition_by_name()-200: do not find match in table vbmeta get partition info failed !! _find_partition_by_name()-200: do not find match in table vbmeta _find_partition_by_name()-200: do not find match in table vbmeta error partition name! Failed to read 65536B from part[vbmeta] at 0 avb_slot_verify.c:721: ERROR: vbmeta: Error loading vbmeta data. avb verification: locked = 1, result = 2 try upgrade as booting failure PHY2=00000000fe03a020,phy-base=0xfe03e000 noSof Device: emmc Manufacturer ID: 15 OEM: 100 Name: BJTD4 Bus Speed: 192000000 Mode : HS200 (200MHz) Rd Block Len: 512 MMC version 5.1 High Capacity: Yes Capacity: 29.1 GiB Bus Width: 8-bit Erase Group Size: 512 KiB HC WP Group Size: 8 MiB User Capacity: 29.1 GiB WRREL Boot Capacity: 4 MiB ENH RPMB Capacity: 4 MiB ENH card in ** Unrecognized filesystem type ** ** Unrecognized filesystem type ** starting USB... USB0: Register 1000120 NbrPorts 1 Starting the controller USB XHCI 1.10 USB1: No ----gpio-vbus-power Register 2000120 NbrPorts 1 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found active_slot: normal _find_partition_by_name()-200: do not find match in table recovery _find_partition_by_name()-200: do not find match in table recovery error partition name! Err imgread(L199):Fail to read 0x2000B from part[recovery] at offset 0 Err imgread(L466):Fail read dtb from recovery, ret 200 restore dtb the dtb partition size is:40000 byte _verify_dtb_checksum()-2815: calc 0, store 0 update_dtb_info()-2923: cpy 1 is not valid _verify_dtb_checksum()-2815: calc 0, store 0 update_dtb_info()-2923: cpy 0 is not valid dtb_read()-3030: total valid 0 Err imgread(L339):Fail read dtb from rsv with sz 0x40000 Err imgread(L466):Fail read dtb from _aml_dtb, ret -340 [imgread]read from part: recovery _find_partition_by_name()-200: do not find match in table recovery _find_partition_by_name()-200: do not find match in table recovery error partition name! Err imgread(L545):Fail to read 0x100000B from part[recovery] at offset 0 kvim4# 0 Quote
laibsch Posted 15 hours ago Author Posted 15 hours ago no boot for Khadas-supplied Fenix 24.04.1.6.9 image, either. sha256sum: e89b80b7777fed524651b98d04e8afc0406fee76e4c5f9ccf4457df4fb6d9054 Spoiler [...] mmc_init: -110, time 1589 emmc: resp timeout, cmd8, status=0x1cf2800 emmc: resp timeout, cmd55, status=0x1cf2800 emmc: tuning start: emmc: best_win_start =5, best_win_size =5 emmc: clk = 10000206, dly1 = 0, dly2 = 0, adj = 12000, cfg = 804872 1 blocks read: OK gpt_alt->magic _mmc_check_gpt: gpt is invalid and can't be repair gpt is complete 34 blocks read: OK mmc_gpt_read: invalid GPT 34 blocks read: OK mmc_gpt_read: invalid GPT fill_ept_by_gpt: invalid gpt check_valid_dts: FDT_ERR_BADMAGIC get_partition_from_dts() 244: ret -9 get_partition_from_dts() 247: ret -9 get_ptbl_from_dtb()-373: get partition table from dts faild mmc_device_init()-1861: get partition table from dtb failed get_ptbl_rsv()-638: magic faild MPT, mmc_device_init()-1895: dtb&rsv are not exist, no LPT source switch to partitions #0, OK mmc1(part 0) is current device ** Invalid partition 1 ** _find_partition_by_name()-203: do not find match in table boot _find_partition_by_name()-203: do not find match in table boot error partition name! 4096 bytes read in 2 ms (2 MiB/s) ## Error: "storage_param" not defined _find_partition_by_name()-203: do not find match in table boot _find_partition_by_name()-203: do not find match in table boot error partition name! 4194304 bytes read in 2 ms (2 GiB/s) avb2: 0 avb2: 0 Wrong Image Format for bootm command ERROR: can't get kernel image! check_ramdump, ramdump_enable = <NULL> libfdt fdt_check_header(): FDT_ERR_BADMAGIC [rsvmem] fdt addr error. rsvmem - reserve memory Usage: rsvmem check - check reserved memory rsvmem dump - dump reserved memory rsvmem check failed try upgrade as booting failure PHY2=00000000fe03a020,phy-base=0xfe03e000 noSof Device: emmc Manufacturer ID: 15 OEM: 100 Name: BJTD4 Bus Speed: 192000000 Mode : HS200 (200MHz) Rd Block Len: 512 MMC version 5.1 High Capacity: Yes Capacity: 29.1 GiB Bus Width: 8-bit Erase Group Size: 512 KiB HC WP Group Size: 8 MiB User Capacity: 29.1 GiB WRREL Boot Capacity: 4 MiB ENH RPMB Capacity: 4 MiB ENH sd: resp timeout, cmd17, status=0x1ff2800 ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** sd: resp timeout, cmd17, status=0x1ff2800 ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** active_slot: normal _find_partition_by_name()-203: do not find match in table recovery _find_partition_by_name()-203: do not find match in table recovery error partition name! Err imgread(L228):Fail to read 0x2000B from part[recovery] at offset 0 Err imgread(L447):Fail read dtb from recovery, ret 229 restore dtb the dtb partition size is:40000 byte _verify_dtb_checksum()-2960: calc 0, store 0 update_dtb_info()-3068: cpy 1 is not valid _verify_dtb_checksum()-2960: calc 0, store 0 update_dtb_info()-3068: cpy 0 is not valid dtb_read()-3175: total valid 0 Err imgread(L391):Fail read dtb from rsv with sz 0x40000 Err imgread(L447):Fail read dtb from _aml_dtb, ret -392 Load dtb/amlogic/kvim4n.dtb from SD (0:1) ... sd: resp timeout, cmd17, status=0x1ff2800 ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** sd: resp timeout, cmd17, status=0x1ff2800 ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** [imgread]read from part: recovery _find_partition_by_name()-203: do not find match in table recovery _find_partition_by_name()-203: do not find match in table recovery error partition name! Err imgread(L551):Fail to read 0x100000B from part[recovery] at offset 0 ethernet@fdc00000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! phy_startup() failed: -110eth init FAILED Retrieving file: pxelinux.cfg/00000000-0000-0000-0000-000000000000 ethernet@fdc00000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! phy_startup() failed: -110eth init FAILED Retrieving file: pxelinux.cfg/01-02-ad-36-01-7d-7a ethernet@fdc00000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! phy_startup() failed: -110eth init FAILED Retrieving file: pxelinux.cfg/C0A81FC8 ethernet@fdc00000 Waiting for PHY auto negotiation to complete........ 0 Quote
Werner Posted 2 hours ago Posted 2 hours ago So besides Armbian a more recent image from khadas themselves also fails to boot? 0 Quote
laibsch Posted 1 hour ago Author Posted 1 hour ago 1 hour ago, Werner said: So besides Armbian a more recent image from khadas themselves also fails to boot? Yes, the more recent Khadas-supplied image also fails to boot. The unit came with Android flashed from the factory and that image worked fine (but was ugly and I do not know which one it was exactly). Trying to install an Android or Ubuntu image via their OOWOW service also failed but at the time I did not log it via serial console. Maybe it is to do with the changes in VIM4 New? Maybe it is a Ubuntu issue? At this point, I cannot say for sure, yet. I believe I can say with a fair degree of certainty that recent images from both Armbian and Khadas are broken. Other users have reported similar experiences. I am currently going through all kinds of images to see if they work or not. @c0rnelius was kind enough to provide me with a trixie-based, self-compiled image and that one worked, too. He also did not have any issues with other images, but I believe he did not try Android or Ubuntu images, but only Trixie and Coreelec ones. I believe I tried at one point a self-compiled Ubuntu image and that also did not work. Again, I did not get a serial console log for that one. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.