public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rahanesh <rahanesh@tataelxsi.co.in>
To: u-boot@lists.denx.de
Subject: [U-Boot] Compilation error for fw_printenv
Date: Thu, 17 Sep 2009 18:04:04 +0530	[thread overview]
Message-ID: <4AB22CBC.2000405@tataelxsi.co.in> (raw)
In-Reply-To: <20090917120715.5F0C7832E864@gemini.denx.de>

Dear Wolfgang.
>
> Obviously your cross tool chain does not provide the (needed)
> linux/mtd/mtd.h header file.  Either use a more complete tool chain
> (we use the ELDK), or manually add this file to your cross tool
> chain's headers.
>
>
>   
After cross compiling now i get the following behaviour.
        After issuing a fw_printenv it said
        * Bad data CRC, Using default environment... *and printed out  
few environment variables.*
*
         Then i did a *fw_setenv bootdelay 6*. It showed some messgaes 
of erasing flash. But it actually erased my uboot itself.

         What might be the issue? Any issue with the config file?

          MTD device name   Device offset   Env. size        Flash 
sector size   Number of sectors
           /dev/mtd0                0x0000           
0x1000               0x10000


What does Device Offset mean?

/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?

  #define CFG_ENV_ADDR        0xAD03F000   (Flash starts at 0xAD000000)
  #define CFG_ENV_SIZE        0x1000
  #define CFG_ENV_SECT_SIZE   0x10000


These are the macros that i found in include/configs/board.h

Please help

Thanks
Rahanesh

      reply	other threads:[~2009-09-17 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  9:32 [U-Boot] Compilation error for fw_printenv Rahanesh
2009-09-17 12:07 ` Wolfgang Denk
2009-09-17 12:34   ` Rahanesh [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=4AB22CBC.2000405@tataelxsi.co.in \
    --to=rahanesh@tataelxsi.co.in \
    --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