From: "Mark A. Greer" <mgreer@mvista.com>
To: Alex Shnitman <alexsh@hectic.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on Motorola Sandpoint/PPMC7400
Date: Wed, 30 Aug 2000 12:20:47 -0700 [thread overview]
Message-ID: <39AD5E8E.E3C244D8@mvista.com> (raw)
In-Reply-To: 20000830215856.B5340@hectic.net
Alex Shnitman wrote:
> Hi, Mark!
>
> On Tue, Aug 29, 2000 at 12:16:09PM -0700, you wrote the following:
>
> > > I downloaded the kernel and tried it. It starts booting, but it hangs
> > > right after initializing the the OpenPIC. :-( I'll download the source
> > > code tonight and try to look at it, although I don't have much hopes
> > > gotta learn though.
> > >
> > > Is there any book that you recommend to get me started? Any other
> > > docs/tips?
> >
> > Oops, I should have included the sandpoint switch settings. For
> > this version of the kernel, the sandpoint switches must be set as
> > follows:
> >
> > S4,S3: up, down
> > S5: down
> > S6: down (yours is probably up which is why it hung in openpic)
> >
> > Try this and see if it helps.
>
> It did! The kernel boots fine now all the way through.
>
> Thanks a lot!
>
> Another question: what would be the best way to go about booting Linux
> from the flash? Would flashing the kernel in instead of the dink32
> monitor do the trick, or does dink32 do some important initializations
> that are needed for the kernel to boot?
Yeah, at the moment, it does rely on DINK to do some initial setup (memory
controller, et. al.). If you want, you can put that in the code yourself and
then you can get rid of DINK. If you don't want to do that, you can still put
the kernel in flash (somewhere that doesn't overwrite DINK or the execption
vectors) as long as you have enough flash on your PPMC module. You can then
do something like "env BOOT=<address>" to cause DINK to automatically jump to
that address--that's should be the address of the linux ppc bootloader--and
the kernel will boot up for you without your intervention.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-30 19:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-28 19:55 Linux on Motorola Sandpoint/PPMC7400 Alex Shnitman
2000-08-28 20:03 ` Gabriel Paubert
2000-08-28 20:35 ` Alex Shnitman
2000-08-28 21:01 ` Gabriel Paubert
2000-08-29 16:43 ` Alex Shnitman
2000-08-28 23:14 ` Mark A. Greer
2000-08-29 17:13 ` Alex Shnitman
2000-08-29 19:16 ` Mark A. Greer
2000-08-30 18:58 ` Alex Shnitman
2000-08-30 19:20 ` Mark A. Greer [this message]
2000-09-03 4:42 ` Bob Doyle
2000-09-04 10:37 ` Adrian Cox
2000-08-30 19:02 ` Alex Shnitman
2000-08-31 0:45 ` Matt Porter
2000-08-30 23:46 ` Dan Malek
2000-08-31 11:13 ` Gabriel Paubert
2000-08-31 15:01 ` Peter Tympanick
2000-08-29 21:27 ` Mark A. Greer
2000-08-29 14:04 ` Tom Roberts
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=39AD5E8E.E3C244D8@mvista.com \
--to=mgreer@mvista.com \
--cc=alexsh@hectic.net \
--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).