From: Michael Tretter <m.tretter@pengutronix.de>
To: Martin Hollingsworth <Martin.Hollingsworth@itk-engineering.de>
Cc: "rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] boot-mbr-switch from u-boot
Date: Thu, 26 Nov 2020 12:20:01 +0100 [thread overview]
Message-ID: <20201126112001.GD9315@pengutronix.de> (raw)
In-Reply-To: <d683cd3f33d949589ae80f97af3a7681@itk-engineering.de>
Hello Martin,
On Thu, 26 Nov 2020 08:57:49 +0000, Martin Hollingsworth wrote:
> I am integrating RAUC into a Xilinx ZynqMP device and using boot-mbr-switch
> method according to documentation chapter 7.6.2. Bootloader is u-boot, RAUC
> u-boot scripts are from contrib/uboot.sh, RAUC is v1.2 (upgrade planned).
>
> When switching between slots from within u-boot the MBR partition table is
> not altered. So when installing a new system (inclduing new bootloader
> partition content) which doesn't boot 3 times, after the fallback we run the
> new bootloader partition with the old rootfs. Do I understand this from the
> source code correctly?
Correct.
>
> In my opinion this is a major problem, because on Xilinx ZynqMP the
> bootloader partition contains the Xilinx bootbin, a first stage bootloader
> which flashes the FPGA firmware before starting u-boot. In this case we run
> the old linux against a new FPGA and have an inconsistent system after the
> RAUC fallback.
How do you tell Linux, what is contained in the FPGA firmware? Linux should
not make any assumptions about the loaded FPGA firmware.
>
> Does anyone have a solution for this problem?
There are a few solutions:
You could use a different mechanism to load the firmware. Instead of the
boot.bin, put the bitstream into the rootfs (or another partition) and load it
from the bootloader (I'm not sure, if U-Boot supports this, but Barebox does.)
or from Linux.
If it is mandatory to load the firmware from the FSBL (or the bootloader
partition in general), you would need a means to tell Linux, which firmware
was loaded. That information has to be stored in the updated bootloader
partition.
Michael
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2020-11-26 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 8:57 Martin Hollingsworth
2020-11-26 11:20 ` Michael Tretter [this message]
2020-11-26 12:18 ` Martin Hollingsworth
2020-11-26 14:00 ` Jan Lübbe
2020-11-27 15:21 ` Martin Hollingsworth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201126112001.GD9315@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=Martin.Hollingsworth@itk-engineering.de \
--cc=rauc@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox