linuxppc_2_4_mpc5200 / 5200lite first day conclusions

linuxppc_2_4_mpc5200 / 5200lite first day conclusions

[Kate Alhola]

I have spent a long day hacking and got it
running with by brand new lite5200 EVB

Just for others there is little summary of my experiencies

- Macraigor Wiggler/ocd_cmdr does not yet support mpc5200
  so there is no low cost ocd tool ( or least i have not found one )
  The COP tools are not compatoble between processors
  when there seems to be relativelly good compatibility between BDM tools
  based least on experience with MPC8xx and MPC555 series

---> continue searching low cost tool or just wait ...... or hack one
       without motorola specs


- It looks like that it is not so easy any more compile non u-boot
  version of kernel. Make zImage gives one compilation error
  mentioned and does not even work after it.

---> Easiest way is to move to u-boot

- With u-boot Wolfgang Denk give advice to make ram
   loadable version. I just did not find easy instructions
   to make it.

--> Find out to change TEXT_BASE from board/icecube/config.mk
  Notice also that there is in icecube.c CFG_RAMBOOT
  that needs to be defined in icecube.h that it works in RAM
 with these modifications it work in RAM

-- Compile u-boot flashable version. Even it
  is vompiled for 0xff800000 base address it looks a like
  that it needs still CFG_RAMBOOT if it is
  started from dbug with go ff800100

-- Now you can get kernel booting from uboot with
   tftpboot 200000 uImage
   bootm 200000

- Try to meke your own ramdisk image. There is still
  in uboot manual pages just mentioned "old wau" , read
  kernel Documentation/initrd.txt . The way i used
  to do it does not work any more. uboot just saus
  invalid magic number. Try found out what is wrong

-- > Find out that it needs new utility to make u-boot
  compatible header
./u-boot-1.0.0/tools/mkimage -n 'Kates ramdisk'  -A ppc -O linux -T
ramdisk -C gzip -d initrd.gz initrd.image

- Got kernel died with "cant fork init",
-->find out that your old linux kernel utilities, busybox, init
 jne are no longer copmpatible with libraries, make or find new set

Looks a like that it is doable but it needs lot of time and
once again "reverse documentation read" that is that found
first a solution and then you find documentation ......

May be good step by step instructions are needed someones that
won't spend all day long hacking

-- After midnight you are hungry, tired and five cats and dog are asking
food
--> feed them and go to sauna ... ;)


Kate


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

Re: linuxppc_2_4_mpc5200 / 5200lite first day conclusions

[Wolfgang Denk]

In message <3FA583B6.5040409@iti.fi> you wrote:
>
> - It looks like that it is not so easy any more compile non u-boot
>   version of kernel. Make zImage gives one compilation error
>   mentioned and does not even work after it.

zImage  requires  a  Linux  bootstap  loader;  this  has   not   been
implemented (yet). We use U-Boot so we don't need it.

> ---> Easiest way is to move to u-boot

Right :-)

> - With u-boot Wolfgang Denk give advice to make ram
>    loadable version. I just did not find easy instructions
>    to make it.

We do NOT recommend to use a U-Boot version booting from RAM; you can
do this if you really want and if you know what you're doing; what we
recommend is to use the standard version and install  it  instead  of
the original bootloader.

> -- Compile u-boot flashable version. Even it
>   is vompiled for 0xff800000 base address it looks a like
>   that it needs still CFG_RAMBOOT if it is
>   started from dbug with go ff800100

Building a low-boot configuration requires more than  just  modifying
the flash base address.

> - Try to meke your own ramdisk image. There is still
>   in uboot manual pages just mentioned "old wau" , read
>   kernel Documentation/initrd.txt . The way i used
>   to do it does not work any more. uboot just saus
>   invalid magic number. Try found out what is wrong

Start reading the U-Boot manual at
http://www.denx.de/twiki/bin/view/DULG/Manual

You   can   find   pre-built   ramdisk   images   for   testing    at
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/ (use the ppc_82xx
version for the MPC5200).

> - Got kernel died with "cant fork init",
> -->find out that your old linux kernel utilities, busybox, init
>  jne are no longer copmpatible with libraries, make or find new set

You must have done something wrong when building the  ramdisk  image.
This works fine for me.

> Looks a like that it is doable but it needs lot of time and
> once again "reverse documentation read" that is that found
> first a solution and then you find documentation ......

Please feel free to contribute to the DULG
(http://www.denx.de/twiki/bin/view/DULG/Manual).

This is a wiki, so everybody can help improving it.

> May be good step by step instructions are needed someones that
> won't spend all day long hacking

Maybe you can point out what is mussing in the DULG, and we add it?

> -- After midnight you are hungry, tired and five cats and dog are asking
> food
> --> feed them and go to sauna ... ;)

I guess I know how that feels (even without cats or dogs).


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
On the subject of C program indentation: "In My Egotistical  Opinion,
most  people's  C  programs  should be indented six feet downward and
covered with dirt."                               - Blair P. Houghton

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