From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tolunay Orkun Date: Wed, 02 May 2007 18:10:19 -0500 Subject: [U-Boot-Users] Flash Erase/Write error in uboot In-Reply-To: <1178123087.27349.7.camel@localhost> References: <20070502002918.CB4EF353AF1@atlas.denx.de> <1178123087.27349.7.camel@localhost> Message-ID: <46391A5B.1090403@orkun.us> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Shiju Mathew wrote: > On Wed, 2007-02-05 at 02:29 +0200, Wolfgang Denk wrote: > >> In message you wrote: >> >>> I have a board with flash part S71WS256N. I was using CFI driver and >>> didn't had any problems programming the device. But from today I am >>> getting an unusual error while writing to flash sectors. It always gives >>> erase successful. But when I try to write data after erase, I get a >>> message that the flash is not erased. I use uboot-1.2. Below is the >>> debug message on running saveenv. Could someone help me to resolve this >>> problem. >>> >> Is it correct to assume that this is just on one board? Seems your >> flash died. This happens. >> >> > The flash is not dead. I could flash uboot using RVI debugger without > any problem. Basically I load two uboot images onto RAM using RVI- one > to run from RAM and writes the second image to flash. This is always > succussfull. ONce the uboot is written to flash, and reboot the board, I > get the error that the "flash is not errased". > Today I tested with the top-of-git version. Still have the same problem. > Anyone have experienced this problem before. > > Thanks, > Shiju > Does this happen with DEBUG enabled? Did you check with DEBUG disabled? I noticed that DEBUG distrupts some of the registers used for status checking... If you have to have DEBUG enabled for testing something else please put #undef DEBUG towards the beginning of cfi_flash.c (after #include etc) Tolunay Tolunay