Need Help - How to add support to a new board to meta-swupdate-boards

[Yogesh Hegde]

Hello, 

I am attempting to add Raspberry Pi 4 support to meta-swupdate-boards. I am new to swupdate and do not fully understand the inner workings of swupdate.

I started with the raspberry pi 3 example given in the meta-swupdate-boards. 

And after following the steps given 

1.  Link 1

2.  Link 2

The image generated for raspberry pi 4 got stuck at uboot.  But this got solved by following the steps given here. Now the board is no longer stuck on uboot but the kernel does not boot up. 

 

In order to debug why the kernel is not booting up, I added `console=tty1` to the kernel command line in `boot.scr` but still there are no kernel print statements printing.

1.  I suspect the kernel is not booting up due to incorrect bootargs, but I am unsure, Please can you point me in the right direction.

2.  Can you please give directions on how SWUPDATE handles bootloader configurations ? If there is no document please point me to any one example of porting which has bootloader side documented so that I can understand the error. 

Thanks in advance. 

Regards

Yogi

[Stefano Babic]

Hi Yogi,

On 17.06.21 10:20, Yogesh Hegde wrote:
> Hello,
>
> I am attempting to add Raspberry Pi 4 support to meta-swupdate-boards. I
> am new to swupdate and do not fully understand the inner workings of
> swupdate.
>
> I started with the raspberry pi 3 example given in
> the meta-swupdate-boards.
>
> And after following the steps given
> 1. Link 1

> <https://stackoverflow.com/questions/60724524/step-by-step-walk-through-on-how-to-use-swupdate-on-raspberry-pi-or-any-embedded>

This has quite nothing to do with SWUpdtae, it is how RPI4 boots, and it
looks like there is an issue with DT or with the built kernel.
Nevertheless, there are some posts regarding issues with an update
firmware (from broacom) together with U-Boot, but at first glance your
kernel or DT are not correct.

> 2. Link 2
> <https://mkrak.org/2018/01/26/updating-embedded-linux-devices-part2/>

>
> The image generated for raspberry pi 4 got stuck at uboot.  But this got
> solved by following the steps given here

> <https://groups.google.com/g/swupdate/c/R87EdIsOujU/m/6seo8d9bCAAJ>. Now

> the board is no longer stuck on uboot but the kernel does not boot up.

This was for RPI3 and it was never tested on RPI4.

>
> WhatsApp Image 2021-06-17 at 09.26.58.jpeg
> In order to debug why the kernel is not booting up, I added
> `console=tty1` to the kernel command line in `boot.scr` but still there
> are no kernel print statements printing.
>

> 1.  I suspect the kernel is not booting up due to incorrect *bootargs,
> *but I am unsure, Please can you point me in the right direction.

It is unrelated to SWUpdate - you can switch to serial line to check if
something is output, console=tty1 will work after the kernel is started
and framebuffer is available.

> 2.  Can you please give directions on how SWUPDATE handles bootloader
> configurations ? If there is no document please point me to any one
> example of porting which has bootloader side documented so that I can
> understand the error.

Again, your issue is unrelated to SWUpdate. Check how to build an image
for RPI4 on Yocto.

To answer your question:

http://sbabic.github.io/swupdate/sw-description.html#bootloader


Best regards,
Stefano Babic

>
> Thanks in advance.
>
> Regards
> Yogi
>

> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/swupdate/CA%2Bpr8UBGNouewTuD3obzVN1iSSd1Y8AV3EHgRNXShYCV2rNQyA%40mail.gmail.com
> <https://groups.google.com/d/msgid/swupdate/CA%2Bpr8UBGNouewTuD3obzVN1iSSd1Y8AV3EHgRNXShYCV2rNQyA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================

[Yogesh Hegde]

Hi Stefano,

Thanks for the quick response.

On Fri, Jun 18, 2021 at 5:49 PM Stefano Babic <sba...@denx.de> wrote:
> Hi Yogi,
>
> On 17.06.21 10:20, Yogesh Hegde wrote:
> > Hello,
> >
> > I am attempting to add Raspberry Pi 4 support to meta-swupdate-boards. I
> > am new to swupdate and do not fully understand the inner workings of
> > swupdate.
> >
> > I started with the raspberry pi 3 example given in
> > the meta-swupdate-boards.
> >
> > And after following the steps given
> > 1. Link 1
> > <https://stackoverflow.com/questions/60724524/step-by-step-walk-through-on-how-to-use-swupdate-on-raspberry-pi-or-any-embedded>
>
> This has quite nothing to do with SWUpdtae, it is how RPI4 boots, and it
> looks like there is an issue with DT or with the built kernel.
> Nevertheless, there are some posts regarding issues with an update
> firmware (from broacom) together with U-Boot, but at first glance your
> kernel or DT are not correct.

You are right.

> > 2. Link 2
> > <https://mkrak.org/2018/01/26/updating-embedded-linux-devices-part2/>
> >
> > The image generated for raspberry pi 4 got stuck at uboot. But this got
> > solved by following the steps given here
> > <https://groups.google.com/g/swupdate/c/R87EdIsOujU/m/6seo8d9bCAAJ>. Now
> > the board is no longer stuck on uboot but the kernel does not boot up.
>
> This was for RPI3 and it was never tested on RPI4.
>
> > WhatsApp Image 2021-06-17 at 09.26.58.jpeg
> > In order to debug why the kernel is not booting up, I added
> > `console=tty1` to the kernel command line in `boot.scr` but still there
> > are no kernel print statements printing.
> >
> > 1. I suspect the kernel is not booting up due to incorrect *bootargs,
> > *but I am unsure, Please can you point me in the right direction.
>
> It is unrelated to SWUpdate - you can switch to serial line to check if
> something is output, console=tty1 will work after the kernel is started
> and framebuffer is available.

Yes, you are right. It seems that the kernel which yocto compiled did
not boot up at all. Changing the kernel fixed the issue and now I have
swupdate working on raspberrypi 4.

I am still investigating which bbappend file caused the kernel to not boot up.

> > 2. Can you please give directions on how SWUPDATE handles bootloader
> > configurations ? If there is no document please point me to any one
> > example of porting which has bootloader side documented so that I can
> > understand the error.
>
> Again, your issue is unrelated to SWUpdate. Check how to build an image
> for RPI4 on Yocto.
>
> To answer your question:
>
> http://sbabic.github.io/swupdate/sw-description.html#bootloader

Thank you, for the link. It will help me understand the swupdate better.

>
> Best regards,
> Stefano Babic

Thank you for your time.

> > Thanks in advance.
> >
> > Regards
> > Yogi
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "swupdate" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to swupdate+u...@googlegroups.com
> > <mailto:swupdate+u...@googlegroups.com>.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/swupdate/CA%2Bpr8UBGNouewTuD3obzVN1iSSd1Y8AV3EHgRNXShYCV2rNQyA%40mail.gmail.com
> > <https://groups.google.com/d/msgid/swupdate/CA%2Bpr8UBGNouewTuD3obzVN1iSSd1Y8AV3EHgRNXShYCV2rNQyA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>
> --
> =====================================================================
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
> =====================================================================

Regards
Yogi