From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with an MPC8272 build
Date: Fri, 02 Aug 2013 07:49:39 -0300 [thread overview]
Message-ID: <51FB8EC3.3030309@zacarias.com.ar> (raw)
In-Reply-To: <51FAF401.60702@rftechnology.com.au>
On 08/01/2013 08:49 PM, Jason Rennie wrote:
> Buildroot does run successfully, and I have put the rootfs that is made
> on the device and it does boot successfully with the older kernel (well
> mostly, some networking stuff appears to be missing). But when I put the
> new kernel on the device I get nothing. I've tried enabling early kernel
> debugging but with no success (setting the CPM to the addresses
> suggested by the old kernels output). I also don't seem to be able to
> get U-Boot to work and I need to end up breaking out the BDI2000 anytime
> I try to update U-Boot with the newer version as I brick the device.
>
> I have tried with the most basic possible build, not tweaking anything
> and basically just doing the stock buildroot build for the MPC8272
> through to poking and tweaking all sorts of thing.
>
> Any tips? I've attached the old dmesg output if tht helps. I'm
> hopelessly confused and been beating my head against this for a month so
> any help would be greatly appreciated. I'm pretty much out of ideas.
A buildroot .config would help so we can see if there's anything that
could go wrong.
On the toolchain side a 603e should be the target, if that's wrong then
anything you build might fail.
On the kernel side are you building a 2.6.18ish kernel with a new
buildroot or a newer kernel? An updated kernel will very likely need an
updated DTB as well.
Regards.
next prev parent reply other threads:[~2013-08-02 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 23:49 [Buildroot] Problem with an MPC8272 build Jason Rennie
2013-08-02 3:46 ` Charles Krinke
2013-08-02 3:50 ` Jason Rennie
2013-08-02 10:49 ` Gustavo Zacarias [this message]
2013-08-02 18:18 ` Charles Krinke
2013-08-05 0:03 ` Jason Rennie
2013-08-06 0:46 ` Jason Rennie
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=51FB8EC3.3030309@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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