Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] BeagleBone defconfig broken?
Date: Fri, 16 Aug 2013 10:23:17 +0200	[thread overview]
Message-ID: <520DE175.1050103@relinux.de> (raw)

Hello all,

I am currently trying to get the latest buildroot to run on my
beaglebone with little success. The last version that seem to run out of
the box is 2012.08, where I can simply copy MLO, u-boot.img and uImage
to the boot partition, dd rootfs.ext2 to the second partition and the
system works.

The current build fails to boot, because u-boot expects the image and
dts in /boot within the root filesystem. After putting them there with a
post build script, u-boot starts the kernel, but the kernel fails to
mount root:
> [    1.509962] Waiting for root device /dev/mmcblk0p2...
The SD partitions seem o.k.:
> Disk /dev/sdi: 3965 MB, 3965190144 bytes
> 255 heads, 63 sectors/track, 482 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdi1   *           1           9       72292    c  W95 FAT32 (LBA)
> /dev/sdi2              10         133      996030   83  Linux
and /dev/mmcblk0p2 sounds like the right partition.

Can anybody give a hint where to look further?

Kind regards

Stephan

-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

             reply	other threads:[~2013-08-16  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  8:23 Stephan Hoffmann [this message]
2013-08-18 17:48 ` [Buildroot] BeagleBone defconfig broken? Ivan Sergeev
2013-08-19  8:17   ` Stephan Hoffmann
2013-08-19 17:54     ` Ivan Sergeev
2013-08-19 17:57       ` Ivan Sergeev
2013-08-19 18:23         ` Stephan Hoffmann

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=520DE175.1050103@relinux.de \
    --to=sho@relinux.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