From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephan Hoffmann <sho@relinux.de>
Date: Wed, 09 Oct 2013 11:37:47 +0200
Subject: [Buildroot] Booting problem for Beaglebone
In-Reply-To: <52551F22.9090801@univ-st-etienne.fr>
References: <52551F22.9090801@univ-st-etienne.fr>
Message-ID: <525523EB.9040207@relinux.de>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Am 09.10.2013 11:17, schrieb AUBERT alain:
> Hello,
>
> We use Beaglebone board and the lastest version of buildroot 2013.08.1.
>
> We launch/make toolchain/ and/make/ without change options in
> menuconfig, linux-menuconfig, ...
> We program the SD card .
> When the beaglebone board powers up,  the default configuration of
> Uboot takes the kernel at /boot/uImage but the default filesystem
> generated by buildroot  doesn't include the /boot directory.
> So, we change in menuconfig,  the option "Install kernel image to
> /boot in target"
>
> Then, the kernel is well loaded but the kernel tries to mount the root
> filesystem, it doesn't find
> /dev/mmcblk0p2. The message is:
> "Waiting for root device /dev/mmcblk0p2 ..."
>
> It seems that the only block peripherals detected were ram and loop
> but not mmcblk
Hello Alain,

I had the same problem:
http://buildroot-busybox.2317881.n4.nabble.com/BeagleBone-defconfig-broken-td49751.html

Unfortunatelly, I had to focus on other things before coming to a
solution so that my beaglebone still sits in its box without buildroot.

Kind regards

Stephan
>
> Can you help us ?
> Thank you
>
> Alain AUBERT
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


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