This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: RedBoot porting
- To: 'Jesper Skov' <jskov at redhat dot com>, Andrew Lunn <andrew dot lunn at ascom dot ch>
- Subject: RE: [ECOS] RedBoot porting
- From: Doug Fraser <dfraser at photuris dot com>
- Date: Mon, 8 Jan 2001 07:30:22 -0500
- Cc: Grant Edwards <grante at visi dot com>, ecos-discuss at sources dot redhat dot com
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
>