[External]Re: Uboot upgrade from 2016 to 2020

[Sinan Akman]

Hi Alex

On 2025-10-16 10:42, Manea, Alexandru (Alexandru) wrote:
>
> Hi Sinan,
>
> We have a very limited supply of boards, maybe one we have everything 
> ongoing we could arrange for one.
>
> Is there anything I can provide so you could help me out a bit? I’m 
> stuck with this hanging situation and I’m running out of idea why it’s 
> not working…as it matches most of the old working uboot settings…
>
>
> Regards,
>
> Alex
>
> *From:*Sinan Akman <sinan at writeme.com>
> *Sent:* Thursday, October 16, 2025 5:39 PM
> *To:* Manea, Alexandru (Alexandru) **CTR** <amanea at avaya.com>; Tom 
> Rini <trini at konsulko.com>
> *Cc:* u-boot at lists.denx.de
> *Subject:* Re: [External]Re: Uboot upgrade from 2016 to 2020
>
> Hi Alex On 2025-10-16 01: 26, Manea, Alexandru (Alexandru) wrote: > Hi 
> Sinan, > > First thanks for replying. I do hope you will be able to 
> help me a bit. > The board is PPCE5500 used for Avaya IP500L platform. 
> > > What I noticed
>
> Hi Alex
> On 2025-10-16 01:26, Manea, Alexandru (Alexandru) wrote:
> > Hi Sinan,
> > 
> > First thanks for replying. I do hope you will be able to help me a bit.
> > The board is PPCE5500 used for Avaya IP500L platform.
> > 
> > What I noticed for hanging is that it hangs when setting mtspr    IVPR, r0 in start.s although this seems correct: CONFIG_SYS_MONITOR_BASE at h
> > 
> > Regards,
> > Alex
> > 
> > From: Sinan Akman <sinan at writeme.com>
> > Sent: Thursday, October 16, 2025 3:00 AM
> > To: Tom Rini <trini at konsulko.com>; Manea, Alexandru (Alexandru) **CTR** 
> <amanea at avaya.com>
> > Cc: u-boot at lists.denx.de
> > Subject: [External]Re: Uboot upgrade from 2016 to 2020
> > 
> > [External Sender]
> > Hi Alexandru On 2025-10-15 18: 19, Tom Rini wrote: > On Tue, Oct 14, 2025 at 10: 21: 37AM +0000, Manea, Alexandru (Alexandru) wrote: > >> Hi, >> >> I have an issue with upgrading our sources to use the 2020. 04 uboot rather
> > 
> > 
> > Hi Alexandru
> > 
> > 
> > 
> > On 2025-10-15 18:19, Tom Rini wrote:
> > 
> >> On Tue, Oct 14, 2025 at 10:21:37AM +0000, Manea, Alexandru (Alexandru) wrote:
> > 
> >>
> > 
> >>> Hi,
> > 
> >>>
> > 
> >>> I have an issue with upgrading our sources to use the 2020.04 uboot rather than the one working now on our system which is 2016.
> > 
> >>> After adding all our board changes, I can see the SPL loading and setting DDR and TLB entries but once it tries to jump to uboot from mmc_boot() it hangs and I can't get to see anything...has anyone encountered this? Is there something I can do to make sure uboot is actually being jumped to or why the hang? I've set the offsets to go to the _start_e500: instructions like the old uboot. I can share the traces I have if needed. Looking forward to an answer.
> > 
> >>
> > 
> >> There might have been some issue with certain PowerPC platforms
> > 
> >> introduced after the v2016.xx releases and fixed later than v2020.04,
> > 
> >> and git log might help. Of course, it would be better still if you could
> > 
> >> move to current mainline and then help with PowerPC maintenance, as we
> > 
> >> do need more people helping there. Thanks.
> > 
> >>
> > 
> > 
> > 
> > 
> > 
> > Which board is this for ?
> > 
> I don't have access to P50x0 or T10x0 boards to test and debug this
> but I might try to see if I can get my hands on a T1040RDB or one of
> your boards (e.g. IP500L). As Tom mentioned any help you can provide
> is definitely very welcome here in this area.

First a minor thing : we don't really top post in discussions here. We 
provide
our comments after quoting the others. It helps to have good flow and
also this is part of the etiquette so please consider not to top post.

For debugging, what I suggest is that you bisect the mainline u-boot tree
to find the commit point (or set of commits) that the break you are 
observing
happened.

Once you find where the break happened you can try to understand what
this commit was trying to do and why it caused the break. With this you
can provide a new patch to fix the problem.

You would probably also need to do some debugging at the board level.
For this I would recommend to use a JTAG debugger like BDI3000 (or
others). You might have one already in house or in the case of BDI3000
you might be able to find a used one.

Finally, I suggest to start a new discussion with all your findings and for
a potential patch ides. While doing this please use a better subject line
indicating clearly what architecture/platform this is related.

I am also cc'ing now Priyanka Jain as I believe the name shows as the
maintainer now for some of the NXP e5500 boards.

Hope this helps. Enjoy u-boot debugging and thanks for all your help.

-- sinan