From: Gary Thomas <gthomas@redhat.com>
To: Warren Jasper <wjasper@tx.ncsu.edu>
Cc: eCos Discussion <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Placing binary file into RAM on target
Date: Fri, 27 Jul 2001 05:39:00 -0000 [thread overview]
Message-ID: <XFMail.20010727063759.gthomas@redhat.com> (raw)
In-Reply-To: <200107271231.IAA25770@lx10.tx.ncsu.edu>
On 27-Jul-2001 Warren Jasper wrote:
>
> Gary,
>
> I would use RedBoot if I could. I have tried to compile and run it
> for the sa11x0, which I thought I could do easily since I have a
> stable working port and gdb-module part working perfectly, but I have
> not met with success.
>
What problems do you have?
If you can get GDB stubs working on a platform, RedBoot is anout 3 minutes
away...
>
> -- Warren
>
> Warren J. Jasper
> wjasper@tx.ncsu.edu
>
>>
>>On 26-Jul-2001 Warren Jasper wrote:
>>>
>>> Does anybody know of a way to place an arbitrary binary file into
>>> SDRAM on a target if one is running gdb stubs? I am running a
>>> Intel StrongARM SA1110, and would like to load a program into
>>> FLASH via eCos (as opposed to JTAG via a parallel port with JFLASH).
>>>
>>
>>Use RedBoot :-)
>>
>>> gdb will only load elf type files, so I guess one option is to convert a
>>> file into "elf" and have the loader put it into memory. Is there an easy wa
>>+ y
>>> to do this or a better way?
>>
>>This would work. However, RedBoot is a more flexible option since you have
>>the ability to relocate [move] the code on the fly, perform checksums, etc.
next parent reply other threads:[~2001-07-27 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200107271231.IAA25770@lx10.tx.ncsu.edu>
2001-07-27 5:39 ` Gary Thomas [this message]
2001-07-26 11:22 Warren Jasper
2001-07-26 11:35 ` Jonathan Larmour
2001-07-26 14:09 ` Gary Thomas
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=XFMail.20010727063759.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=wjasper@tx.ncsu.edu \
/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).