linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Jander <david.jander@protonic.nl>
To: "Hager, Johannes, HRD/AB" <johannes.hager@lfk.eads.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: AW: Compiling glibc-2.3.2 (debian) on mpc8xx ;-)
Date: Tue, 9 Mar 2004 14:03:31 +0100	[thread overview]
Message-ID: <200403091403.31151.david.jander@protonic.nl> (raw)
In-Reply-To: <2D9AB865A49FD511914700105A0EF679016C4909@morse.smart.lfk.eads.net>


On Tuesday 09 March 2004 10:20, you wrote:
> Dear David,
> sadly I have got no answer to your question, but I want to ask you
> something:
> Are you using U-Boot for starting Linux?
> If you do, can you give me a short roadmap, how to port to new
> board?

Yes, we are using u-boot.
Well, here's a list of suggestions based on what we did:
1.- Read the README of u-boot.
2.- Assuming there are already other boards with the same CPU and at least a
more or less similar setup that are supported, pick one of them, and copy the
directory boards/xxxx to boards/yyyy (where yyyy is the name of your board).
3.- Go to include/configs and make a copy of the xxxx.h file. Don't forget to
add your board also to the Makefile.
4.- Watch out for special stuff for the board you are using as start, it could
get in your way.
5.- Check if the xxxx's config and board support files are indeed a good
starting point (clean documented sources, using the newest format of config
files and most important, get to fully understand the source).
6.- Look at several other examples to pick up ideas and learn from the
sources.
7.- Configure your board with the design information, and from what you
learned reading README and the examples.
8.- Leave SDRAM configuration for later (assuming you use a MPC8xx processor,
where SDRAM is a special issue), and look if you get something out of your
serial port first.
9.- Use Jtag or BDM interfaces to place the bootloader into flash.
(We used a homebrewed Jtag interface to program the on-board flash, although
everyone and ther brother in this list will probably say that you MUST do it
with the BDI2000 from abatron via the BDM port).
10.- Have a Scope at hand to examine the CS and address lines (if at all
possible). This may help to see what's going on before the serial port comes
into play.
11.- If you have a mpc8xx processor, read the technical notes from Micron
about how to interface SDRAM to the MPC8xx, and how to program the UPM
correctly. There's a tool from Motorola that let's you draw the waveforms on
screen and obtain the corresponding byte-code for the UPM. This might be
handy. Again look at and learn from what others did.

Good Luck!

Best regards,

--
David Jander
Protonic Holland.
tel.: +31 (0) 229 212928
fax.: +31 (0) 229 210930
Factorij 36 / 1628 AL Zwaag

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

       reply	other threads:[~2004-03-09 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2D9AB865A49FD511914700105A0EF679016C4909@morse.smart.lfk.eads.net>
2004-03-09 13:03 ` David Jander [this message]
2004-03-09 14:20   ` remote access via shell Kevin P. Dankwardt
2004-03-09 15:14     ` Wolfgang Denk
2004-03-10 14:31       ` RAM Disk problems Kevin A. Sapp
2004-03-10 15:00         ` Wolfgang Denk
2004-03-10 17:35           ` Kevin A. Sapp
2004-03-10 15:03         ` Jaap-Jan Boor
2004-03-09 16:24     ` remote access via shell Gerrit Van de Velde

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=200403091403.31151.david.jander@protonic.nl \
    --to=david.jander@protonic.nl \
    --cc=johannes.hager@lfk.eads.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).