From: "Brian Padalino" <bpadalino@perigee•com>
To: "Chris Zimman" <chris@cryptoapps•com>
Cc: <linuxppc-embedded@lists•linuxppc.org>
Subject: RE: PPCBoot on Ebony board
Date: Wed, 16 Jul 2003 11:39:28 -0400 [thread overview]
Message-ID: <DGEEIPOFGGPOACEFBGGCAEHGCAAA.bpadalino@perigee.com> (raw)
In-Reply-To: <20030716142936.GA30975@dingdong.cryptoapps.com>
I am actually stuck with an OCDemon Wiggler JTAG interface. I was quoted as
being $2300 for the BDI2000.
That is a bit out of my range for this project. Know anyone selling a used
one?
I guess I will just try to get gdb to work (in cygwin) with this wiggler.
Thanks for everyone's help!
Brian
-----Original Message-----
From: owner-linuxppc-embedded@lists•linuxppc.org
[mailto:owner-linuxppc-embedded@lists•linuxppc.org]On Behalf Of Chris
Zimman
Sent: Wednesday, July 16, 2003 10:30 AM
To: Brian Padalino
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: PPCBoot on Ebony board
On Wed, Jul 16, 2003 at 07:59:28AM -0400, Brian Padalino wrote:
> I found the flash programmer utility, but I am actually a bit scared to
> flash the flash with the version of PPCBoot that I made. I am working
> without a JTAG interface, so flashing using JTAG is out of the question,
and
> how would I re-flash if the PPCBoot binary I have doesn't work properly?
Is
> the board running out of EEPROM right now with the IBM Open Shell always
> there? I have sifted through the documentation a bit, but haven't found a
> straight answer as to exactly how the board is setup right out of the box.
If you built a standard U-Boot 440GP config, odds are that it will work
fine.
If you have a flash programmer, you can always save a copy of the OSOpen
image and then reflash with that if U-Boot doesn't come up right.
I'm not sure if your board is using the EEPROM, but that's only used for
strapping anyway.
> Any sort of help is appreciated. I am extremely new to ICE, JTAG and such
> embedded systems -- so please, be patient with me (if you can).
The first thing I would recommend you do is to get a BDI2000 JTAG
debugger. If you're going to be doing any serious work on U-Boot,
Linux, etc. this is one of the most valuable tools you can have.
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-16 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 4:32 [RFC] consistent_sync and non L1 cache line aligned buffers Eugene Surovegin
2003-07-15 15:46 ` Tom Rini
2003-07-15 16:20 ` Eugene Surovegin
2003-07-15 16:25 ` Tom Rini
2003-07-15 16:17 ` Matt Porter
2003-07-15 16:27 ` Eugene Surovegin
2003-07-15 18:11 ` PPCBoot on Ebony board Brian Padalino
2003-07-15 21:32 ` Chris Zimman
2003-07-16 11:59 ` Brian Padalino
2003-07-16 14:29 ` Chris Zimman
2003-07-16 15:39 ` Brian Padalino [this message]
2003-07-16 14:45 ` Roland Dreier
2003-07-15 23:51 ` [RFC] consistent_sync and non L1 cache line aligned buffers Matt Porter
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=DGEEIPOFGGPOACEFBGGCAEHGCAAA.bpadalino@perigee.com \
--to=bpadalino@perigee$(echo .)com \
--cc=chris@cryptoapps$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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