From: Jason Rennie <jason.rennie@rftechnology.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with an MPC8272 build
Date: Mon, 05 Aug 2013 10:03:10 +1000 [thread overview]
Message-ID: <51FEEBBE.9020206@rftechnology.com.au> (raw)
In-Reply-To: <CALo-6+hZ1-BzFd=uU-9gxazw+Z09R=rXPKY1Q0qC1x46ag8ucA@mail.gmail.com>
Thanks for the reply Charles.
I do know I need to use ttyCPM0/1 (made that mistake already). I agree,
what is wrong with the old S0?
The kernel output I included was from the 2.6.18 build made long ago by
someone who has long since moved on. I figured it would be worth
including as a "last known good" configuration.
Jason
On 3/08/2013 4:18 AM, Charles Krinke wrote:
> Good point Gustavo. If I recall, if the dtb is wrong, one will not get
> as far in the kernel boot process.
>
> In looking at the output, it looks like it is all the way to running
> the init process. Usually when that happens in the systems I work
> with, it is a matter of not satisfying the init process properly. Most
> usually that is a mismatch of the name of the root console.
>
> For whatever reason, in recent years, all the folks making SOC designs
> have gone away from the old, original ttyS0 and every vendor seems to
> have a special name for their serial port, so I thought that would be
> the most fruitful place to look.
>
> Charles
>
> On 8/2/13, Gustavo Zacarias <gustavo@zacarias.com.ar> wrote:
>> 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.
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>
next prev parent reply other threads:[~2013-08-05 0:03 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
2013-08-02 18:18 ` Charles Krinke
2013-08-05 0:03 ` Jason Rennie [this message]
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=51FEEBBE.9020206@rftechnology.com.au \
--to=jason.rennie@rftechnology.com.au \
--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