linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Lauri Ojantakanen <lauri.ojantakanen@solidtech.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Booting sandpoint from ide disk
Date: Fri, 06 Sep 2002 13:26:11 -0400	[thread overview]
Message-ID: <3D78E533.97F0DA5F@mvista.com> (raw)
In-Reply-To: 20020906142827.GS761@opus.bloom.county


Tom Rini wrote:

> On Fri, Sep 06, 2002 at 11:02:58AM +0300, Lauri Ojantakanen wrote:
>
> > Instant need for booting from ide disk seem to have gone away :( Dink32 does
> > not start anymore at all. When I restart the machine nothing comes through
> > the serial cable (settings are correct). I have not touched to any board
> > switches. Red leds on the altimus board are as follows:
>
> Were you trying to put the kernel in flash or something?  If you've got
> access to HW debuggers (like the Abatron BDI) look at what's at
> 0xFF00_0000, it should start off with a bunch of nop's.

Ah, I guess I should have said, "Don't overwrite DINK" if that's what you did.
If you overwrote DINK, you'll have to find a ROM burner & a copy of DINK and put
it back on the FLASH.  After that, you can put the zImage either further back in
that FLASH where id doesn't overwrite any other code or better yet put it in the
secondary FLASH.

Mark


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

  reply	other threads:[~2002-09-06 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 10:16 Booting sandpoint from ide disk Lauri Ojantakanen
2002-09-05 15:47 ` Mark A. Greer
2002-09-06  8:02   ` Lauri Ojantakanen
2002-09-06 14:28     ` Tom Rini
2002-09-06 17:26       ` Mark A. Greer [this message]
2002-09-08 19:27         ` Lauri Ojantakanen
2002-09-08 20:05           ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2002-09-05 14:57 Rod Boyce
2002-09-05 15:24 ` Wolfgang Denk

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=3D78E533.97F0DA5F@mvista.com \
    --to=mgreer@mvista.com \
    --cc=lauri.ojantakanen@solidtech.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).