From: Victor Librado <vlibrado@bioingenieria.es>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot fw_setenv does not write
Date: Tue, 03 Jul 2007 11:14:40 +0200 [thread overview]
Message-ID: <468A1380.30607@bioingenieria.es> (raw)
In-Reply-To: <1183405876.9292.23.camel@jaalaptop>
Yes, cat /dev/mtd1 shows the content and the environment variables.
Also linux mtd-utils, flash_eraseall, nandwrite works ... It seems a
problem writing nand in fw_setenv
# ./fw_setenv bootdelay 4
Warning: Bad CRC, using default environment
Unlocking flash...
Done
Erasing old environment...
Done
Writing environment to /dev/mtd1...
CRC write error on /dev/mtd1: Invalid argument
Error: can't write fw_env to flash
It erases but cannot write. Indeed rebooting starts with the default
environment.
Kernel printk:
nand_write: Attempt to write not page aligned data
What may happens? Any with fw_setenv working compiled for arm
architecture and uclibc?
Victor Librado Sancho
Departamento I+D
------------------------------------------------------------------------
Jeff Angielski escribi?:
> On Mon, 2007-07-02 at 17:36 +0200, Victor Librado wrote:
>
>> u-boot environment tool fw_setenv does not work when writing the
>> environment to flash. Working with at91sam9260ek running kernel 2.6.20.
>>
> <snip>
>
>> Offset and environmet size as defined in myboard.h for u-boot
>> compilation. I suppose flash sector size is the erase (block size).
>>
>> Any help please?
>>
>
> There is nothing special about the u-boot env. The parameters are in
> human readable format if you dump the contents [or used to be last time
> I looked]. And the fw_xxx tools just access the flash through the
> normal MTD layer.
>
> With this in mind, can you access that block using the standard
> utilities? cat? dd? einfo? erase? etc. If not, your MTD
> configuration for your board is broken.
>
>
>
prev parent reply other threads:[~2007-07-03 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 15:36 [U-Boot-Users] u-boot fw_setenv does not write Victor Librado
2007-07-02 19:51 ` Jeff Angielski
2007-07-03 9:14 ` Victor Librado [this message]
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=468A1380.30607@bioingenieria.es \
--to=vlibrado@bioingenieria.es \
--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