linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Dennis Khoo" <dkhoo@atmxdsl.com>
To: "RamanaYV" <venkataramana_y@mic.co.in>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PPCBOOT in customised MPC860T board
Date: Thu, 19 Feb 2004 11:09:24 -0800	[thread overview]
Message-ID: <000001c3f71c$1372ee30$7ec7c7c7@dkhoo> (raw)
In-Reply-To: 4034377A.000003.00996@RAMANAYV


Ramana,

Perhaps you should try the u-boot forum and use pick a tqm board as your
guide for the u-boot port.  But briefly for u-boot port:

1. Change Makefile to use your cross compiler and add your board config
2. Create a file named your_board.h in u-boot-x.x.x/include/configs for your
board configs.
3. Create a dir for your board under u-boot-x.x.x/board and in it
a) write/copy some flash routines in say flash.c
b) write/copy some ram routines in say your_board.c
c) write/copy other files like Makefile, etc
4. Modify u-boot-x.x.x/include/commproc.h to your board specs.
5. Compile and burn the u-boot.bin through BDM(I use DENX's $50 BDM4GDB but
that required on the MPCBDM so invest in a BDI2000.)

For the kernel(for 2.4.22 but 2.4.19 is similar):

1. Change the Makefile to use the right cross-compiler and also to tell it
to
build a ppc kerel. For example, add an entry "YOUR_BOARD CONFIG_YOURBOARD \"
in the list of boards under "if [ "$CONFIG_8xx" =
"y" ]; then" ....

2. Modify arch/ppc/config.in to add your board name to list of boards
already
present in the kernel for your cpu family.

#if defined(CONFIG_YOURBOARD)
 #include <platforms/yourboard.h>
 #endif

Please note that different kernel versions have different organizations so
yourboard.h which you will create later may have to be placed in a different
location.

3. Add the following to include/asm/mpc8xx.h:

 #if defined(CONFIG_YOURBOARD)
 #include <platforms/yourboard.h>
 #endif

4. Create the include/asm/yourboard.h   Not much to do here basically
#define IMAP_ADDR/SIZE to get the board going. (look at tqm board for
guidance)

5.  This next step is optional but it saves me a lot of time when I clean
and
rebuild my kernel.  When I clean my kernel, the .config file which was
created
when I do a "make menuconfig" or "make config" is wiped out and the next
time
when I build a kernel, the default config file "arch/ppc/defconfig is used
which usually means I have to reconfigure a lot of
the options.  To save time, right after I do a "make menuconfig" and the
.config
file is generated in the top directory, I copy the .config file and replace
arch/ppc/defconfig with it.

6. (If your board has ethernet) Add board specific scc ethernet pin info to
include/asm/commproc.h(find a spot
somewhere between the list of boards and possibly change
arch/ppc/8xx_io/fec.c to get fast ethernet(fec) to work.

7. whatever else you need.

Hopes this helps

Dennis Khoo
Software Engineer
Adapcom, INC.

----- Original Message -----
From: "RamanaYV" <venkataramana_y@mic.co.in>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, February 18, 2004 8:11 PM
Subject: PPCBOOT in customised MPC860T board


>
> I was working in MPC860T customised board and trying to port linux
through
> PPCBOOT.
>
> can you give me breif guidence to boot PPCBOOT in my board and to port
> linux-2.4.19 based kernel.
>
> Thank you,
> Ramana
>
>


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

  reply	other threads:[~2004-02-19 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19  4:11 PPCBOOT in customised MPC860T board RamanaYV
2004-02-19 19:09 ` Dennis Khoo [this message]
2004-02-19 19:48   ` Wolfgang Denk
2004-02-19 19:43 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-02-20  4:53 Thamarai Selvan
2004-02-20  9:01 ` 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='000001c3f71c$1372ee30$7ec7c7c7@dkhoo' \
    --to=dkhoo@atmxdsl.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=venkataramana_y@mic.co.in \
    /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).