From: Gary Thomas <gary@mlbassoc.com>
To: Ram Sudhir Tadavarthi <ram.tadavarthi@netco.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] any tool/strategy present in eCos to load ram image stored in flash and run it ???
Date: Thu, 01 Jun 2006 16:50:00 -0000 [thread overview]
Message-ID: <1149176634.7288.132.camel@hermes> (raw)
In-Reply-To: <20060601135337.89F41215207@gemmini.netco.de>
On Thu, 2006-06-01 at 16:07 +0200, Ram Sudhir Tadavarthi wrote:
> Hi all,
>
> I am new to eCos. I have redboot working for my platform(PQ2FADS-ZU board).
> Now I am creating ram images on the host and loading the ram images to the
> target using the redboot load via tftp and running them successfully.
>
> However in production series, we would like to store the ram image in flash,
> copy the image in ram and run it from ram.
>
> Is there any tool/strategy/option in eCos to do this? Can we configure
> redboot to do it?
>
> In my point of view, most of you might have done this already. Can anybody
> give me hint how to do this.
This is exactly what the FIS (create/load) commands are for. You can
create a boot script to load the image and execute it.
To create the image:
RedBoot> lo program_image
RedBoot> fi create program
To run it in your boot script:
(boot) fi lo program
(boot) g
--
------------------------------------------------------------
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
prev parent reply other threads:[~2006-06-01 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 14:12 Ram Sudhir Tadavarthi
2006-06-01 16:27 ` Andrew Lunn
2006-06-01 16:50 ` Gary Thomas [this message]
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=1149176634.7288.132.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=ram.tadavarthi@netco.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).