All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] error in fw_printenv
Date: Thu, 17 Sep 2009 13:26:58 +0200	[thread overview]
Message-ID: <m2iqfhdd6l.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4AB2116A.5040004@tataelxsi.co.in> (rahanesh@tataelxsi.co.in's message of "Thu, 17 Sep 2009 16:07:30 +0530")

Hi Rahanesh,

>> Well, that most certainly means that your /dev/mtd0 is not a NOR or
>> NAND flash device.
>>
>>   
>        Now used the fw_printenv under tools/env directory of uboot. It 
> does not have IOCTL error.
>      
>         On issuing a fw_printenv it showd following messages
>  
>          Bad data CRC, Using default environment and printed only few 
> environment variables.

This should have made big warning signs flash up - if data crc was not
correct, it was 99% sure that your configuration wasn't ok.

>           Then i did a fw_setenv bootdelay 6. It showed some messgaes of 
> erasing flash. But it actually erased my uboot itself.

No big wonder here.

>           What might be the issue? config file?

Of course.

>            MTD device name   Device offset   Env. size        Flash 
> sector size   Number of sectors
>             /dev/mtd0                0x0000           
> 0x1000               0x10000
>
>
> What does Device Offset mean?

Offset is the offset into the area mapped by the device file.

> /dev/mtd0 has both uboot as well as  environment variables. Environment 
> variables lie at bottom of /dev/mtd0. Is that the meaning of device offset?

That would be the meaning.  You can always test by reading /dev/mtd0
directly from linux and inspect its contents, i.e. try

dd if=/dev/mtd0 bs=64k count=1 | hexdump -C | less

(or something comparable) and look for your environment.

>    #define CFG_ENV_ADDR        0xAD03F000   (Flash starts at 0xAD000000)
>    #define CFG_ENV_SIZE        0x1000
>    #define CFG_ENV_SECT_SIZE   0x10000
>
>
> These are the macro that i found in include/configs/board.h

This looks completly weird to me.  Can you tell me exactly what board
you are working with?  It looks like this cannot be a NOR flash..

Cheers
  Detlev

-- 
In God we trust.  All others we monitor
                       -- NSA motto
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

      reply	other threads:[~2009-09-17 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 12:53 [U-Boot] error in fw_printenv Rahanesh
2009-09-16 13:28 ` Wolfgang Denk
2009-09-16 13:36   ` Rahanesh
2009-09-16 13:42     ` Wolfgang Denk
2009-09-17  4:32       ` Rahanesh
2009-09-17 10:37       ` Rahanesh
2009-09-17 11:26         ` Detlev Zundel [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=m2iqfhdd6l.fsf@ohwell.denx.de \
    --to=dzu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.