From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Albrecht Dreß" <albrecht.dress@arcor.de>
Cc: LinuxPPC Embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: [OT] write flash on MPC5200 board via jtag
Date: Tue, 22 Jul 2008 18:30:10 -0400 [thread overview]
Message-ID: <9e4733910807221530vd5573d3oc2b56f544ab1c1f6@mail.gmail.com> (raw)
In-Reply-To: <1216753011l.5683l.0l@antares>
On 7/22/08, Albrecht Dre=DF <albrecht.dress@arcor.de> wrote:
> Hi,
>
> sorry for a somewhat off-topic question...
>
> I want to design a mpc5200b board which is roughly derived from Freescal=
e's
> 5200B Lite demo. Obviously, I have the problem to initially write u-boot
> into the boot nor flash. I believe this would be possible using the
> jtag/bsm interface (is that true?).
>
> Can you recommend any good hardware and software solution for that, if
> possible running on linux (OSS?)? I don't need a "real" debugger (maybe =
an
> interface to gdb), just something to write the flash, so u-boot comes up.
I haven't tried it, but a Macraigor USB Wiggler supports the MPC5200
and it's $250.
http://www.macraigor.com/cpus.htm
That should be enough to write uboot into RAM. Once uboot is in RAM
you can use it to write the flash.
Let me know if you try it and it works.
>
> Thanks for any help,
> Albrecht.
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--=20
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-07-22 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 18:56 [OT] write flash on MPC5200 board via jtag Albrecht Dreß
2008-07-22 21:29 ` Grant Likely
2008-07-22 21:55 ` Mike Timmons
2008-07-22 22:30 ` Jon Smirl [this message]
2008-07-25 19:48 ` Albrecht Dreß
2008-07-23 12:21 ` WITTROCK
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=9e4733910807221530vd5573d3oc2b56f544ab1c1f6@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=albrecht.dress@arcor.de \
--cc=linuxppc-embedded@ozlabs.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).