From: Thomas Lange <thomas@corelatus.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Field upgrade
Date: Tue, 02 Dec 2003 23:44:29 +0100 [thread overview]
Message-ID: <3FCD15CD.4010209@corelatus.com> (raw)
In-Reply-To: <20031202220143.15ACFC5F5F@atlas.denx.de>
We dont upgrade miniboot. It is so simple, we never
have to upgrade it. It does not touch any cpu registers,
memory configuration and such stuff.
It only scans the flash for an image with correct crc
and starts it.
During the past two years, we have upgraded ppcboot/u-boot
on live systems several times to add functionality, correct bugs
etc.
But miniboot is the same.
All advanced stuff is done by u-boot. Shipping a system to a customer
without a possibility to upgrade u-boot without risking a dead card
is not an option IMHO.
/Thomas
Wolfgang Denk wrote:
> In message <3FCD0356.30502@corelatus.com> you wrote:
>
>>Sure there is a sw solution! We have been using it for
>>2 years now. Check out board "gth".
>>
>>We use a pre loader called miniboot, which boots the first
>>image with correct crc it finds in flash.
>
>
> You are just shifting the problem to a diferent level, actually
> adding MORE complexity.
>
> Just one question: How do you reliably field upgrade the "miniboot"
> image running on your board?
>
> Best regards,
>
> Wolfgang Denk
>
next prev parent reply other threads:[~2003-12-02 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 14:39 [U-Boot-Users] Field upgrade Chris Simmonds
2003-12-02 15:15 ` Wolfgang Denk
2003-12-02 21:25 ` Thomas Lange
2003-12-02 22:01 ` Wolfgang Denk
2003-12-02 22:44 ` Thomas Lange [this message]
2003-12-02 22:59 ` Wolfgang Denk
2003-12-02 23:53 ` Thomas Lange
2003-12-03 0:29 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 16:10 Callebaut, Benoit
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=3FCD15CD.4010209@corelatus.com \
--to=thomas@corelatus.com \
--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