On February 9, 2026 thus sayeth Francesco Dolcini: > On Mon, Feb 09, 2026 at 11:16:35AM +0100, Francesco Dolcini wrote: > > On Mon, Feb 09, 2026 at 03:38:51PM +0530, Suhaas Joshi wrote: > > > On 09:45-20260209, Francesco Dolcini wrote: > > > > + Bryan, Anshul > > > > > > > > On Mon, Feb 09, 2026 at 09:38:55AM +0100, Francesco Dolcini wrote: > > > > > Verdin AM62 and AM62P are not booting anymore with U-Boot > > > > > 42b3ee7fa524, > > > > > everything was fine with b5213bbfdcb1. > > > > > > > > > > Looking at the commits between the two revision, I would say that the > > > > > issue is with this series > > > > > https://lore.kernel.org/all/[email protected]/ > > > > > > > > We have also commit 3382d75f7a6c ("arch: arm: dts: k3: refactor common > > > > nodes to k3-*-r5.dtsi") that might be the root cause for this issue. > > > > > > > > > > Hi Francesco. Unfortunately, I don't have Verdin line of boards with me, > > > so I cannot reproduce this issue. This is also why I wasn't able to test > > > my series on my end and had requested board-specific maintainers do the > > > same. > > > > > > Since I don't have the boards, could you run the following test to help > > > us ascertain which of the 2 suspected commits actually broke the boot? > > > > > > * First drop my AM625 Verdin patch, and compile and copy the binaries, > > > and boot. > > > * Then let my patch remain in the tree, and remove Anshul's refactor > > > patch, and try the same thing again. > > > > > > This could help us ascertain which commit broke boot, and we can try > > > fixing from that commit. > > > > Sure, I can bisect it. > > > > Do this difference in the logs > > > > Failed to set clock rates for '/a53@0': -22 > > > > vs > > > > Failed to set clock rates for '/a53@0': -61 > > > > ring any bell? > > The boot failure start with commit 2ffab9da9142 ("Merge patch series > "Firewall ATF and OP-TEE memory regions in Sitara""). > > With commit 24338c81ec2f ("arm: dts: k3-binman: Use configs for > ATF/OPTEE addresses") the board still boots fine. > I have some concern that this commit is changing something, however > CONFIG_K3_ATF_LOAD_ADDR is 0x80000000, while before in the dtsi file it > was 0x70000000. I tried changing it back without any positive result, > I just got an EL3 exception. > > Any more test I should do? >
Do you mind copying a boot log to a pastebin for me? I thought I had one of these boards but I'm still digging around for it. 0x80000000 should be where we load TFA now days unless some boards have opted out of letting U-Boot move it to the bottom of DRAM ~Bryan
