mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Peter Kuennemann@Crane-Soft" <pkue@crane-soft.de>
Cc: barebox@lists.infradead.org
Subject: Re: Booting PhyTec PCM043/IMX35  from USB/SD-Card
Date: Thu, 28 Jun 2012 12:43:41 +0200	[thread overview]
Message-ID: <20120628104341.GW1623@pengutronix.de> (raw)
In-Reply-To: <4FEBFF6C.6010304@crane-soft.de>

On Thu, Jun 28, 2012 at 08:53:32AM +0200, Peter Kuennemann@Crane-Soft wrote:
> > 
> > Has this been solved in the mean time? The above looks correct, I have
> > no idea what's wrong.
> 
> The case has been partly solved now. I am able to boot from NAND and NOR but I cannot
> access the MMC. Reason for the kernel messages ...(driver?) above was a missing device
> "mxc_nand" in the kernel parms for mtdparts:
> 
>     mtdparts=physmap-flash.0:256k(barebox)ro,128k(bareboxenv),2M(kernel),-(root); \
>     mxc_nand:256k(barebox)ro,128k(bareboxenv),2M(kernel),-(root)
> 
> However, I still cannot access the mmc from barebox. It would be enough to be able to
> read the mmc. I want to be able to store kernel or rootfs image updates on the mmc
> and flash them to either NAND or NOR after reboot to enable remote update services.
> 
> Question: "How can I access the MMC from barebox (read only may be sufficient)

The pcm043 currently does not have mmc support. You have to add this to
the board file:

imx35_add_mmc0(NULL);

or

imx35_add_mmc1(NULL);

depending on which port is routed to the slot. Also you have to setup
the iomuxer (you can probably copy the pin settings from the kernel). Of
course you also have to enable MMC support in the config.

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:[~2012-06-28 10:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 15:43 Peter Kuennemann@Crane-Soft
2012-05-24 19:55 ` Sascha Hauer
2012-05-25  9:35   ` Peter Kuennemann@Crane-Soft
2012-05-31 18:27     ` Sascha Hauer
2012-05-31 19:13       ` CRANESOFT
2012-06-28  6:53       ` Peter Kuennemann@Crane-Soft
2012-06-28 10:43         ` Sascha Hauer [this message]
2012-06-28 13:36           ` Peter Kuennemann@Crane-Soft
2012-06-28 13:54             ` Sascha Hauer
2012-08-23 17:59           ` Peter
2012-08-24  8:46             ` Jan Lübbe
2012-08-27  7:45               ` Peter

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=20120628104341.GW1623@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=pkue@crane-soft.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