linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Failsafe bootloader
Date: Tue, 3 Jun 2003 21:28:51 +0200	[thread overview]
Message-ID: <20030603192851.GA1921@mars.ravnborg.org> (raw)


Hi all.

We are developing an application for an embedded target that will be
located in some rural areas. We foresee a need to update the target
with a new version of the application or a new kernel from time to time.

A few of the added requirements on top of that are:
1) The target shall boot up in the old kernel, if a bogus kernel is loaded
2) The target shall boot up in the old application, if a bogus
	application is loaded
3) On the management side an update shall be handled as a single file,
	the target may decide to 'unpack' it when received.

We have looked all over the net, but none of the bootloaders found
so far could meet the above demands.
The boot loaders usually have an interactive mode used to select
between different configurations - and there are no feedback from
the application side if the reboot actually went well.
The interactiviness does not fit well with an embedded target.

Do you know of a boot loader that partially or fully meets the above
requirements?

Background information
Today we are using VxWorks - for which we have made our own boot loader.
The boot laoder allows the boot loader itself, and the application part
to be upgraded - and if a restart is failed the old version will
be activated on a subsequent build.
I want the same behaviour in the Linux based target.

	Thanks in advance,

	Sam

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-06-03 19:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 19:28 Sam Ravnborg [this message]
2003-06-03 19:47 ` Failsafe bootloader Mark Hatle
2003-06-03 20:07   ` Wolfgang Denk
2003-06-03 20:05 ` Wolfgang Denk
     [not found] <00047C13.C22236@ravnborg.org>
2003-06-03 20:10 ` Jerry Van Baren
2003-06-03 21:51   ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-06-04  6:47 Darin.Johnson
2003-06-04 10:16 ` Magnus Damm
     [not found] <00048074.C22236@opensource.se>
2003-06-04 12:04 ` Jerry Van Baren
2003-06-04 12:33 Darin.Johnson
     [not found] <00048177.C22236@nokia.com>
2003-06-04 12:54 ` Jerry Van Baren
2003-06-04 13:15 Johnson, Stephen
2003-06-04 14:11 ` Wolfgang Denk
2003-06-04 13:51 Callebaut Benoit
2003-06-04 14: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=20030603192851.GA1921@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).