All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Zimman <chris@cryptoapps.com>
To: Brian Padalino <bpadalino@perigee.com>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Using gdb to load PPCBoot/U-Boot
Date: Wed, 16 Jul 2003 13:07:21 -0500	[thread overview]
Message-ID: <20030716180721.GA31881@dingdong.cryptoapps.com> (raw)
In-Reply-To: <DGEEIPOFGGPOACEFBGGCKEHGCAAA.bpadalino@perigee.com>


On Wed, Jul 16, 2003 at 01:17:52PM -0400, Brian Padalino wrote:
> Is it at all possible to use gdb to load the ppcboot/u-boot binary images to
> the flash?

Maybe in the realm of "all things possible" it is, but not normally.
The way that you typically program flash in circuit is to put the host
processor (the 440GP in your case) into slave mode and have it execute a
small stub of code that first erases the sectors that you want to write
to and then programs them with the new data.

The alternative is to pop the PQFP out of the socket and program it in
an external flash programmer.

> If it is possible, is there a general direction I should be looking at to
> accomplish this task?  Am I causing too much trouble for myself by not being
> able to afford a BDI2000?

JTAG is definitely the easiest way to do this, and yes, you are definitely
causing yourself lots of potential grief by not having a BDI2000.  If you
only intend to do userland development and never do anything more low level,
you can get by without one.  But for anything else, you definitely want one.
As far as JTAG debuggers go, they are very featured, pretty cheap (look at
the WindRiver VisionICE stuff for a comparison -- they want like $7-$10K per
target!) and definitely the most supported on this list.

--Chris

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-07-16 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 17:17 Using gdb to load PPCBoot/U-Boot Brian Padalino
2003-07-16 18:07 ` Chris Zimman [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=20030716180721.GA31881@dingdong.cryptoapps.com \
    --to=chris@cryptoapps.com \
    --cc=bpadalino@perigee.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.