Hi Mahavir
I changed the settings accordingly to:
# MTD device name Device offset Env. size Flash
sector size Number of sectors
# NAND example
/dev/mtd0 0x60000 0x20000
0x20000 1
Nevertheless the Bad CRC stays with fw_printenv:
uncorrectable error : Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs
nfsroot=${serverip}:${rootpath}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
root@sheeva:~# ./fw_setenv x_bootargs_root 'root=/dev/sda1 rootwait'^M
Warning: Bad CRC, using default environment^M
root@sheeva:~# exit^
reboot again does not work and again uboot has to be reinstalled.
Regards
Norbert
Mahavir Jain wrote:
Hi Nobert
On Wed, 2010-05-12 at 04:09 -0700, Norbert Wegener wrote:
> Hi
> For some time I have the problem to which the solution is described
> here.
> Unfortunately this seems to work on a guruplug and does not work on a
> sheevaplug.
> With the binaries and config, that had been attached to the last mail, I
> tried to set variables from a running linux:
>
> root@sheeva:~# ./fw_printenv ^M
> Warning: Bad CRC, using default environment^M
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath} ip=
> ${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm^M
> bootdelay=5^M
> baudrate=115200^M
>
> Linking fw_printenv to fw_setenv and setting variables results in:
>
> Warning: Bad CRC, using default environment^M
>
> Even worse: If I reboot the sheevaplug hangs and I have to reinstall
> uboot
> via openocd.
>
> Questions is, how to set the uboot environment on a sheevaplug from a
> running system?
Try changing Device offset to 0x60000 (ENV starts here for sheevaplug)
in fw_env.config file assuming you are using open U-Boot.
Thanks
Mahavir
>
> Norbert
>