From: John Stile <john@stilen.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] designing a firmware update mechanism
Date: Thu, 17 Jan 2013 13:40:55 -0800 [thread overview]
Message-ID: <1358458855.32266.43.camel@genx> (raw)
I have an embedded project using an atmel arm processor, primary
bootloader at91BootStrap on NOR to call uboot (and the reset of the
system) on NAND.
I am trying to devise a way to partition NAND redundantly, with 2 copies
of (uboot + uboot-env + kernel + roofs).
At91bootstrap will have to decide which uboot to start some how. I have
not determined this yet, but I think reading something out of the two
uboot-env areas might be a good start.
Will I need to compile 2 versions of uboot, differing only in where to
look for the uboot-env, or is there another way?
I don't think giving one copy of uboot 2 uboot-env will do the trick.
Could anyone share a firmware update strategy with me that uses uboot,
or is that outside the scope of this list?
reply other threads:[~2013-01-17 21:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1358458855.32266.43.camel@genx \
--to=john@stilen.com \
--cc=u-boot@lists.denx.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