From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bas Mevissen <abuse@basmevissen.nl>
Date: Thu, 05 Aug 2010 16:22:01 +0200
Subject: [U-Boot] Firmware upgrade possibilites technikes in uboot.
In-Reply-To: <4F4169B21905494EBD47A304F02192C9333E0BE837@XCH-HQ-01.kk.local>
References: <4F4169B21905494EBD47A304F02192C9333E0BE837@XCH-HQ-01.kk.local>
Message-ID: <2856df5375271e3a9e9a80ce66bf1d90@localhost>
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


On Thu, 5 Aug 2010 15:41:35 +0200, Lasse Skov <lasko@kk-electronic.com>
wrote:
> Hi
> 
> Im working on a target where I use the u-boot and think a little about
> good techniques for upgrade the BSP on the target and to make it fails
> saft.
> 
> Is ther any helpeful things I can use in uboot for this.?
> 
> My plan is to split my flash I 4 levels.
> 
> High
>            Filesystem
>            BSP_2
>            BSP_1
>            uBoot
> Low
> 
> And then let uBoot make a checksum on BSP_2 and boot this.
> If it's not is possible then boot BSP_1.
> 
> Another option is to build in a telnet session or something in the
> bootloader so ist possible to upgrade remote on only a Ethernet
connection.
> But it think the best is to keep the bootloader "simple".
> 
> /Lasse

You could add a command to u-boot to do checksum stuff and store the
result in an environment variable. 
Then you have the boot command be something like:

bootcmd='check_boot; bootm $(pref_bsp_addr)'

-- 
Bas.