mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: ManuelCurcio@Eaton.com
Cc: barebox@lists.infradead.org
Subject: Re: beagle bone black: problem of boot from eMMC
Date: Mon, 5 Jan 2015 10:59:05 +0100	[thread overview]
Message-ID: <20150105095905.GF30369@pengutronix.de> (raw)
In-Reply-To: <1420041155.29284.24.camel@eaton.com>

On Wed, Dec 31, 2014 at 02:52:39PM +0000, ManuelCurcio@Eaton.com wrote:
> Hi,
> 
> From the lasted Barebox version (barebox-2014.12.0): 
> 
> I generated a MLO and a barebox.bin for the BeagleBone
> (am335x_defconfig&am335x_mlo_defconfig config file) with the
> modification of : 
> [PATCH] net: cpsw: Fix crashes on beaglebone black   ledphilippe at
> gmail.com 
> that I copied in a SD card. It work fine.
> 
> 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
> <---------
> 
> 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. 
> So my correction,although improving the situation, is not exactly the
> correction to do. Some one can help me ? 

In your bootlog above mmc@481d8000 (which is the eMMC) is not
registered. I had a quick look at the code and didn't find anything
obvious. I can have a closer look this evening.

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

      parent reply	other threads:[~2015-01-05  9:59 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
2015-01-14  8:43     ` ManuelCurcio
2015-01-05  9:59 ` Sascha Hauer [this message]

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=20150105095905.GF30369@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=ManuelCurcio@Eaton.com \
    --cc=barebox@lists.infradead.org \
    /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