From: Chris Zimman <chris@cryptoapps.com>
To: Brian Padalino <bpadalino@perigee.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PPCBoot on Ebony board
Date: Tue, 15 Jul 2003 16:32:54 -0500 [thread overview]
Message-ID: <20030715213254.GA27907@dingdong.cryptoapps.com> (raw)
In-Reply-To: <DGEEIPOFGGPOACEFBGGCOEGPCAAA.bpadalino@perigee.com>
On Tue, Jul 15, 2003 at 02:11:07PM -0400, Brian Padalino wrote:
>
> I am trying to transfer PPCBoot that I had compiled over a tftp session in
> the 440GP 1.18 ROM Monitor (02/11/02) that came on the Ebony board. Is that
> the wrong method of trying it? I tried using both serial ports and Kermit
> with Xon/Xoff handshaking, but it just ended up timing out.
>
> I keep getting the error:
> Loading file "C:\ppc\bootp\boot.img" ...
> Sending tftp boot request ...
> Not a valid boot image file
>
> Which stems from an improper magic number at the top of the file to say it's
> a valid boot image.
This is not going to work. You want to program PPCBoot into flash via a
flash programmer or via JTAG.
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-15 21:32 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 [this message]
2003-07-16 11:59 ` Brian Padalino
2003-07-16 14:29 ` Chris Zimman
2003-07-16 15:39 ` Brian Padalino
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=20030715213254.GA27907@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 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).