U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bas Mevissen <abuse@basmevissen.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] Firmware upgrade possibilites technikes in uboot.
Date: Thu, 05 Aug 2010 16:22:01 +0200	[thread overview]
Message-ID: <2856df5375271e3a9e9a80ce66bf1d90@localhost> (raw)
In-Reply-To: <4F4169B21905494EBD47A304F02192C9333E0BE837@XCH-HQ-01.kk.local>


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.

  reply	other threads:[~2010-08-05 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-05 13:41 [U-Boot] Firmware upgrade possibilites technikes in uboot Lasse Skov
2010-08-05 14:22 ` Bas Mevissen [this message]
2010-08-05 15:02   ` Albert ARIBAUD
2010-08-05 15:31     ` Bas Mevissen
2010-08-05 18:13       ` Wolfgang Denk

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=2856df5375271e3a9e9a80ce66bf1d90@localhost \
    --to=abuse@basmevissen.nl \
    --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