From: Gary Thomas <gary@mlbassoc.com>
To: Ramprasad <rprasad@pav.research.panasonic.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] how to create RAM redboot image
Date: Wed, 15 Oct 2003 21:52:00 -0000 [thread overview]
Message-ID: <1066254746.32461.97.camel@hermes> (raw)
In-Reply-To: <02ec01c39365$912b2650$bca6a996@dhcp297>
On Wed, 2003-10-15 at 15:44, Ramprasad wrote:
> Hello all,
>
> I compiled the redboot for ASB2305 (for AM33 processor) and got the images
> like .img, .bin, .elf and .srec. But in the manuals says you have to
> download .ram of redboot image using JTAG debugger. Please can you tell me
> how can I get the .ram (or .rom) image.
>
The "RAM" version is simply a version which has the startup type set
to RAM. The file name suffices have nothing to do with this.
The process should be something like this:
% ecosconfig new asb2305 redboot
% ecosconfig import ${ECOS_REPOSITORY}/hal/mn10300/asb2305/current/misc/redboot_RAM.ecm
% ecosconfig tree
% make
Then download whatever file your JTAG software wants - some want to
see raw binary (hence the .bin suffix), some an ELF image (.elf), ...
Once you have this running, build the ROM version. In a separate directory,
using the same steps as above, except use the ..._ROM.ecm file
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-10-15 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 20:40 [ECOS] standalone RAM application Aaron Richardson
2003-10-10 21:17 ` Gary Thomas
2003-10-10 22:02 ` Aaron Richardson
2003-10-13 6:30 ` Eric de Jong
2003-10-15 21:44 ` [ECOS] how to create RAM redboot image Ramprasad
2003-10-15 21:52 ` Gary Thomas [this message]
2003-10-24 15:35 ` [ECOS] Bringup the asb2305 board Ramprasad
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=1066254746.32461.97.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rprasad@pav.research.panasonic.com \
/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).