From: David Hawkins <dwh@ovro.caltech.edu>
To: rtos <rtos123@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux on PPC
Date: Thu, 02 Mar 2006 21:10:43 -0800 [thread overview]
Message-ID: <4407CFD3.4060206@ovro.caltech.edu> (raw)
In-Reply-To: <190edfbd0603021801g5505cab9h8e285fdc7bf476d1@mail.gmail.com>
Hiya,
I'm no expert in this, but here's the basics;
> We have a customized board running on IBM PPC 750. The customer boot
> loader is provided by the vendor. Also, the vendor has provided
> the BSP on vxworks.
The PPC 750 is a fairly old processor, so there will be Linux
support for it. For example, I picked up a couple of Artesyn
PrPMC boards that contain a PPC 750, and this board can run
Linux, though I have not had time to try booting it yet.
If the vendor provided the VxWorks BSP, then hopefully they
also provided you with the physical memory map of the board.
This is what you really need to get another bootloader (eg. U-Boot)
and Linux up-and-running. If the vendor will provide schematics
for the board, that would also help (hey, it never hurts to
ask for them).
> We are planning to use linux on this processor. What are the steps
> involved in booting the board with linux.
> Which linux to be used and what are the procedures involved. I dint come
> across a documents which had these details.
>
> I am new to the linux front. So any help is highly appreciated.
>
Step 1. Get the memory map of the board.
Step 2. Find a PPC 750 port in the Linux source.
For example, in the 2.6 series kernel, the place to start
looking is under arch/ppc/platforms. grep -Ie 750 shows
up some of the PPC 750 based systems.
chestnut.c 750FX/GX evaluation board
katana.c Looks like one too
prpmc750.c Looks like a Motorola board
Look at the comments in the code, look at the memory map
of the reference board versus your custom board. There is
a very good chance that the custom board is based on a
reference design - thats the whole point of them.
Step 3. Build a minimal kernel
Step 4. Boot
Step 5. Purchase a BDI2000 JTAG debugger and use it to figure
out why Step 4 didn't work.
Repeat at Step 3.
When I get time to play with my Artesyn board, I'll go back to
the katana.c file, the grep above had some comments about Artesyn
boards. If it fails to boot, I'll use the BDI2000 to see where it
dies and go from there.
Once you can boot Linux, you might decide that the custom bootloader
on the board is inflexible. The U-Boot bootloader is very nice
and will have support for other 750-based boards, it shouldn't
take too much to port that too. But first, try to get a Linux
kernel booted, even if it has a hard-wired command line.
Also take a look over on the Freescale web site, search for
'porting linux', it'll show up AN2145, AN2222, AN2579, and
a bunch of other application notes. They'll give you an idea
of what it takes to port to a new processor.
> I am new to the linux front. So any help is highly appreciated.
So it depends how much time you have versus how much you
want to spend.
There are also commercial companies that will do the job for you.
If you can come up with the memory map and hardware details of
the board, you could always post a request on this list, and
I am sure there are people reading this list that would
respond. (I'm not one of them though, so I'm not trying to
drum up business ok)
Regards,
Dave
next prev parent reply other threads:[~2006-03-03 5:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 2:01 Linux on PPC rtos
2006-03-03 2:23 ` Frank
2006-03-03 5:09 ` nreddy
2006-03-03 16:00 ` Wolfgang Denk
2006-03-03 5:10 ` David Hawkins [this message]
2006-03-03 9:33 ` Adrian Cox
2006-03-03 16:04 ` Wolfgang Denk
2006-03-03 16:53 ` David Hawkins
2006-03-04 2:05 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 19:39 Rune Torgersen
2006-03-03 20:06 ` David Hawkins
2006-03-04 2:09 ` Wolfgang Denk
2006-03-04 2:51 ` David Hawkins
2006-03-03 20:28 Steve Strublic
2006-03-03 20:31 Rune Torgersen
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=4407CFD3.4060206@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rtos123@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.