public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] fw_setenv broken?
Date: Wed, 17 Nov 2010 17:56:11 +0100	[thread overview]
Message-ID: <4CE4092B.7090209@denx.de> (raw)
In-Reply-To: <1290011424.2927.1123.camel@quadra>

On 11/17/2010 05:30 PM, Steve Sakoman wrote:
> I'm seeing some strange behavior with the fw_setenv tools on OMAP.
> 
> Here's what I see when using the tools on OMAP (overo in this case):
> 
> 1. fw_printenv prints the environment with no issues [1]
> 2. fw_setenv allows me to change a variable with no reported errors [2]
> 3. fw_printenv will print the changed environment, however the variables
> are not sorted [3]

I tested yesterday on a davinci board, I can confirm this behavior, I
have not thought was an error. I do not see any code in fw_env.c to sort
variables. I konow the variables are sorted in u-boot, but do we ever
have this feature on the userland fw_printenv ?

> 4. Since all seems well at this point, I reboot.  There is an error
> reading the new environment [4]

I cannot confirm that. I made the same test, environment is stored on a
SPI flash. No CRC error, the environment was restored correctly after a
reset and/or power cycle.

> I added debug printf's to readenv() in env_nand.c and the root cause is
> an error return from ret=nand_read(&nand_info[0], offset, &len,
> char_ptr)).  I get an error code of -74
> 
> Before I spend too much time on this I wanted to check to see if others
> are seeing this issue, or whether it might be OMAP specific.

At least this should not be a general failure, because it works on my
target. It could be also nand specific.

Best regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2010-11-17 16:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 16:30 [U-Boot] fw_setenv broken? Steve Sakoman
2010-11-17 16:56 ` Stefano Babic [this message]
2010-11-17 17:39   ` Wolfgang Denk
2010-11-17 17:51     ` Steve Sakoman
2010-11-17 18:13     ` Mike Frysinger
2010-11-17 18:28       ` Wolfgang Denk
2010-11-17 20:05     ` Steve Sakoman
2010-11-17 20:47       ` Wolfgang Denk
2010-11-17 21:29         ` Steve Sakoman
2010-11-17 21:40           ` Wolfgang Denk
2010-11-17 21:55             ` Steve Sakoman
2010-11-17 22:08             ` Scott Wood
2010-11-17 22:48               ` Steve Sakoman
2010-11-17 23:05                 ` Wolfgang Denk
2010-11-19  0:13               ` Steve Sakoman
2010-11-19  0:20                 ` Scott Wood
2010-11-19  0:33                   ` Steve Sakoman
2010-11-19  5:09                   ` Steve Sakoman

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=4CE4092B.7090209@denx.de \
    --to=sbabic@denx.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