From: Peter <sailingsmoky@googlemail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Booting PhyTec PCM043/IMX35 from USB/SD-Card
Date: Thu, 23 Aug 2012 19:59:55 +0200 [thread overview]
Message-ID: <50366F9B.2080007@crane-soft.de> (raw)
In-Reply-To: <20120628104341.GW1623@pengutronix.de>
Am 28.06.2012 12:43, schrieb Sascha Hauer:
> 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.
...
>> 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
>
Sascha I'ld like to pick up this thread again abd I hope that someone can
give me the hint to help me out here.
I managed to access the mmc applying your hints above. The card seem to
appear correctly with all it's partitions:
---
imx-esdhc@mci0: registered as mci0
mci@mci0: registered disk0
ehci@ehci0: USB EHCI 1.00
---
barebox:/ ls /dev
defaultenv disk0 disk0.0
disk0.1 env0 full
---
I am able to boot the kernel from NOR flash and use the mmc as rootfs. However
I did not yet find a way to boot the kernel from the MMC. I set up the MMC
with 255 heads, 63 sectors/track, 245 cylinders and formated partition 1 as
VFAT and made it bootable. I then copied uImage to it. Partition 2 contains
the rootfs which can be used when booting the kernel from flash.
Barebox /env/config contains: (besides others)
...
kernel_loc=disk
rootfs_loc=disk
rootfs_type=ext2
rootfs_part_linux_dev=mmcblk0p2
kernel_part=disk0.0
...
Trying to boot results in:
booting kernel from /dev/disk0.0
and then followed by the barebox prompt.
barebox:/
Kernel parameters are: console=ttymxc0,115200 video=mx3fb:CTP-CLAA070LC0ACW ip=dhcp root=/dev/mmcblk0p2 rootfstype=ext2 noinitrd rootwait
mtdparts=physmap-flash.0:256k(barebox)ro,128k(bareboxenv),2M(kernel),-(root);:256k(barebox)ro,128k(bareboxenv),2M(kernel),-(root)
A little help would be very much appreciated.
Regards and many thanks for your support.
Peter
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-08-23 18:00 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
2012-06-28 13:36 ` Peter Kuennemann@Crane-Soft
2012-06-28 13:54 ` Sascha Hauer
2012-08-23 17:59 ` Peter [this message]
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=50366F9B.2080007@crane-soft.de \
--to=sailingsmoky@googlemail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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