I am unable to boot from SD card. I have tried to use the "flex-installer -i auto -m ls1046ardb -d /dev/sdc" and have tried "flex-installer -b boot_LS_arm64_lts_5.10.tgz -r rootfs_lsdk2108_ubuntu_main_arm64.tgz -f firmware_ls1046ardb_sdboot.img -d /dev/sdc" from my build/images directory. They both end in a kernel panic (below). Any suggestions?
debug port output:
[ 2.999330] Waiting for root device PARTUUID=79e0ff00-04...
[ 3.055507] mmc0: new ultra high speed SDR104 SDHC card at address aaaa
[ 3.062435] mmcblk0: mmc0:aaaa SD32G 29.7 GiB (ro)
[ 3.068327] mmcblk0: p1 p2 p3 p4
[ 3.083392] VFS: Cannot open root device "PARTUUID=79e0ff00-04" or unknown-block(179,4): error -30
[ 3.092365] Please append a correct "root=" boot option; here are the available partitions:
[ 3.100725] 0100 4096 ram0
[ 3.100727] (driver?)
[ 3.106826] 0101 4096 ram1
[ 3.106828] (driver?)
[ 3.112931] 0102 4096 ram2
[ 3.112933] (driver?)
[ 3.119032] 0103 4096 ram3
[ 3.119034] (driver?)
[ 3.125136] 0104 4096 ram4
[ 3.125138] (driver?)
[ 3.131236] 0105 4096 ram5
[ 3.131238] (driver?)
[ 3.137341] 0106 4096 ram6
[ 3.137343] (driver?)
[ 3.143446] 0107 4096 ram7
[ 3.143447] (driver?)
[ 3.149546] 0108 4096 ram8
[ 3.149548] (driver?)
[ 3.155650] 0109 4096 ram9
[ 3.155652] (driver?)
[ 3.161750] 010a 4096 ram10
[ 3.161751] (driver?)
[ 3.167940] 010b 4096 ram11
[ 3.167942] (driver?)
[ 3.174128] 010c 4096 ram12
[ 3.174130] (driver?)
[ 3.180318] 010d 4096 ram13
[ 3.180319] (driver?)
[ 3.186505] 010e 4096 ram14
[ 3.186506] (driver?)
[ 3.192695] 010f 4096 ram15
[ 3.192696] (driver?)
[ 3.198887] 1f00 524288 mtdblock0
[ 3.198889] (driver?)
[ 3.205432] 1f01 65536 mtdblock1
[ 3.205434] (driver?)
[ 3.211974] 1f02 65536 mtdblock2
[ 3.211976] (driver?)
[ 3.218509] b300 31166976 mmcblk0
[ 3.218511] driver: mmcblk
[ 3.225307] b301 131072 mmcblk0p1 79e0ff00-01
[ 3.225309]
[ 3.232106] b302 2097152 mmcblk0p2 79e0ff00-02
[ 3.232108]
[ 3.238901] b303 5242880 mmcblk0p3 79e0ff00-03
[ 3.238903]
[ 3.245697] b304 23623168 mmcblk0p4 79e0ff00-04
[ 3.245698]
[ 3.252498] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,4)
[ 3.260938] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.10.35-dirty #15
[ 3.267550] Hardware name: LS1046A RDB Board (DT)
[ 3.272248] Call trace:
[ 3.274696] dump_backtrace+0x0/0x1a8
[ 3.278353] show_stack+0x18/0x68
[ 3.281663] dump_stack+0xc8/0x120
[ 3.285059] panic+0x16c/0x334
[ 3.288109] mount_block_root+0x1c0/0x250
[ 3.292112] mount_root+0x10c/0x144
[ 3.295595] prepare_namespace+0x130/0x170
[ 3.299687] kernel_init_freeable+0x210/0x23c
[ 3.304040] kernel_init+0x14/0x114
[ 3.307523] ret_from_fork+0x10/0x34
[ 3.311096] SMP: stopping secondary CPUs
[ 3.315023] Kernel Offset: 0x520644c00000 from 0xffff800010000000
[ 3.321113] PHYS_OFFSET: 0xffffdee980000000
[ 3.325291] CPU features: 0x0040022,21806000
[ 3.329555] Memory Limit: none
[ 3.332608] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,4) ]---
Hello,
Are you able to boot from the emmc nor flash? If the board is configured with the default switch settings and power is supplied to the board, then the boot loader (U-Boot) image
located in QSPI NOR flash virtual bank 0 runs.
After confirming it boots please review again your switch configuration and try again using the pre-build images.
https://www.nxp.com/webapp/Download?colCode=LS1046ARDBGSG
Regards.
Of course it booted with the default settings. I then switched the boot config switches to allow for sd-boot (as defined in the LS1046ARDB user guide), and this is what I got with both my slightly modified image AND the pre-built image.