Re: Converting to DM SERIAL for Kirkwood boards

[Stefan Roese <sr@denx.de>]

Hi Tony,

On 12/19/22 01:17, Tony Dinh wrote:
> Hi Stefan,
> 
> On Fri, Dec 16, 2022 at 1:49 PM Tony Dinh <mibodhi@gmail.com> wrote:
>>
>> Hi Stefan,
>> Yes, I also think we need Kconfig changes for Kirwood. I will try that
>> and send in patches.
>>
>> Hi Pali,
>> I hope debugging this will be a bit quicker now that I can tell that
>> it got stuck (hung or infinite loop) in nand_init() in
>> ./common/board_r.c.
>>
>> U-Boot 2023.01-rc3-00048-gc917865c7f-dirty (Dec 15 2022 - 21:20:41 -0800)
>> Pogoplug V4
>> SoC:   Kirkwood 88F6281_A1
>> Model: Cloud Engines PogoPlug Series 4
>> DRAM:  128 MiB
>> Core:  19 devices, 15 uclasses, devicetree: separate
>> NAND:
>>
> 
> As Pali suggested, I did a git bisect to track down the Pogo V4
> problem. And the result is that perhaps we missed testing commit
> 37bb396669 in rc1. If I go back one commit from this one, it is
> working fine. So I think the orion_timer itself is working very well
> with no problem.
> 
> git checkout 37bb396669b27aa62fe8bc5eeb6bfde92e09c2d3
> Previous HEAD position was 3b44b3fdf2 arm: mvebu: Add support for
> programming LD0 and LD1 eFuse
> HEAD is now at 37bb396669 timer: orion-timer: Only init timer once
> 
> This is where the Pogo V4 was frozen during boot. Among the Kirkwood
> boards that I have and used for testing, it is the only one that has
> CONFIG_BOOTSTAGE=y.

Thanks for testing and git bi-secting.

> Should I create a new post for would like to continue this topic here
> in this thread?

Let me check, if I can find the root cause and this problem quickly. If
not, then we should probably disable CONFIG_BOOTSTAGE on the Pogo v4 for
a short while until we've fixed this issue.

Thanks,
Stefan