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


Am 28.06.2012 12:43, schrieb Sascha Hauer:
>> ...
>> 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
> 
> 

I have tried to update the board code accordingly but stumbled upon another
problem. The size of barebox increased to 0x40bb7 so I changed the
partition definitions in pcm043.c as follows:

#define CONFIG_MX35_BBSIZE      0x42000
   ...
   devfs_add_partition("nor0", 0x00000, CONFIG_MX35_BBSIZE, PARTITION_FIXED, "self0"); /* ourself */
   devfs_add_partition("nor0", CONFIG_MX35_BBSIZE, 0x20000, PARTITION_FIXED, "env0");
   ...
Barebox boots OK but after having saved the environment (saveenv) it dow not boot anymore.

Barebox boot messages ...

Malloc space: 0x86e00000 -> 0x87dfffff (size 16 MB)
Stack space : 0x86df8000 -> 0x86e00000 (size 32 kB)
envfs: wrong magic on /dev/env0
no valid environment found on /dev/env0. Using default environment   <== expected
running /env/bin/init...

devinfo <== What is defined ?
...
`---- cfi_flash0
     `---- 0x00000000-0x01ffffff: /dev/nor0
     `---- 0x00000000-0x00041fff: /dev/self0
     `---- 0x00042000-0x0005ffff: /dev/env0

saveenv  <== save the environment
reset    <== nothing after here

What is wrong here?

Peter

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

  reply	other threads:[~2012-06-28 13:36 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 [this message]
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=4FEC5DD6.4040308@crane-soft.de \
    --to=pkue@crane-soft.de \
    --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