From: Kate Alhola <kate@iti.fi>
To: linuxppc-embedded@lists.linuxppc.org
Subject: linuxppc_2_4_mpc5200 / 5200lite first day conclusions
Date: Mon, 03 Nov 2003 00:22:46 +0200 [thread overview]
Message-ID: <3FA583B6.5040409@iti.fi> (raw)
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/
next reply other threads:[~2003-11-02 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 22:22 Kate Alhola [this message]
2003-11-02 23:30 ` linuxppc_2_4_mpc5200 / 5200lite first day conclusions 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=3FA583B6.5040409@iti.fi \
--to=kate@iti.fi \
--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 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.