All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ficheux <pierre.ficheux@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Booting problem for Beaglebone
Date: Mon, 23 Dec 2013 16:08:18 +0100 (CET)	[thread overview]
Message-ID: <800187025.16985041.1387811298810.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <52565A42.1080707@univ-st-etienne.fr>

Hi,

I still have the same problem with recent BR (2013.11 or Git) and Beaglebone Black (waiting for root device)

[    4.690564]      host=10.5.16.129, domain=daviel.openwide.fr., nis-domain=(none)
[    4.698407]      bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath=
[    4.704779]      nameserver0=10.5.1.1[    4.712875] Waiting for root device /dev/mmcblk0p4...



Any idea?

Thx by advance



----- Mail original -----
> De: "AUBERT alain" <alain.aubert@univ-st-etienne.fr>
> ?: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> Cc: buildroot at busybox.net
> Envoy?: Jeudi 10 Octobre 2013 09:41:54
> Objet: Re: [Buildroot] Booting problem for Beaglebone
> 
> Dear Thomas
> 
> You find in attached file the buildroot  .config file
> 
> Best regards
> 
> Alain
> 
> 
> 
> 
> 
> Le 09/10/2013 17:36, Thomas Petazzoni a ?crit :
> > Dear AUBERT alain,
> >
> > On Wed, 09 Oct 2013 17:15:13 +0200, AUBERT alain wrote:
> >
> >> We have already done all steps of the building as you indicated in
> >> your mail
> >>
> >> The 2 partitions are visible in Uboot with correct pararmeters.
> >> We have done fatls mmc 0:1 and ext2ls mmc 0:2 to see the contents
> >>
> >> Moreover, we have done the same operation with buildroot 2012.05
> >> and the
> >> beaglebone board works fine
> >>
> >> It seems that the problem comes from the use of Flattened devices
> >> tree
> >> in the new version of buildroot
> >>
> >> You can find the bootlog in the attached file
> > I am not following closely the BeagleBone kernels, but from the
> > boot
> > log it seems like the MMC card is not detected. Several
> > possibilities:
> >
> >   * The MMC support is not enabled in the kernel configuration, or
> >   the
> >     proper MMC driver.
> >
> >   * The MMC device is not described in the Device Tree and/or the
> >     support for MMC on this platform is not available.
> >
> > The version of the kernel being displayed is just 3.8.11, which
> > indicates a mainline kernel (which doesn't support MMC on AM335x,
> > as
> > far as I know). However, our beaglebone_defconfig uses a TI custom
> > kernel, which I believe, should show probably show a different
> > kernel
> > version than just 3.8.11.
> >
> > Can you send us your Buildroot .config file?
> >
> > Best regards,
> >
> > Thomas
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
Pierre FICHEUX -/- CTO OW/OWI, France -\- pierre.ficheux at openwide.fr
                                         http://ingenierie.openwide.fr
                                         http://www.linuxembedded.fr
I would love to change the world, but they won't give me the source code

  reply	other threads:[~2013-12-23 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  9:17 [Buildroot] Booting problem for Beaglebone AUBERT alain
2013-10-09  9:37 ` Stephan Hoffmann
2013-10-09 11:55 ` Thomas Petazzoni
2013-10-09 15:15   ` AUBERT alain
2013-10-09 15:36     ` Thomas Petazzoni
2013-10-10  7:41       ` AUBERT alain
2013-12-23 15:08         ` Pierre Ficheux [this message]
2013-12-23 16:45           ` Thomas Petazzoni
2013-12-23 16:51             ` Pierre Ficheux
2013-12-23 21:47               ` Thomas Petazzoni

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=800187025.16985041.1387811298810.JavaMail.root@openwide.fr \
    --to=pierre.ficheux@openwide.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.