From: ivica@asist-traffic.com
To: linuxppc-embedded@ozlabs.org
Subject: MPC5200 toolchain test
Date: Thu, 25 Nov 2004 16:24:32 +0100 [thread overview]
Message-ID: <41A5F930.3080104@asist-traffic.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1724 bytes --]
Greeting!
I have a MPC5200 based custom board with preloaded u-boot.
My job is to create some sort of development environment, build
linux kernel and userland environment and in the end test the hardware
before larger series are built.
So far I managed to create GNU toolchain for it with crostool from
Dan Kegel. Everything was built without any problems. Of course,
I wanted to test this toolchain so I wanted to compile a simple
hello_world program load it into the memory of my MPC5200 board
and run it. So far I've failed. I admit. I don't know how to compile
a program to run without the OS. But I have some clues. I think it
needs to be linked properly so all the things OS does for you are inserted
into the binary image that is supposed to get executed. I need some detail
understanding on this.
Anyhow I want to do this before I compile kernel. Since I'm talking
about the kernel let me ask you what kernel you suggest for MPC5200?
The latest 2.6.10-rc or the one Sylvain Munaut is maintaining?
Next ... I would like to create a development environment that is totally
"closed" from my system and I want all the crosstools in it. This way
I could ensure none of my native tools are conflicting with cross
development.
I keep hearing about jails and sanboxes but I don't know what they mean.
Ok maybe I really need to google it out here but I'm beat. I'm googling
three days already. :D
Any tips on creating these kind of environments would be greatly
appreciated.
I will attach scripts which I used to create toolchain. I hope I did it
correctly.
My sources of documentation are google, IRC and these two books:
Building Embedded Linux, Karim Yaghmour
Programming Embeded Systems, Michael Barr
TIA,
Ivica
[-- Attachment #2: demo-ppc603e.sh --]
[-- Type: text/plain, Size: 632 bytes --]
#!/bin/sh
set -ex
TARBALLS_DIR=$HOME/tmp/downloads
RESULT_TOP=/opt/MPC5200-crosstools
export TARBALLS_DIR RESULT_TOP
GCC_LANGUAGES="c,c++"
export GCC_LANGUAGES
# Really, you should do the mkdir before running this,
# and chown /opt/crosstool to yourself so you don't need to run as root.
mkdir -p $RESULT_TOP
# Build the toolchain. Takes a couple hours and a couple gigabytes.
#eval `cat powerpc-604.dat gcc-3.4.0-glibc-2.3.2.dat` sh all.sh --builduserland --notest
eval `cat powerpc-603e.dat gcc-3.4.1-glibc-2.3.3.dat` sh all.sh --notest
#eval `cat powerpc-604.dat gcc-3.4.1-glibc-20040827.dat` sh all.sh --notest
echo Done.
[-- Attachment #3: powerpc-603e.dat --]
[-- Type: text/plain, Size: 125 bytes --]
TARGET=powerpc-603e-linux-gnu
TARGET_CFLAGS="-O -mcpu=603e"
GCC_EXTRA_CONFIG="--with-cpu=603e --enable-cxx-flags=-mcpu=603e"
next reply other threads:[~2004-11-25 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 15:24 ivica [this message]
2004-11-25 22:58 ` MPC5200 toolchain test Wolfgang Denk
2004-11-26 10:48 ` ivica
2004-11-26 14:36 ` Wolfgang Denk
2004-11-27 18:42 ` Jon Masters
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=41A5F930.3080104@asist-traffic.com \
--to=ivica@asist-traffic.com \
--cc=linuxppc-embedded@ozlabs.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).