Hi Robert, all,
I finally came across to testing this again. A more careful comparison
between Robert's build script and mine showed that my build of
trusted-firmware-a was missing the parameter
PRELOADED_BL33_BASE=0x82000000. Once I specified that parameter, u-boot
would fully start up.
Next, I applied this patch series to the current u-boot and reran my
build script. The output proceeded a little further, but it would hang
in the middle of U-boot initialization:
--- snip ---
U-Boot SPL 2026.07-rc1 (May 11 2026 - 17:57:58 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.5--v11.02.05 (Fancy Rat)')
Set clock rates for '/a53@0', CPU: 1250MHz at Speed Grade 'T'
SPL initial stack usage: 13464 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
U-Boot SPL 2026.07-rc1 (May 11 2026 - 17:58:12 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.5--v11.02.05 (Fancy Rat)')
SPL initial stack usage: 2048 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
U-Boot 2026.07-rc1 (May 11 2026 - 17:58:12 +0000)
SoC: AM62X SR1.0 HS-FS
Reset reason: POR
Model: BeagleBoard.org PocketBeagle2
DRAM: 448 MiB (total 512 MiB)
--- snip ---
When I compiled Robert's version of u-boot
(ef03e35488377a32cdd4f76d1a03ef7f60c798ef from January 30), I would land
in a menu like this:
--- snip ---
U-Boot 2026.01 (May 11 2026 - 17:38:46 +0000)
SoC: AM62X SR1.0 HS-FS
Reset reason: POR
Model: BeagleBoard.org PocketBeagle2
DRAM: 512 MiB
Core: 89 devices, 32 uclasses, devicetree: separate
MMC: mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In: serial@2860000
Out: serial@2860000
Err: serial@2860000
Net: No ethernet found.
Press SPACE to abort autoboot in 0 seconds
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'uEnv.txt'
Scanning for bootflows in all bootdevs
Seq Method State Uclass Part Name Filename
--- ----------- ------ -------- ---- ------------------------
----------------
Scanning bootdev '[email protected]':
0 extlinux ready mmc 1 [email protected]_
/extlinux/extlinux.conf
** Booting bootflow '[email protected]_1' with extlinux
PocketBeagle 2 microSD (extlinux.conf) (swap enabled)
1: microSD (failsafe)
2: copy microSD to eMMC
3: microSD (debug)
4: microSD (default)
5: techlab
6: techlab workshop
Enter choice:
--- snip ---
Should I apply the patch set to an older revision of U-boot? As far as I
can tell, it may now be hanging related to some DRAM layout or device
tree mismatch.
Marko
