From: Frank Przybylski <Frank.Przybylski@vas-gmbh.de>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Programming Flash
Date: Thu, 14 Sep 2000 09:44:28 +0200 [thread overview]
Message-ID: <39C081DC.FEB15486@vas-gmbh.de> (raw)
In-Reply-To: A3E34B558F5CD211B4980008C7A4A99002423F1B@sparrow.eng.gilbarco.com
Hi,
"Banks, Kelly" wrote:
>
> There isn't necessarily ANY onboard code required to program FLASH, other
> than the BDM/JTAG drivers onchip directly from Motorola.
>
> The basics of FLASH programming consists of writing command words into
> command addresses and then writing the data into the desired address
> (re:AMD's Am29DL16xC pub#21553 Rev. C 08/23/99)... I don't see why one
> couldn't use MaCraigor's scripting language within the BDM Commander to
> carry out the entire operation THROUGH the BDM/JTAG keeping all the logic
> over on the host with no bootstrap code & no secondary ports required (Of
> Course, the specifics of your FLASH device may vary).
>
> Kelly
It's indeed possible to program FLASH without any code onboard, just with script
commands. I first used this way to program FLASH (AM29LV160DB) with the MPCBDM
via gdb script. I don't know how the Macraigor communicates while accessing
memory, but I guess this will be real slow. Because you have to access each word
of memory more than once, just for the programming, not included the
communication. So I tried a middle way: I have a gdb script which uses MPCBDM
target commands to setup the board, so that it's possible to execute code in
SDRAM. If I need to program FLASH, I execute another MPCBDM target command,
which downloads a fast FLASHing routine into the MPC controlled SDRAM and let
the MPC doing the FLASH programming itself. That's pretty fast. It's not
programmed nice, but it works fine for me. See
http://www.vas-gmbh.de/software/mpcbdm
hth
Frank
--
===============================================================================
Frank Przybylski,VAS GmbH,Gotenstr.6,20097 Hamburg,GERMANY,TEL:+49-40-238568-14
mailto:Frank.Przybylski@vas-gmbh.de , visit us at http://www.vas-gmbh.de
===============================================================================
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-14 7:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 13:35 Programming Flash Banks, Kelly
2000-09-14 7:44 ` Frank Przybylski [this message]
2000-09-14 14:58 ` Larry Battraw
-- strict thread matches above, loose matches on Subject: below --
2000-09-13 11:50 jonb
[not found] <319E391E2049D311843500609457383D07FD09@exchange.vividimage .com>
2000-09-12 21:56 ` Jerry Van Baren
2000-09-12 20:04 Kirk Haderlie
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=39C081DC.FEB15486@vas-gmbh.de \
--to=frank.przybylski@vas-gmbh.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).