public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Stefan Sommerfeld <sommerfeld@mikrom.de>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Reboot flashing from eCos system?
Date: Mon, 15 Aug 2005 16:38:00 -0000	[thread overview]
Message-ID: <1124123909.29732.13.camel@hermes> (raw)
In-Reply-To: <009c01c5a1b6$670dbac0$152ca8c0@nullnullsix>

On Mon, 2005-08-15 at 18:28 +0200, Stefan Sommerfeld wrote:
> Hi,
> 
> coming back to this, because i really need a solution. I tried to load a 
> RAM based RedBoot out of my ROM based RedBoot without any luck. Is there a 
> way to build a "CYGSEM_HAL_USE_ROM_MONITOR" RAM based RedBoot? I made a 
> RedBoot which allows me to flash the first sector, but it reports: "Sorry, 
> 'RedBoot' is a reserved image and cannot be deleted".
> 

There should not be any reason to do so.  Simply build the RAM version
of RedBoot, including the FLASH (and maybe network) drivers.  Then
when you run it, you'll have complete control and can write to any
portion of the FLASH.  This is common practice - I do it all the time.

Note: there should not be any reason to try and delete the image called
"RedBoot" (which is obviously what you tried although you didn't say 
so).  You can safely overwrite it with the new contents.  For example,
after booting into a RAM version:

  RedBoot> lo -b 0x100000 RedBoot.ROM
  RedBoot> fi cr RedBoot

If you want to rewrite the whole FLASH, you could do something like:

  RedBoot> lo -b 0x100000 -r FLASH.image
  RedBoot> fi wr -f 0xFC000000 -b 0x100000 -l 0x1000000

(of course, these values and addresses are just examples, you'd need
to fill in the specifics for your platform yourself).  If you don't
have enough RAM to hold the whole FLASH image, simply perform multiple
load/fi command pairs to cover the whole thing.

> 
> ----- Original Message ----- 
> From: "Gary Thomas" <gary@mlbassoc.com>
> To: "Stefan Sommerfeld" <zerocom@cs.tu-berlin.de>
> Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
> Sent: Donnerstag, 21. Juli 2005 00:49
> Subject: Re: [ECOS] Reboot flashing from eCos system?
> 
> 
> > On Wed, 2005-07-20 at 23:38 +0200, Stefan Sommerfeld wrote:
> >> Hi,
> >> >>
> >> >> Is it possible to re-flash reboot from a running ecos system? I need 
> >> >> to
> >> >> flash a whole system (inclusive reboot) for production, but i'm not 
> >> >> sure
> >> >> if
> >> >> i can flash reboot besides the normal system (ecos and configs).
> >> >
> >> > Yes, if your RedBoot runs in ROMRAM mode, then this would be safe.
> >>
> >> Thanks ... you're understanding me. I, of course, talked about RedBoot.
> >>
> >> Any chance to do this with a ROM RedBoot? I have a pre-installed RedBoot 
> >> on
> >> a module which i want to replace. I'm thinking about disabling all 
> >> IRQ's,
> >> MMU tables should already be in RAM, so if there's no special locking
> >> mechanism in RedBoot, flashing should work.
> >
> > Probably *not* safe as there are many mechanisms within RedBoot that
> > your application will rely upon, unless you disable
> >   CYGSEM_HAL_USE_ROM_MONITOR

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


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

  reply	other threads:[~2005-08-15 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 21:27 Stefan Sommerfeld
2005-07-20 21:30 ` Gary Thomas
2005-07-20 21:38   ` Stefan Sommerfeld
2005-07-20 22:49     ` Gary Thomas
2005-08-15 16:29       ` Stefan Sommerfeld
2005-08-15 16:38         ` Gary Thomas [this message]
2005-08-15 16:53           ` Stefan Sommerfeld
2005-08-16  7:27 Retallack, Mark (Siemens)

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=1124123909.29732.13.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=sommerfeld@mikrom.de \
    /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).