From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for Freescale P2020RDB board
Date: Mon, 7 Jun 2010 20:44:13 +0200 [thread overview]
Message-ID: <20100607204413.540d07fe@surf> (raw)
In-Reply-To: <AANLkTilZluCVpvJzNT8FhStCyABMxOtL_Sh_RC9d_Ibh@mail.gmail.com>
Hello Marcus,
On Mon, 7 Jun 2010 18:41:29 +0200
Marcus Tangermann <marcus.tangermann@gmail.com> wrote:
> I try to get a working kernel and image for a Freescale PowerPC P2
> based board P2020RDB using buildroot 2010.05.
> In menuconfig I've chosen a PowerPC generic architecture with uClibc
> 0.9.30 and gcc 4.4.4.
> The compiled images (kernel and ext2 rootfs) don't work. After
> loading them via tftp and u-boot, the machine simply stops (=crashes).
The kernel is very specific to each board, so if you don't configure
the kernel compilation process in Buildroot, you'll end up having a
kernel that very likely isn't designed to run on your hardware.
It's also very likely that the support for your board isn't available
in the mainline kernel, so you'd probably have to tell Buildroot to
apply a few patches to the kernel.
As no-one has contributed support for your board to Buildroot, you will
definitely not be able to generate a working kernel image ? out of the
box ?. Some work will be needed.
> To test the rootfs I've manually compiled a kernel using the Freescale
> toolchain. The kernel works but the rootfs crashes the machine after
> loading.
? crash ? is unfortunately a relatively poor description of what's
going on. Do you have the boot log ?
> So, I would be glad if someone has some hints regarding my problem:
> 1. Is it possible to generate a working image for an P2020RDB or are
> there problems with the e500v2 core?
I'm not a PowerPC expert, so I can't say.
> 2. Is it possible to integrate the external toolchain from Freescale
> (gcc-4.3.74-eglibc-2.8.74-dp-2) ?
Depends whether their toolchain supports sysroot or not. Is this
toolchain publicly available ?
> The toolchain type seems to fit neither glibc nor eglibc style.
Well, according to the toolchain name you provided, it is very likely
based on eglibc.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-06-07 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 16:41 [Buildroot] buildroot for Freescale P2020RDB board Marcus Tangermann
2010-06-07 18:44 ` Thomas Petazzoni [this message]
2010-06-07 19:18 ` Marcus Tangermann
2010-06-07 20:22 ` Thomas Petazzoni
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=20100607204413.540d07fe@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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