public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Christian Erhardt <christian.erhardt@mojo2k.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] fw_readenv not working with uboot.env stored on FAT partition BAD CRC
Date: Mon, 29 Dec 2014 13:43:40 +0100	[thread overview]
Message-ID: <54A14C7C.7050206@mojo2k.de> (raw)

Hello,

i'm using a Raspberry Pi with u-boot. I'm building a stock RPI Kernel 
3.12.y with buildroot. The u-boot version is 2015.01-rc3.

U-Boot is working fine and when i call saveenv a file uboot.env is 
written to the first FAT Partition on the SD Card. But when i try to 
access the boot params with fw_readenv, i always get the BAD CRC error. 
I tried every possible configuration in fw_env.config, but it will not work.

if first tried the obvious configuration

/dev/mmcblk0p1    0x0000    0x4000

does not work, then i tried to calculate the offset from /dev/mmcblk0:

/dev/mmcblk0p1    0x100000    0x4000

0x100000 because startsecotor is 2048 * 512 byte = 1048576 = 0x100000 in hex

It will not work. I'm a little confused if this configuration makes 
sense at all, i thought, with the rpi config, fw_readenv will look for 
the file uboot.env in the given partition?

My partion layout is as follows

243 heads, 62 sectors/track, 1022 cylinders, total 15407104 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xee294a37

    Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *        2048      104447       51200    e  W95 FAT16 (LBA)
/dev/sdf2          104448      411647      153600   83  Linux
/dev/sdf3          411648      718847      153600   83  Linux
/dev/sdf4          718848    15407103     7344128   83  Linux


Regards

Christian Erhardt

                 reply	other threads:[~2014-12-29 12:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54A14C7C.7050206@mojo2k.de \
    --to=christian.erhardt@mojo2k.de \
    --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