From: Philip Downer <pdowner@prospero-tech.com>
To: rauc@pengutronix.de
Subject: [RAUC] Understanding u-boot integration
Date: Tue, 25 Apr 2017 14:43:41 +0100 [thread overview]
Message-ID: <CAE6wzSLwyMbGkcoEiBdgqbcL9igO3WWbawEpLdmiOpPGJ1mycA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]
After seeing a presentation on RAUC at FOSDEM I've been looking to
integrate it with a Yocto based i.mx6 embedded system that I'm working on.
Everything is pretty much working but I'm just trying to understand the
integration with u-boot, I've based my u-boot scripts on the one in contrib
from the RAUC repository. I've had to make some changes due to an old
version of u-boot and quirks of our setup, however my questions are about
the general process.
As I understand it, when the system boots, the first slot from BOOT_ORDER
will be selected, say slot A. Then BOOT_A_LEFT will be decremented from 3
to 2 and we will save the environment to nand flash. Is it then intended
that when the OS boots successfully it should change the BOOT_A_LEFT
variable in nand flash back to 3?
Following on from that, if I'm correct, this seems like a lot of writes to
nand flash. Writing to nand is also not that quick for us at 3.41 seconds
from within Linux, is there not a reasonable chance of corruption if the
system was reset during that write?
--
Philip Downer
+44 (0)7879 470 969
pdowner@prospero-tech.com
[-- Attachment #1.2: Type: text/html, Size: 1424 bytes --]
[-- Attachment #2: Type: text/plain, Size: 65 bytes --]
_______________________________________________
RAUC mailing list
next reply other threads:[~2017-04-25 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 13:43 Philip Downer [this message]
2017-05-03 6:11 ` Enrico Joerns
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=CAE6wzSLwyMbGkcoEiBdgqbcL9igO3WWbawEpLdmiOpPGJ1mycA@mail.gmail.com \
--to=pdowner@prospero-tech.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