raspberrypi cm3 v2019.07 not working

Belisko Marek marek.belisko at gmail.com
Tue May 12 13:00:20 CEST 2020


On Tue, May 12, 2020 at 12:51 PM Matthias Brugger <mbrugger at suse.com> wrote:
>
>
>
> On 12/05/2020 11:15, Belisko Marek wrote:
> > On Fri, May 8, 2020 at 11:39 PM Belisko Marek <marek.belisko at gmail.com> wrote:
> >>
> >> Hi Matthias,
> >>
> >> On Fri, May 8, 2020 at 11:28 PM Matthias Brugger <mbrugger at suse.com> wrote:
> >>>
> >>> Hi Marek,
> >>>
> >>> On 08/05/2020 21:52, Belisko Marek wrote:
> >>>> On Wed, May 6, 2020 at 11:02 PM Belisko Marek <marek.belisko at gmail.com> wrote:
> >>>>>
> >>>>> On Tue, May 5, 2020 at 10:18 PM Belisko Marek <marek.belisko at gmail.com> wrote:
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> I'm trying to run 2019.07 u-boot on raspberrypi cm3 module but I got
> >>>>>> no feedback on console. When used 2018.01 it boots fine. Probably I
> >>>>>> need to do git bisect but maybe someone have some idea or experience
> >>>>>> what can cause that. Thanks.
> >>>>> I give a try 2020.01 and I got only this:
> >>>>> U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000)
> >>>>>
> >>>>> DRAM:  948 MiB
> >>>>> RPI Compute Module 3 (0xa020a0)
> >>>>>
> >>>>> I'll try to debug it and let you know.
> >>>> Debug messages shows this:
> >>>> https://pastebin.com/2SwNzrb1
> >>>>
> >>>> I tried to debug but I have no clue what is going one there.
> >>>>
> >>>> Also u-boot 2019.07 is not working at all on cm3 due to this commit
> >>>> (after bisect when reverted u-boot start working again):
> >>>> 143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device
> >>>> tree sources to Linux 5.1-rc6 state
> >>>>
> >>>> Any ideas hint how to resolve this issue? Thanks.
> >>>>
> >>>
> >>> Can you try to cherry-pick the following two patches to your tree:
> >>> 5051377a0b ("arm: dts: bcm283x: Rename U-Boot file")
> >>> 89e47e8eb6 ("fdt: fix bcm283x dm-pre-reloc definitions")
> >> But those are present in 2020.01 and this version at least print
> >> something to console but stuck somewhere (pls see pastebin log with
> >> debug enabled)
> >> I prefer to run 2020.01 ;). Thanks.
> > Any other stuff I can try to make it working in 2020.01? Could that be
> > firmware issue somehow? Thanks.
>
> Sorry I didn't realized that your first try was with 2020.01.
> I just confirmed that it acutually does not boot. As a shortcut, do you know
> which is the last working version of U-Boot?
v2019.07 with reverted  commit :
143256b353c4d2ad1cf5e5e63b38410188b35e49 - fdt: update bcm283x device
tree sources to Linux 5.1-rc6 state
work fine. Without revert it shows anything on console. So something
between 2019.07..2020.01 mus fix it partially ;)
>
> Regards,
> Matthias

BR,

marek


More information about the U-Boot mailing list