erase and saveenv stop working after using fw_setenv
Quoted 53 lines
Message: 1
Date: Tue, 16 Sep 2008 10:46:26 +0300
From: Petri Lehtinen <[email protected]>
Subject: [U-Boot] erase and saveenv stop working after usingfw_setenv
To: u-boot at lists.denx.de
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowedHi!
I'm using U-Boot 1.3.4 and Linux 2.6.26.5 on MPC8323E-RDB. After using
fw_printenvin Linux, erase and saveenv stop working in U-Boot. In Linux, fw_* still work.When using erase, this is the result:
=> protect off
fe040000fe05ffff
Un-Protected 1 sectors
=> erasefe040000fe05ffffFlash erase error at address
fe040000
Block Erase Error.
Block locked.
done
Erased 1 sectors
=> mdfe040000fe040000:c7be9eae626f6f74636d643d73657465 ....bootcmd=setefe040010:6e7620626f6f746172677320726f6f74nv bootargs root
...So the sector doesn't get erased.
Errors are similar when using saveenv:
=> saveenv
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
Flash erase error at addressfe040000
Block Erase Error.
Block locked.
done
Erased 1 sectorsI tracked the error message down to
cfi_flash.c, where this function call fails:
flash_isequal(info, sector, 0,FLASH_STATUS_DONE)However, I have no clue on how CFI works, so my ability to debug it further stops here. A possible reason I can think of is that the ioctl calls in
fw_setenvare somehow messing up the Flash status.
Quoted 9 lines
Any ideas?
--
Petri Lehtinen
Inoi Oy
Tel. : +358 40 758 0229
Email: petri.lehtinen at inoi.fi
Hi
I think it is the problem of hardware locking, try enabling CFG_FLASH_PROTECTION .
Signature · 5 lines
Thanks & Regards Yusuf A Khan Multitech Software Systems Koramangala,Bangalore