This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: The basics

To: Jonathan Larmour <jlarmour at redhat dot com>
Subject: Re: [ECOS] The basics
From: Andrew Lunn <andrew dot lunn at ascom dot ch>
Date: Fri, 19 Oct 2001 18:40:44 +0200
Cc: Tim Michals <Tim dot Michals at cygnetinc dot com>, ecos-discuss at sources dot redhat dot com
References: <63A6C537769693488EF351F5DB94668615B453@cyglew04.cygnetinc.com> <3BD0536A.79E24FFB@redhat.com>

On Fri, Oct 19, 2001 at 05:23:06PM +0100, Jonathan Larmour wrote:
> Tim Michals wrote:
> > 
> > It is my understanding an image can be targeted to RAM or ROM.  In a
> > production system, a goal maybe to use RedBoot to configure the hardware
> > then load an production image into RAM from ROM?
> 
> Absolutely. Or the production image could be built for ROM itself. But
> using RedBoot does allow you to do field update.

You can do field updates so long as you use redboot to do it. The
application cannot update its self if you have redboot in ROM. With
that situation there is a danger the application will jump into ROM
because of an incoming ethernet packet etc. This causes a read from
FLASH while its in write mode and a crash....

If you want the application to be able to update itself, you cannot
have Redboot running in ROM. RAM is OK. 

      Andrew

Follow-Ups:
- Re: The basics
  - From: Jonathan Larmour

References:
- The basics
  - From: Tim Michals
- Re: The basics
  - From: Jonathan Larmour

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]