This is the mail archive of the
mailing list for the eCos project.
Re: contributing a failsafe update meachanism for FIS from within ecos applications
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Neundorf, Alexander" <Alexander dot Neundorf at jenoptik dot com>
- Cc: ecos-devel at sources dot redhat dot com
- Date: Mon, 18 Oct 2004 14:52:31 +0200
- Subject: Re: contributing a failsafe update meachanism for FIS from within ecos applications
- References: <5A8A17126B73AC4C83968F6C4505E3C50131B184@JO-EX01.JENOPTIK.NET>
On Mon, Oct 18, 2004 at 02:25:53PM +0200, Neundorf, Alexander wrote:
> Any technical comments ?
You need to make some of the code conditionally compiled on CDL. ie by
default there is no valid marker, only one flash block is used etc.
You should have CDL to control where the second flash block is. Its
bad to assume its the next block.
What happens when an old redboot reads the fis directory of a new
redboot with these valid/invalid entry?
Does the entry show up on the fis list? Does it have a sensible name?
Is there any way to see if its valid/invalid etc.
At the moment you seemed to of focused on the mechanics of how you
boot/update reliably. Thats the easy part. You now need to see how it
fits into the rest of redboot and eCos. Hopefully some of the
questions i asked above with get you started in that direction.