From: Zaheer Sheriff <zaheer.sheriff@easunreyrolle.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] How to resolve CRC issue in Uboot and maintain the env variables
Date: Fri, 25 Nov 2011 19:12:29 +0530 [thread overview]
Message-ID: <4ECF9B45.8060409@easunreyrolle.com> (raw)
In-Reply-To: <4ECF8892.1010402@denx.de>
Stefan,
I thought the error is generic, I never know it is processor or board
specific error.
Here are the details:
OMAPL138 EVM board
u-boot version 2011.9 NOvember release.
modified env in da850 config file as :
-------
/*
* Linux Information
*/
#define LINUX_BOOT_PARAM_ADDR (PHYS_SDRAM_1 + 0x100)
#define CONFIG_CMDLINE_TAG
#define CONFIG_SETUP_MEMORY_TAGS
#define CONFIG_BOOTARGS "mem=32M console=ttyS2,115200n8 noinitrd rw
ip=10.1.5.115:10.1.5.69:10.1.5.1:255.255.255.0::eth0: root=/dev/nfs
nfsroot=10.1.5.69:/home/targetNFS"
#define CONFIG_BOOTCOMMAND "if mmc rescan 0:1; then fatload mmc 0:1
0xc0700000 uImage; bootm c0700000; fi;"
#define CONFIG_BOOTDELAY 3
#define CONFIG_EXTRA_ENV_SETTINGS "ethaddr=00:08:ee:03:6a:c4\0"
---------------------------
Will this extra env creates CRC error.
this is my env variable:
setenv bootcmd 'sf probe 0;sf read c0008000 40000 340000; go c0008000'
Image file size is: 335268 hex
how to resolve this.
Zaheer
On Friday, November 25, 2011 5:52:42 PM, Stefano Babic wrote:
> On 25/11/2011 11:51, Zaheer Sheriff wrote:
>> Hi,
>> When I got the warning like
>>
>> **** Warning - bad CRC, using default environment*
>>
>> I came across the reason for this in
>> _http://www.denx.de/wiki/view/DULG/WarningBadCRCUsingDefaultEnvironment_
>>
>> Question:
>> I have ported U-Boot to a custom board. It seems to boot OK, but it
>> prints:
>>
>> *** Warning - bad CRC, using default environment
>>
>> Why?
>> Answer:
>> Most probably everything is OK. The message is printed because the
>> flash sector or ERPROM containing the environment variables has
>> never been initialized yet. The message will go away as soon as you
>> save the envrionment variables using the |*saveenv*| command.
>>
>>
>>
>> How to resolve this. Yes every time I could not save the environment,
>
> You have not said which processor you use, which kind of board, which
> board you used as reference, if you are running the current U-boot
> version...you told us nothing, how can we help ?
>
> Best regards,
> Stefano Babic
>
--
Zaheer Sheriff K
--
WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.
www.easunreyrolle.com
This e-mail and any files transmitted with it are for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.
If you are not the intended recipient, please contact the sender by
reply e-mail and destroy all copies of the original message.
Any unauthorized review, use, disclosure, dissemination, forwarding,
printing or copying of this email or any action taken in reliance on
this e-mail is strictly prohibited and may be unlawful.
next prev parent reply other threads:[~2011-11-25 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 10:51 [U-Boot] How to resolve CRC issue in Uboot and maintain the env variables Zaheer Sheriff
2011-11-25 12:22 ` Stefano Babic
2011-11-25 13:42 ` Zaheer Sheriff [this message]
2011-11-25 15:05 ` Stefano Babic
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=4ECF9B45.8060409@easunreyrolle.com \
--to=zaheer.sheriff@easunreyrolle.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