From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Stile <john@stilen.com>
Date: Thu, 17 Jan 2013 13:40:55 -0800
Subject: [U-Boot] designing a firmware update mechanism
Message-ID: <1358458855.32266.43.camel@genx>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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?