Mon, May 11, 2026 at 09:12:53PM +0300, Marko Mäkelä wrote:
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)
I tried applying this patch series to the U-boot release tags v2026.01
as well as v2026.04. On the former, the compilation would fail due to a
missing file:
arch/arm/dts/.k3-am62-r5-pocketbeagle2.dtb.pre.tmp:15:10: fatal error:
k3-am625-r5.dtsi: No such file or directory
15 | #include "k3-am625-r5.dtsi"
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.lib:421:
arch/arm/dts/k3-am62-r5-pocketbeagle2.dtb] Error 1
On the latter, the boot hangs just like it did on top of v2026-07-rc2~5
that I had used last night:
U-Boot 2026.04 (May 12 2026 - 05:40:25 +0000)
SoC: AM62X SR1.0 HS-FS
Reset reason: POR
Model: BeagleBoard.org PocketBeagle2
DRAM: 448 MiB (total 512 MiB)
When I built v2026-07 and this patchset (exactly the same source code)
using the build_u-boot.sh script in
https://github.com/beagleboard/u-boot-pocketbeagle2/ instead of my own
code I got some panic output at the crash point. I tried it 3 times and
got similar output each time. I did not check how the build options
would differ from my own script, for which the boot just silently hung:
U-Boot 2026.04 (May 12 2026 - 05:54:06 +0000)
SoC: AM62X SR1.0 HS-FS
Reset reason: POR
Model: BeagleBoard.org PocketBeagle2
DRAM: 448 MiB (total 512 MiB)
PANIC in EL3.
x30 = 0x00000000800047f4
x0 = 0x0000000002860000
...
sp_el0 = 0x000000008000c520
...
Could it be a stack overrun or a clash between heap and stack? There are
several register values pointing to higher addresses than sp_el0. Should
the stack pointer be initialized at a different address?
Best regards,
Marko
