From: Doug Fraser <dfraser@photuris.com>
To: 'Jesper Skov' <jskov@redhat.com>, Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Grant Edwards <grante@visi.com>, ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] RedBoot porting
Date: Mon, 08 Jan 2001 04:36:00 -0000 [thread overview]
Message-ID: <E2D27064CD59574F88D05AEF5728396D01E5E2@PH01SRV02.photuris.com> (raw)
Then RedBoot becomes a chunk of the application at that
point. What I want then, I guess, is two copies of 'RedBoot'.
An immutable copy in FLASH that provides recovery of a dead board
and a runtime copy that contains the callbacks for the OS.
The runtime copy is normally copied to RAM and run there. The
FLASH copy is just used to network boot an image if the rest
of my FLASH is dead (for development). I plan on two application
regions of FLASH to provide failsafe remote updates. The
bootstrap picks the image to load based on CRC sanity. Updates
load and verify one section before erasing the second.
Does the above sound reasonable?
Doug
> -----Original Message-----
> From: Jesper Skov [ mailto:jskov@redhat.com ]
> Sent: Monday, January 08, 2001 6:05 AM
> To: Andrew Lunn
> Cc: Jesper Skov; Grant Edwards; ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] RedBoot porting
>
<snip>
> This should work already for targets that support it. Adding the
> support to new targets it relatively simple (only really requires PIC
> startup code that initializes the system, copies everything to RAM and
> jumps there). Remember, RedBoot _is_ just an application (as far as I
> know, anyway).
>
> Jesper
>
next reply other threads:[~2001-01-08 4:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 4:36 Doug Fraser [this message]
2001-01-08 4:54 ` Jesper Skov
2001-01-08 7:34 ` Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 2:55 [ECOS] redboot porting yu weiping
[not found] <20010108171508.U10158@biferten.ma.tech.ascom.ch>
[not found] ` <XFMail.20010108095423.gthomas@redhat.com>
2001-01-09 0:50 ` [ECOS] RedBoot porting Andrew Lunn
2001-01-09 8:57 ` Grant Edwards
2001-01-09 9:05 ` Andrew Lunn
2001-01-09 9:12 ` Grant Edwards
2001-01-09 9:09 ` Gary Thomas
2001-01-09 9:24 ` Grant Edwards
2001-01-09 9:47 ` Andrew Lunn
2001-01-09 10:08 ` Lewin A.R.W. Edwards
2001-01-09 10:30 ` Grant Edwards
2001-01-09 10:39 ` Andrew Lunn
2001-01-09 11:24 ` Grant Edwards
2001-01-08 5:32 Doug Fraser
2001-01-05 9:49 Grant Edwards
2001-01-05 15:41 ` Jonathan Larmour
2001-01-08 0:08 ` Jesper Skov
2001-01-08 0:29 ` Andrew Lunn
2001-01-08 1:09 ` Jesper Skov
2001-01-08 2:36 ` Andrew Lunn
2001-01-08 3:04 ` Jesper Skov
2001-01-08 7:31 ` Grant Edwards
2001-01-08 7:40 ` Lewin A.R.W. Edwards
2001-01-08 8:24 ` Grant Edwards
2001-01-08 7:42 ` Gary Thomas
2001-01-08 7:57 ` Grant Edwards
2001-01-08 7:59 ` Andrew Lunn
2001-01-08 8:07 ` Gary Thomas
2001-01-08 14:42 ` Grant Edwards
2001-01-08 16:26 ` Gary Thomas
2001-01-09 7:33 ` Grant Edwards
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=E2D27064CD59574F88D05AEF5728396D01E5E2@PH01SRV02.photuris.com \
--to=dfraser@photuris.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.com \
--cc=jskov@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).