From: "Teresa Gámez" <t.gamez@phytec.de>
To: ManuelCurcio@Eaton.com
Cc: barebox@lists.infradead.org
Subject: Re: beagle bone black: problem of boot from eMMC
Date: Mon, 05 Jan 2015 10:41:52 +0100 [thread overview]
Message-ID: <1420450912.6731.16.camel@lws-gamez.phytec.de> (raw)
In-Reply-To: <1420041155.29284.24.camel@eaton.com>
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.
>
> 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.
This may help.
Regards,
Teresa
> So my correction,although improving the situation, is not exactly the
> correction to do. Some one can help me ?
>
> Thanks very much !
>
>
>
> -----------------------------
> Eaton Industries (France) S.A.S ~ Siège social: 110 Rue Blaise Pascal, Immeuble Le Viséo - Bâtiment A Innovallée, 38330, Montbonnot-St.-Martin, France ~ Lieu d'enregistrement au registre du commerce: Grenoble ~ Numéro d'enregistrement: 509 653 176 ~ Capital social souscrit et liberé:€ 16215441 ~ Numéro de TVA: FR47509653176
>
> -----------------------------
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-01-05 9:42 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 [this message]
2015-01-06 9:06 ` Sascha Hauer
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=1420450912.6731.16.camel@lws-gamez.phytec.de \
--to=t.gamez@phytec.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