From: Jeff Angielski <jeff@theptrgroup.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot fw_setenv does not write
Date: Mon, 02 Jul 2007 15:51:16 -0400 [thread overview]
Message-ID: <1183405876.9292.23.camel@jaalaptop> (raw)
In-Reply-To: <46891B8F.3020200@bioingenieria.es>
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.
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
next prev parent reply other threads:[~2007-07-02 19:51 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 [this message]
2007-07-03 9:14 ` Victor Librado
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=1183405876.9292.23.camel@jaalaptop \
--to=jeff@theptrgroup.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