From: Grant Edwards <grante@visi.com>
To: jimmy.gendron@telus.com
Cc: gdb@sources.redhat.com
Subject: Re: Réf. : Re: Flash programming using GDB with ARM Multi-ICE
Date: Tue, 06 Aug 2002 13:34:00 -0000 [thread overview]
Message-ID: <20020806153914.A29318@visi.com> (raw)
In-Reply-To: <OFBB0DB463.03E099BD-ON85256C0D.006FE3FB@quebectel.qc.ca>; from jimmy.gendron@telus.com on Tue, Aug 06, 2002 at 04:24:57PM -0400
On Tue, Aug 06, 2002 at 04:24:57PM -0400, jimmy.gendron@telus.com wrote:
> If i understand:
>
> 1. Write a "stub" to initiate memory map
>
> 2. Write I/O routines to copy image to be burned from host to target RAM
> (through DCC)
I don't do step 2 in my app. (I don't know what DCC is, either...)
I link my app with the image to be burned. To my app, the
image to be burned is just a section of memory containing
bytes. My linker script makes the starting/ending addresses of
that image section visible so my app knows where the image data
is in RAM. The linker creates a single application image that
contains the flash burning program as well as a copy of
whatever is to be burned into flash.
> 3. Copy from RAM to flash
That's what my little app does.
> The run that using GDB/Multi-ICE and everything should work.
>
> Am i right? Are you aware of an available library for that?
I don't know of any. Burning flash is usually fairly simple,
but it varies slightly from one flash vendor to another and
even from one board layout to another.
--
Grant Edwards
grante@visi.com
prev parent reply other threads:[~2002-08-06 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 13:25 jimmy.gendron
2002-08-06 13:34 ` Grant Edwards [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=20020806153914.A29318@visi.com \
--to=grante@visi.com \
--cc=gdb@sources.redhat.com \
--cc=jimmy.gendron@telus.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