From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx28: Saving env vars on MMC
Date: Fri, 25 Nov 2011 09:13:27 +0100 [thread overview]
Message-ID: <201111250913.27515.marek.vasut@gmail.com> (raw)
In-Reply-To: <4ECF3FF7.40502@denx.de>
> On 25/11/2011 03:05, Fabio Estevam wrote:
> > Hi,
> >
> > I am trying to save environment variables on a SD card of a MX28EVK
> > board.
> >
> > 'save' command reports no errors, but if I reboot the board then the
> > board no longer boots.
> >
> > In order to recover the boot, I need to reformat the SD card and
> > reflash the u-boot.sd image.
> >
> > I am trying the following configuration taken from FSL U-boot:
> >
> > /*
> >
> > * MMC Driver
> > */
> >
> > #define CONFIG_ENV_IS_IN_MMC
> > #define CONFIG_ENV_OFFSET 0x400
>
> I do not know the details, but this offset is very low and it seems
> taken from other i.MX (MX5). This can overwrite your U-Boot. The
> write_env() function in env_mmc.c converts the offset in a block number,
> and this means you are writing at the block #2.
>
> Because 1 Block=512 byte, can you try to move the offset to a very high
> block ?
>
> > #define CONFIG_ENV_SIZE 0x20000 - 0x400
>
> This seems too much...
>
> Stefano
You have to be careful on the imx28 about the following:
1) sector 0 / first 512 bytes : That's where MBR is
2) sector 2048 + ... : That's where U-Boot is located
But it's strange, there's about 1MB of space between MBR and U-Boot ... can you
actually check the first 2MB of the card and run binary diff on the good and bad
card ? That way you'll see what changed.
M
next prev parent reply other threads:[~2011-11-25 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 2:05 [U-Boot] mx28: Saving env vars on MMC Fabio Estevam
2011-11-25 7:12 ` Stefano Babic
2011-11-25 8:13 ` Marek Vasut [this message]
2011-11-25 13:20 ` Fabio Estevam
2011-11-25 13:42 ` Marek Vasut
2011-11-25 14:30 ` Marek Vasut
2011-11-25 15:06 ` Fabio Estevam
2011-11-25 15:13 ` Marek Vasut
2011-11-26 21:33 ` Fabio Estevam
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=201111250913.27515.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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