From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Flash Erase/Write error in uboot
Date: Wed, 02 May 2007 18:10:19 -0500 [thread overview]
Message-ID: <46391A5B.1090403@orkun.us> (raw)
In-Reply-To: <1178123087.27349.7.camel@localhost>
Shiju Mathew wrote:
> On Wed, 2007-02-05 at 02:29 +0200, Wolfgang Denk wrote:
>
>> In message <f3cea0230705011722q2a88618bg371fdd67eeed18c8@mail.gmail.com> 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
next prev parent reply other threads:[~2007-05-02 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 0:22 [U-Boot-Users] Flash Erase/Write error in uboot Shiju Mathew
2007-05-02 0:29 ` Wolfgang Denk
2007-05-02 16:24 ` Shiju Mathew
2007-05-02 23:10 ` Tolunay Orkun [this message]
2007-05-03 18:40 ` Shiju Mathew
2007-05-03 21:31 ` Tolunay Orkun
2007-05-05 2:46 ` Shiju Mathew
2007-05-05 5:18 ` Stefan Roese
2007-05-05 5:26 ` Tolunay Orkun
[not found] ` <c166aa9f0705050648p16b150c2sfb123108f7b0bce6@mail.gmail.com>
2007-05-08 18:36 ` Shiju Mathew
2007-05-08 18:59 ` Wolfgang Denk
2007-05-02 5:01 ` Stefan Roese
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=46391A5B.1090403@orkun.us \
--to=listmember@orkun.us \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.