From: Magnus Damm <damm@opensource.se>
To: Darin.Johnson@nokia.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Failsafe bootloader
Date: Wed, 4 Jun 2003 12:16:28 +0200 [thread overview]
Message-ID: <20030604121628.7d042138.damm@opensource.se> (raw)
In-Reply-To: <F0B628F30F48064289D8CCC1EE21B7A8012E39C8@mvebe001.americas.nokia.com>
On Tue, 3 Jun 2003 23:47:22 -0700
Darin.Johnson@nokia.com wrote:
> It also could be very nice if you could upgrade the lowest level of software, the boot loader or system initializer (ppcboot, etc). We had found a bug in our loader at one point, and because many registers are "write once" it was difficult to fix these settings from the application software. But finding a foolproof and reliable way to upgrade the boot loader software is difficult, especially if you are relying on customers and operators to do the upgrading.
And that's why you should use Miniboot as your first bootloader. =)
It's not upgradeable itself, but it is used to load and update a
secondary bootloader. Miniboot itself should be very small and simple
to keep the number of bugs low. It only requires the internal memory
of the mpc8xx so almost all hardware initialization is made
after miniboot has run, and therefore is upgradeable.
Need to upgrade your hardware configuration?
No problem as long as you haven't changed CS0 or your SMC... =)
And yes, it runs with watchdog on and leaves that configuration
up to the secondary bootloader.
http://opensource.se/projects/miniboot/index.html
However, the number of boards / processors supported are limited at the moment.
I've also heard that uboot/ppcboot could be used to update itself, but I've never
tested it myself.
/ magnus
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-04 10:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 6:47 Failsafe bootloader Darin.Johnson
2003-06-04 10:16 ` Magnus Damm [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-04 13:51 Callebaut Benoit
2003-06-04 14:13 ` Wolfgang Denk
2003-06-04 13:15 Johnson, Stephen
2003-06-04 14:11 ` Wolfgang Denk
[not found] <00048177.C22236@nokia.com>
2003-06-04 12:54 ` Jerry Van Baren
2003-06-04 12:33 Darin.Johnson
[not found] <00048074.C22236@opensource.se>
2003-06-04 12:04 ` Jerry Van Baren
[not found] <00047C13.C22236@ravnborg.org>
2003-06-03 20:10 ` Jerry Van Baren
2003-06-03 21:51 ` Wolfgang Denk
2003-06-03 19:28 Sam Ravnborg
2003-06-03 19:47 ` Mark Hatle
2003-06-03 20:07 ` Wolfgang Denk
2003-06-03 20:05 ` 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=20030604121628.7d042138.damm@opensource.se \
--to=damm@opensource.se \
--cc=Darin.Johnson@nokia.com \
--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).