mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Teresa Gámez" <t.gamez@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: beagle bone black: problem of boot from eMMC
Date: Tue, 6 Jan 2015 10:06:24 +0100	[thread overview]
Message-ID: <20150106090624.GH4544@pengutronix.de> (raw)
In-Reply-To: <1420450912.6731.16.camel@lws-gamez.phytec.de>

On Mon, Jan 05, 2015 at 10:41:52AM +0100, Teresa Gámez wrote:
> Hello Manuel,
> 
> Am Mittwoch, den 31.12.2014, 14:52 +0000 schrieb ManuelCurcio@Eaton.com:
> > 
> > After, I wanted to boot from the the internal eMMC. 
> > So after boot from sd card, I mounted the eMMC (mount /dev/mmc1.0) and
> > copied the MLO and barebox.bin in the /mnt/mmc1.0 folder.
> > 
> > When I try to boot from the internal eMMC ,I have the following error: 
> > --------->
> > barebox 2014.12.0 #2 Wed Dec 31 15:29:16 GMT 2014
> > 
> > 
> > Board: TI AM335x BeagleBone
> > detected 'BeagleBone Black'
> > omap-hsmmc 48060000.mmc: registered as 48060000.mmc
> > booting from MMC
> > fat fat0: probe failed: error 22
> > Unable to mount  (-22)
> > booting failed
> > <---------
> 
> This issue comes from commit:
> 
> commit 0d6392de4ad824a6553c0e3e3e18edef689a7c85
> Author: Sascha Hauer <s.hauer@pengutronix.de>
> Date:   Thu Jun 5 12:09:07 2014 +0200
> 
>     ARM: AM335x: Beaglebone: Use stripped down devicetree for MLO
> 
> For the MLO only the am335x-bone-common.dtsi is used to create the
> device tree. But this does not have the emmc support included.

Damn. Somehow I knew I was guilty :(

> 
> > 
> > I tried myself to find a 'correction' by added the call of
> > am33xx_of_register_bootdevice(void) function at the end of the static
> > int beaglebone_devices_init(void) function. With this modification,
> > sometime (depending of the last boot: from SD Card or from eMMC)  I can
> > boot, someting not. 
> 
> What you are also missing is a disabled emmc node from the
> am335x-boneblack.dts in the am335x-bone-common.dtsi.

I just sent a patch which fixes this.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2015-01-06  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31 14:52 ManuelCurcio
2015-01-05  9:41 ` Teresa Gámez
2015-01-06  9:06   ` Sascha Hauer [this message]
2015-01-14  8:43     ` ManuelCurcio
2015-01-05  9:59 ` Sascha Hauer

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=20150106090624.GH4544@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=t.gamez@phytec.de \
    /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