Re: [flashrom] "S25FL128S......0" on usbblaster_spi

[Stefan Tauner]

On Fri, 30 May 2014 22:00:59 -0400
Liviu Toma  wrote:
> Hello,
>
> I had some success programming the Spansion "S25FL128S......0" with
> usbblaster_spi (Altera USB blaster cheap clone).
> The read function works OK. The write function fails the first time but if
> I run it again it works the second time (this is consistent, I've done it
> on 3 different chips). It appears the first time it does Erase then Write,
> but only the erasing works. The second time it's already erased from the
> first run and the write works OK.
> Log attached.

Hi Liviu,

each erased block is verified to contain 0xFF before it is tried to be
written. So the erase is successful when the W is printed. Now there
are two possibilities: either the writes did not work, or after a write
another delete undoes the write later. Can you please tell me the exact
S25FL128S model you have? There are many versions of the chip (as the
dots in the name suggests) and I presume that the problem is that the
current implementation is not compatible with all models.

"S25FL128S......0" on usbblaster_spi

[Liviu Toma]

Hi,

Thanks very much for the reply. Just to clarify, I am not concerned, I was
able to flash the chip. I was merely sending the info as instructed by the
tool.
The inscription on the chip read Spansion FL128PIF (the next line reads
92599012 but I assume that's some date / serial number).

Thanks,
Liviu

On Sat, May 31, 2014 at 11:35 AM, Stefan Tauner <
[e-mail]> wrote:
> On Fri, 30 May 2014 22:00:59 -0400
> Liviu Toma  wrote:
> > Hello,
> >
> > I had some success programming the Spansion "S25FL128S......0" with
> > usbblaster_spi (Altera USB blaster cheap clone).
> > The read function works OK. The write function fails the first time but
>
> if
> > I run it again it works the second time (this is consistent, I've done it
> > on 3 different chips). It appears the first time it does Erase then
>
> Write,
> > but only the erasing works. The second time it's already erased from the
> > first run and the write works OK.
> > Log attached.
>
> Hi Liviu,
>
> each erased block is verified to contain 0xFF before it is tried to be
> written. So the erase is successful when the W is printed. Now there
> are two possibilities: either the writes did not work, or after a write
> another delete undoes the write later. Can you please tell me the exact
> S25FL128S model you have? There are many versions of the chip (as the
> dots in the name suggests) and I presume that the problem is that the
> current implementation is not compatible with all models.