Hi Nishanth,
On Thu, Nov 09, 2023 at 06:23:03AM -0600, Nishanth Menon wrote:
On 11:29-20231109, Mattijs Korpershoek wrote:
Hi Maxime, Nishanth,
On mer., nov. 08, 2023 at 16:05, Maxime Ripard mripard@redhat.com wrote:
Hi Nishanth,
I've been trying for the last few days to get an SK-AM62 to boot from the eMMC user data area.
I finally got the jumper configuration to make the CPU boot from there thanks to Mattijs, but it looks like the 2024.01-rc2 release doesn't support booting from there:
U-Boot SPL 2024.01-rc2 (Nov 08 2023 - 14:11:12 +0100) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.5--v09.01.05 (Kool Koala)') SPL initial stack usage: 13368 bytes Trying to boot from MMC1 MMC Device 0 not found spl: could not find mmc device 0. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###
It looks like you tried to fix it with 0f1c1e8b368b ("arm: mach-k3: am625: Add support for UDA FS"), but it looks like it's not enough.
I confirm I reproduce the issue on AM62x SK EVM.
Beagle play seems to boot fine:
U-Boot SPL 2024.01-rc2 (Nov 09 2023 - 11:24:04 +0100) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.1--v09.01.01 (Kool Koala)') SPL initial stack usage: 13400 bytes Trying to boot from MMC1 Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted Starting ATF on ARM64 core...
NOTICE: BL31: v2.8(release):08.06.00.007 NOTICE: BL31: Built : 11:17:33, Nov 9 2023
U-Boot SPL 2024.01-rc2 (Nov 09 2023 - 11:24:30 +0100) SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.1--v09.01.01 (Kool Koala)') SPL initial stack usage: 1888 bytes Trying to boot from MMC1 Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
U-Boot 2024.01-rc2 (Nov 09 2023 - 11:24:30 +0100)
SoC: AM62X SR1.0 GP Model: BeagleBoard.org BeaglePlay DRAM: 2 GiB Core: 98 devices, 27 uclasses, devicetree: separate MMC: mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2 Loading Environment from nowhere... OK In: serial@2800000 Out: serial@2800000 Err: serial@2800000 Net: No ethernet found.
Press SPACE to abort autoboot in 2 seconds =>
Note that Beagle Play does not boot tiboot3 from UDA (User Data Area) but from mmc0boot0 so the boot flow is not exactly the same.
Thanks! Maxime
There is nothing complex here - sorry for the late response, Sync DT with v6.7-rc1 should take care of this:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ar... Vs: https://github.com/u-boot/u-boot/blob/master/arch/arm/dts/k3-am625-sk-u-boot... (notice no sdhci0 with bootph properties)
I backported that linux patch onto 2023.10 and 2024.01-rc2, both work like a charm.
Thanks! Maxime