From: Einar Vading <Einar.Vading@RHIMagnesita.com>
To: "rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: [RAUC] Robust u-boot environment with RAUC
Date: Thu, 25 Mar 2021 15:22:53 +0000 [thread overview]
Message-ID: <AM0PR08MB45802E04BF39F513E949C4D8E5629@AM0PR08MB4580.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 948 bytes --]
Hi,
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.
Vänliga hälsningar / Best Regards
Einar Vading
Software Developer AGELLIS AB
[cid:08b60f59-61a0-41f4-8a02-48d7f47c2730]
T +46 73 420 76 81
Agellis Group AB
Tellusgatan 15,
SE-224 57, Lund, Sweden
www.agellis.com<http://www.agellis.com/>; www.rhimagnesita.com<http://www.rhimagnesita.com/>
[-- Attachment #1.1.2: Type: text/html, Size: 4543 bytes --]
[-- Attachment #1.2: Outlook-ggtizjsb.png --]
[-- Type: image/png, Size: 10716 bytes --]
[-- Attachment #2: Type: text/plain, Size: 66 bytes --]
_______________________________________________
RAUC mailing list
next reply other threads:[~2021-03-25 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 15:22 Einar Vading [this message]
2021-03-25 15:52 ` Jan Lübbe
2021-03-25 18:54 ` Enrico Jörns
2021-03-26 5:48 ` [RAUC] [NEWSLETTER]Re: " Einar Vading
2021-03-26 9:13 ` Jan Lübbe
2021-03-28 10:11 ` Einar Vading
2021-03-28 14:11 ` Matt Campbell
2021-03-28 20:23 ` [RAUC] [NEWSLETTER]Re: " Einar Vading
2021-03-29 5:14 ` Einar Vading
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=AM0PR08MB45802E04BF39F513E949C4D8E5629@AM0PR08MB4580.eurprd08.prod.outlook.com \
--to=einar.vading@rhimagnesita.com \
--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