Other Parts Discussed in Thread: AM625
Hi TI Experts
Getting a kernel panic, but from u-boot the settings look correct. I think there is a problem with bootargs.
I'm not sure if this is related to using GPT partitions .vs. MBR style bootable flag.
Error:
[ 2.686019] VFS: PARTUUID= is invalid.
[ 2.686019] Expected PARTUUID=<valid-uuid-id>[/PARTNROFF=%d]
[ 2.686024] Disabling rootwait; root= is invalid.
[ 2.686650] /dev/root: Can't open blockdev
[ 2.686668] VFS: Cannot open root device "PARTUUID=" or unknown-block(0,0): error -6
[ 2.686672] P
[ 1.136841] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
[ 1.140322] debugfs: Directory 'pd:182' with parent 'pm_genpd' already present!
[ 1.141044] mmc2: CQHCI version 5.10
[ 1.141079] mmc1: CQHCI version 5.10
[ 1.143290] debugfs: Directory 'pd:186' with parent 'pm_genpd' already present!
[ 1.155788] ALSA device list:
[ 1.155799] No soundcards found.
[ 1.183234] mmc2: SDHCI controller on fa20000.mmc [fa20000.mmc] using ADMA 64-bit
[ 1.213866] mmc0: Command Queue Engine enabled
[ 1.213885] mmc0: new HS200 MMC card at address 0001
[ 1.214587] mmcblk0: mmc0:0001 S0J56X 14.8 GiB <======== HARWARWE UDA partition 0 - I have two filesystem partitions
[ 1.218247] mmcblk0: p1 p2
[ 1.218988] mmcblk0boot0: mmc0:0001 S0J56X 31.5 MiB
[ 1.220275] mmcblk0boot1: mmc0:0001 S0J56X 31.5 MiB
[ 1.221403] mmcblk0rpmb: mmc0:0001 S0J56X 4.00 MiB, chardev (240:0)
Preface:
=> mmc part Partition Map for MMC device 0 -- Partition Type: EFI Part Start LBA End LBA Name Attributes Type GUID Partition GUID 1 0x00000022 0x003f8021 "primary" <== Filesystem partition [/dev/mmcblk0p1] attrs: 0x0000000000000000 type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 guid: e7dbd504-c47a-493d-a1d4-aa34686b4b5b <== Seems like it may be looking for this 2 0x003f8022 0x007f0021 "secondary" attrs: 0x0000000000000000 type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 guid: 93e4c649-cb27-4c27-ab7f-eb65a9ec348c => ls mmc 0 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found <DIR> 4096 bin <DIR> 4096 boot <== Boot image is available <DIR> 4096 dev
=> ls mmc $bootpart /boot/dtb <DIR> 4096 . <DIR> 4096 .. <DIR> 4096 ti
=> ls mmc $bootpart /boot/dtb/ti <DIR> 4096 . <DIR> 4096 .. 1990 k3-am625-beagleplay-csi2-ov5640.dtbo <snip> 1636 k3-am625-sk-pwm.dtbo 2483 k3-am625-sk-rpi-hdr-ehrpwm.dtbo 59456 k3-am625-sk.dtb <== Here is the dtb
am62x.env MODS:
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env?h=09.01.00.008#n32
--- a/board/ti/am62x/am62x.env
+++ b/board/ti/am62x/am62x.env
@@ -28,8 +28,9 @@ args_all=setenv optargs ${optargs} earlycon=ns16550a,mmio32,0x02800000
run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
boot=mmc
-mmcdev=1
-bootpart=1:2
+mmcdev=0
+bootpart=0:1 ?? Correct mmcdev=0 (eMMC) and HWpartition=1 (boot0) ??
bootdir=/boot
rd_spec=-
STATE OF U-BOOT environment:
=> echo $mmcdev
0
=> echo $bootpart
0:1
And I have executed
=> echo $name_fdt
ti/k3-am625-sk.dtb
=> echo $fdtfile
ti/k3-am625-sk.dtb
mmc partconf 0 1 1 1 (This makes boot0 (0 1 1 1) running tiboot3.bin/tispl.bin/u-boot.img boot 1 (0 1 2 1))
HW Partition is the 3rd value, So UDA is (0 1 0 1) and RPMD is (0 1 3 0), partconf is zero indexed.
mmc bootbus 0 2 0 0 8 bit eEMMC
TO FIX THE " 2.657698] Please append a correct "root=" boot option; here are the available partitions:"
I set:
setenv root /dev/mmcblk0p1
Then
=> boot Which fails as above.
Once I get U-boot to launch from eMMC u-boot I can update uEnv.txt.emmc to perform these steps automatically.
Note, The Ethernet version of U-boot correctly utilizes uEnv.txt.ether to boot and the flash the eMMC boot0,
erase eMMC UDA, then create partitions and load the RFS image (with kernel/dtb/ that DOES correctly boot Linux (without kernel panic).
Just really close but still not right at this time.
Regards,
RG
