Re: [RAUC] Robust u-boot environment with RAUC

["Enrico Jörns" <ejo@pengutronix.de>]

Am Donnerstag, dem 25.03.2021 um 16:52 +0100 schrieb Jan Lübbe:
> Hi,
> 
> On Thu, 2021-03-25 at 15:22 +0000, Einar Vading wrote:
> > We have a Raspberry Pi 4 system set up using RAUC for updates and u-boot for
> > booting. For some systems in the field we have the u-boot environment on the
> > FAT boot partition and we mount that in fstab so that RAUC can access it with
> > the fw_print/setenv commands.
> > 
> > One issue we have seen is that the env-file gets corrupted every now and then.
> > After corruption we can't RAUC update. The only solution we have to this
> > problem now is to delete the corrupted env-file and reboot, then we can
> > perform the upgrade.
> > 
> > I have no idea how to track down whatever corrupts the file and I was
> > wondering if anyone has any input.
> 
> You could try placing the environment on a separate partition to avoid any
> potential issues in the FAT implementation. Also, I think U-Boot has a way to
> support redundant environments.

Exactly. This should also be documented in the U-Boot integration guideline for
eMMC:

https://rauc.readthedocs.io/en/latest/integration.html#example-setting-up-u-boot-environment-on-emmc-sd-card

When writing to the FAT very short before hard rebooting, I could imagine this
can lead to failures. Do you see the corruption only after updates, or also
suddenly after n boots?

How does the system report the corruption?


Regards, Enrico

> Regards,
> Jan

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |


_______________________________________________
RAUC mailing list