From: "Michael Washburn" <mwashbur@stny.rr.com>
To: "Kent Borg" <kentborg@borg.org>, <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Boot ROM Responsibilities (and GDB)?
Date: Wed, 9 Jan 2002 13:10:35 -0500 [thread overview]
Message-ID: <009f01c19938$efaa0580$2f438209@endicott.ibm.com> (raw)
In-Reply-To: 20020109112508.B4902@borg.org
Kent,
I just scanned through several PPC 405 Boot code sources and found that they
are all resetting the DBCR very early after the cpu starts up. These sources
include the openbios support, mentioned by Armin Kuster in his response, and
in the ppcboot sources (http://ppcboot.sourceforge.net/ ), along with
several boot sources I've developed.
The 405GP User's Manual (
http://www-3.ibm.com/chips/techlib/techlib.nsf/techdocs/852569B20050FF778525
6996006130F8 )does offer a slight hint to do this in section 8.10, though
they don't say what it should be set to since it is application dependent.
Good Luck,
Mike
----- Original Message -----
From: "Kent Borg" <kentborg@borg.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, January 09, 2002 11:25 AM
Subject: Boot ROM Responsibilities (and GDB)?
>
> Is there any documentation on what a 405 boot ROM is supposed to do
> before jumping to the PPC kernel?
>
> We finally found what was messing with our use of GDB. DBSR was
> (sometimes) coming up with some unfortunate bits set, our boot ROM
> didn't know to clear them and the code that actually uses the CPU's
> debug hardware didn't bother to put that hardware in an appropriate
> state.
>
> Coming from an old fashioned perspective where boot ROMs are little
> and only sufficient to get the next higher level of program running,
> it seems strange to make them have to know anything about details of
> assorted hardware other than to disable optional things and make very
> basic things (like RAM access) work.
>
> Because we have a custom boot ROM (lifted from a previous non-Linux
> use of the same board--that's part of the beauty of having boot ROMs
> be simple, they are then quite universal and can be written quite
> early in the project before you even know what the project is) what
> else are we missing?
>
> What are a PPC boot ROM's responsibilities? (I.E., what do we add to
> our version of head.S.)
>
>
> Thanks,
>
> -kb, the Kent who is trying to keep his head in two different arch
> trees at once without too much confusion.
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-09 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 16:25 Boot ROM Responsibilities (and GDB)? Kent Borg
2002-01-09 17:30 ` Dan Malek
2002-01-09 17:37 ` Armin Kuster
2002-01-09 18:10 ` Michael Washburn [this message]
2002-01-09 18:22 ` Dan Malek
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='009f01c19938$efaa0580$2f438209@endicott.ibm.com' \
--to=mwashbur@stny.rr.com \
--cc=kentborg@borg.org \
--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).