public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] fail over mechanism strategy (Avila IXP425 ) - need suggestion
@ 2007-02-22 10:17 Bhanu Prakash Adhikari
  0 siblings, 0 replies; only message in thread
From: Bhanu Prakash Adhikari @ 2007-02-22 10:17 UTC (permalink / raw)
  To: ecos-discuss


Folks,

I'm working on a fail over mechanism on Avila board with IXP425
processor.

I have a CF with linux image and ramdisk. The board boots fine with CF
image.

Details -

1. Avila GW2348
2. IXP 425
3. RedBoot 2.02
4. Linux 2.6.18	(in CF)
5. SnapGear 3.4.0  


My new requirement is to have a robust fail over mechanism - for example
- when the CF card or the image it has got corrupted for some reason, I
must have a light thin version (may be uClinux or snapgear) of image
should be loaded on the board and continue working with the new
(uClinux/snapgear) image. With the thin image the CF will be rewritten
or reformatted with new image.

My strategy is to have uClinux/snapgear image on the inbuilt flash and
would be invoked when CF is corrupted.


My questions -

1. Suggest me whether I'm on the right direction or not?
2. Can I achieve this by any means through Redboot commands?
3. I find ramdisk must be loaded at 0x00800000 to get properly mounted.
Is it possible to change the location? If so, how can I do that?
4. Can I have ramdisk for uClinux loaded and written at different
location other than this (0x00800000)?

5. I feel the need of patching redboot with the required logic -

a)	if (CF image == corrupt)
	{
		Load uClinux from inbuilt flash
	}

	Or

b)	if (CF image not booted)
	{
		Load uClinux from inbuilt flash
	}

       Do we have any watchdog timer in IXP or in redboot to achieve
this?


Awaiting for your valuable inputs,

Thanks in advance,
Bhanu Prakash A









The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.

www.aztecsoft.com

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-02-22 10:17 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-22 10:17 [ECOS] fail over mechanism strategy (Avila IXP425 ) - need suggestion Bhanu Prakash Adhikari

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).