U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Marko Mäkelä" <marko.makela@iki.fi>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Randolph Sapp <rs@ti.com>,
	Erik Welsh <Erik.Welsh@octavosystems.com>,
	Anshul Dalal <anshuld@ti.com>,
	bb@ti.com, nm@ti.com, trini@konsulko.com, afd@ti.com,
	u-boot@lists.denx.de
Subject: Re: [PATCH 2/3] k3-am62-pocketbeagle2: add initial board support
Date: Tue, 12 May 2026 09:10:07 +0300	[thread overview]
Message-ID: <agLEP74BpPCIFbrd@kehys.lan> (raw)
In-Reply-To: <agIcJSyF5vf99ouY@kehys.lan>

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

  reply	other threads:[~2026-05-12  6:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 22:37 [PATCH 0/3] k3-am62-pocketbeagle2: add board and variant support rs
2026-03-17 22:37 ` [PATCH 1/3] arm: mach-k3: am62: add &main_uart6 to clock and pwr tree rs
2026-03-17 22:37 ` [PATCH 2/3] k3-am62-pocketbeagle2: add initial board support rs
2026-03-20  9:29   ` Anshul Dalal
2026-03-20 15:32     ` Robert Nelson
2026-03-23 19:37       ` Randolph Sapp
2026-03-23 19:46         ` Robert Nelson
2026-03-26  0:34           ` Randolph Sapp
2026-03-26 23:23             ` Randolph Sapp
2026-03-27 14:25               ` Marko Mäkelä
2026-03-27 14:53                 ` Robert Nelson
2026-03-27 19:15                   ` Marko Mäkelä
2026-03-28  8:18                     ` Marko Mäkelä
2026-03-28 16:39                       ` Robert Nelson
2026-03-29 17:13                         ` Marko Mäkelä
2026-03-30 14:41                           ` Robert Nelson
2026-04-18 15:02                         ` Marko Mäkelä
2026-04-18 17:53                           ` Robert Nelson
2026-04-19 13:54                             ` Marko Mäkelä
2026-04-19 15:08                               ` Robert Nelson
2026-04-20 18:20                                 ` Marko Mäkelä
2026-05-11 18:12                                   ` Marko Mäkelä
2026-05-12  6:10                                     ` Marko Mäkelä [this message]
2026-03-30 23:57               ` Randolph Sapp
2026-03-31 16:13                 ` Robert Nelson
2026-03-31 22:54                   ` Randolph Sapp
2026-03-17 22:38 ` [PATCH 3/3] k3-am62-pocketbeagle2: add support for 1GB variant rs
2026-03-20 10:10   ` Anshul Dalal
2026-03-20 15:26     ` Robert Nelson
2026-03-23 18:38       ` Randolph Sapp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=agLEP74BpPCIFbrd@kehys.lan \
    --to=marko.makela@iki.fi \
    --cc=Erik.Welsh@octavosystems.com \
    --cc=afd@ti.com \
    --cc=anshuld@ti.com \
    --cc=bb@ti.com \
    --cc=nm@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=rs@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox