Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Torsten Mohr <tmohr@s.netic.de>
To: buildroot@busybox.net
Subject: [Buildroot] 2011.02, BeagleBoard-xM, linux-2.6.37 does not boot
Date: Mon, 21 Mar 2011 22:43:38 +0100	[thread overview]
Message-ID: <201103212243.38429.tmohr@s.netic.de> (raw)
In-Reply-To: <AANLkTi=t3L2WbrJXY0QRejbZTVKfNPbeSLjBazO3+E8T@mail.gmail.com>

Hello,

thank you for your hints,

> > Not sure if i missed something, some questions came up:
> > 
> > - does buildroot use the correct kernel for BeagleBoard-xM?
> > - do i need to apply patches?
> > - what configuration file do i need to chose?
> > - does u-boot need special options to boot that kernel?
> > 
> > It would be great if anybody had some hints for me.
> 
> Maybe you need setenv console=/dev/ttyO2

When configuring the kernel i found out that this is actually set as the 
internal CMDLINE.

Also (other hint), the kernel debugging options in the kernel are set.

I compiled a kernel today and i can boot it, it does not boot using the 
standard scripts that came with the Angstroem distro.

When interrupting standard boot and giving:

mmc init
mmc rescan 0
loaduimage
bootm 0x82000000

Then the kernel starts to boot.


Thanks for your hints,
Torsten.

  reply	other threads:[~2011-03-21 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20 22:25 [Buildroot] 2011.02, BeagleBoard-xM, linux-2.6.37 does not boot Torsten Mohr
2011-03-21  7:51 ` Bob Liu
2011-03-21 21:43   ` Torsten Mohr [this message]
2011-03-22  4:35     ` [Buildroot] build without linux, busybox, - just buildroot internal toolchain Steve Calfee
2011-03-22  5:51       ` Baruch Siach

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=201103212243.38429.tmohr@s.netic.de \
    --to=tmohr@s.netic.de \
    --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