From: Grant Edwards <grante@visi.com>
To: Hugo Villeneuve <hvilleneuve@softacoustik.com>
Cc: Red Hat Insight <insight@sources.redhat.com>
Subject: Re: downloading binary file
Date: Tue, 06 Nov 2001 12:02:00 -0000 [thread overview]
Message-ID: <20011106140542.A21458@visi.com> (raw)
In-Reply-To: <20011106192114.6355F2D0553@breg.mc.mpls.visi.com>
On Tue, Nov 06, 2001 at 02:19:57PM -0500, Hugo Villeneuve wrote:
> Hi,
>
>
> >I know you can if you convert the binary file to ELF using
> >arm-elf-objcopy.
>
> This binary file is in fact produced from an ELF file. The problem is
> that the .text section of this ELF file points to Flash memory, and I
> want to download it to RAM memory.
So put it there. objcopy can move sections around as well as
convert from one format to another. It's a very handy little
program. Do "man objcopy" and pay particular attention to
the --change-section-address option.
> >What model of Jeeni do you have? I've never heard of the
> >"AMR Angel/Ethernet" target before...
>
> My typo error: should be "ARM Angel/Ethernet"
It would be awfully handy to have commands to dump a region of
memory to a file in any of the bfd formats, and to be able to
read such a file into memory at a specific location. I keep
threatening to impliment that, but I never do it...
--
Grant Edwards
grante@visi.com
next parent reply other threads:[~2001-11-06 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011106192114.6355F2D0553@breg.mc.mpls.visi.com>
2001-11-06 12:02 ` Grant Edwards [this message]
2001-11-06 12:37 ` Fernando Nasser
2001-11-16 8:21 Hugo Villeneuve
-- strict thread matches above, loose matches on Subject: below --
2001-11-06 11:23 Hugo Villeneuve
2001-11-06 11:20 Hugo Villeneuve
[not found] <200111061526.HAA13164@cygnus.com>
2001-11-06 7:49 ` Fernando Nasser
2001-11-06 7:00 Hugo Villeneuve
2001-10-02 14:37 Hugo Villeneuve
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=20011106140542.A21458@visi.com \
--to=grante@visi.com \
--cc=hvilleneuve@softacoustik.com \
--cc=insight@sources.redhat.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).