From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for Freescale P2020RDB board
Date: Mon, 7 Jun 2010 22:22:19 +0200 [thread overview]
Message-ID: <20100607222219.60312e32@surf> (raw)
In-Reply-To: <FCD7AA7B-967C-436A-8C06-381EEBD8C729@gmail.com>
On Mon, 7 Jun 2010 21:18:03 +0200
Marcus Tangermann <marcus.tangermann@gmail.com> wrote:
> The board is supported by recent kernels as I've managed to build a
> working 2.6.33 from kernel.org using the toolchain provided by
> Freescale. So maybe my problems result from the toolchain generated
> within buildroot.
Ah, great. You'll still have to tell how the kernel should be
configured, anyway.
> Sorry, I know. Unfortunately there is no further information. The
> board simply stops, no console output.
Ok, so it might be a non-working userspace or an incorrect console=
configuration in the kernel command line.
> You can download the whole BSP from Freescale:
> http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=P2020&fpsp=1&tab=Design_Tools_Tab
Which one exactly ? Those are multi-GB downloads, I'd prefer to pick
the right one from the beginning. Or maybe, better, you can put the
toolchain only online ?
> Yes, sounds reasonable ;-) Any chance to use eglibc based external
> toolchains?
If they support --sysroot, then yes. If then don't, then no.
What does CROSS-gcc -v from your toolchain returns ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-06-07 20:22 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
2010-06-07 19:18 ` Marcus Tangermann
2010-06-07 20:22 ` Thomas Petazzoni [this message]
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=20100607222219.60312e32@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