AT45DB011D read not working

[The Raven]

Read is not working, other things (yet) not tested.
See log for details.
It ends with a "Speicherzugriffsfehler" which means "Segmentation
fault".
I can do more tests if needed. Tell me what you need. :-)

THX

[Stefan Tauner]

On Wed, 26 Mar 2014 19:14:17 +0100
The Raven <originalraven(a)hotmail.com> wrote:

  Read is not working, other things (yet) not tested.
 See log for details.
 It ends with a "Speicherzugriffsfehler" which means "Segmentation
fault".
 I can do more tests if needed. Tell me what you need. :-)
Hi there,

that's probably my fault but I had no time to review the proposed fix
yet. Take a look at http://patchwork.coreboot.org/patch/4107/ please.

-- 
Kind regards/Mit freundlichen Grüßen, Stefan Tauner

[The Raven]

Thx,
i try it Monday and report! :-)

Am 29.03.2014 14:59, schrieb Stefan Tauner:
  On Wed, 26 Mar 2014 19:14:17 +0100
 The Raven <originalraven(a)hotmail.com> wrote:

  Read is not working, other things (yet) not
tested.
 See log for details.
 It ends with a "Speicherzugriffsfehler" which means "Segmentation
fault".
 I can do more tests if needed. Tell me what you need. :-)
 Hi there,

 that's probably my fault but I had no time to review the proposed fix
 yet. Take a look at http://patchwork.coreboot.org/patch/4107/ please.

[The Raven]

Tested and it seems to work!!! :-)
Read works, other not tested.
I don't like to test erase and write with this chip, but i search for
another
AT45DB011D to do this tests and report.
Strange that this error only happens on 011D and not on 161D.

Can you please commit this patch?

THX and greetings

[The Raven]

Ok, have made some more tests (with patched version).
Think read and write works, but erase not. Look for me like a dump or
something.
Attached logs.

Hope it helps :-)

[The Raven]

Tested with "flashrom v0.9.7-r1796".
Chip is still "UNTESTED" for all operations, but probe, read, erase and
write works.
Tested many times with random data. Always ok.

I also tested the erase functions:
Function 0 -> ok
Function 1 -> ok
Function 3 -> Not OK!

The output is:
Found Atmel flash chip "AT45DB021D" (264 kB, SPI).
This chip may contain one-time programmable memory. flashrom cannot read
and may never be able to write it, hence it may not be able to completely
clone the contents of this chip (see man page for details).
===
This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to flashrom(a)flashrom.org if any of the above
operations
work correctly for you with this flash part. Please include the flashrom
output with the additional -V option for all operations you tested (-V, -Vr,
-VE, -Vw), and mention which mainboard or programmer you tested.
Please mention your board in the subject line. Thanks for your help!
Erasing and writing flash chip... Trying erase function 0...
0x000000-0x00083f:E, 0x000840-0x0083ff:E, 0x008400-0x0107ff:EError:
invalid response 0x11 from device
at45db_erase: error sending erase command!
Reading current flash chip contents... Error: invalid response 0xE9 from
device
spi_read_at45db: error sending read command!
Can't read anymore! Aborting.
FAILED!
Your flash chip is in an unknown state.
Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail flashrom(a)flashrom.org, thanks!

But writing with this mode works!
Output:
Found Atmel flash chip "AT45DB021D" (264 kB, SPI).
This chip may contain one-time programmable memory. flashrom cannot read
and may never be able to write it, hence it may not be able to completely
clone the contents of this chip (see man page for details).
===
This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
The test status of this chip may have been updated in the latest development
version of flashrom. If you are running the latest development version,
please email a report to flashrom(a)flashrom.org if any of the above
operations
work correctly for you with this flash part. Please include the flashrom
output with the additional -V option for all operations you tested (-V, -Vr,
-VE, -Vw), and mention which mainboard or programmer you tested.
Please mention your board in the subject line. Thanks for your help!
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0...
0x000000-0x00083f:W, 0x000840-0x0083ff:W, 0x008400-0x0107ff:S,
0x010800-0x018bff:S, 0x018c00-0x020fff:S, 0x021000-0x0293ff:S,
0x029400-0x0317ff:S, 0x031800-0x039bff:S, 0x039c00-0x041fff:S
Erase/write done.
Verifying flash... VERIFIED.

Hope it helps!

Greetings

[Stefan Tauner]

On Tue, 20 May 2014 18:15:40 +0200
The Raven <originalraven(a)hotmail.com> wrote:

Hi,
thanks for your report!

  Tested with "flashrom v0.9.7-r1796".
 Chip is still "UNTESTED" for all operations, but probe, read, erase and
 write works.
 Tested many times with random data. Always ok.
 
 I also tested the erase functions:
 Function 0 -> ok
 Function 1 -> ok
 Function 3 -> Not OK!
 
 The output is:
 Found Atmel flash chip "AT45DB021D" (264 kB, SPI).
 This chip may contain one-time programmable memory. flashrom cannot read
 and may never be able to write it, hence it may not be able to completely
 clone the contents of this chip (see man page for details).
 ===
 This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
 The test status of this chip may have been updated in the latest development
 version of flashrom. If you are running the latest development version,
 please email a report to flashrom(a)flashrom.org if any of the above
 operations
 work correctly for you with this flash part. Please include the flashrom
 output with the additional -V option for all operations you tested (-V, -Vr,
 -VE, -Vw), and mention which mainboard or programmer you tested.
 Please mention your board in the subject line. Thanks for your help!
 Erasing and writing flash chip... Trying erase function 0...
 0x000000-0x00083f:E, 0x000840-0x0083ff:E, 0x008400-0x0107ff:EError:
 invalid response 0x11 from device
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That's a serprog error, and probably stems from a bug in the arduino
implementation... i guess.

  at45db_erase: error sending erase command!
 Reading current flash chip contents... Error: invalid response 0xE9 from
 device
 spi_read_at45db: error sending read command!
 Can't read anymore! Aborting.
 FAILED!
 Your flash chip is in an unknown state.
 Please report this on IRC at chat.freenode.net (channel #flashrom) or
 mail flashrom(a)flashrom.org, thanks!
 
 But writing with this mode works!
 Output:
 Found Atmel flash chip "AT45DB021D" (264 kB, SPI).
 This chip may contain one-time programmable memory. flashrom cannot read
 and may never be able to write it, hence it may not be able to completely
 clone the contents of this chip (see man page for details).
 ===
 This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE
 The test status of this chip may have been updated in the latest development
 version of flashrom. If you are running the latest development version,
 please email a report to flashrom(a)flashrom.org if any of the above
 operations
 work correctly for you with this flash part. Please include the flashrom
 output with the additional -V option for all operations you tested (-V, -Vr,
 -VE, -Vw), and mention which mainboard or programmer you tested.
 Please mention your board in the subject line. Thanks for your help!
 Reading old flash chip contents... done.
 Erasing and writing flash chip... Trying erase function 0...
 0x000000-0x00083f:W, 0x000840-0x0083ff:W, 0x008400-0x0107ff:S,
 0x010800-0x018bff:S, 0x018c00-0x020fff:S, 0x021000-0x0293ff:S,
 0x029400-0x0317ff:S, 0x031800-0x039bff:S, 0x039c00-0x041fff:S
 Erase/write done.
 Verifying flash... VERIFIED.
Actually... your data in this log does not require an erase cycle,
that's why it *looks* like working... because it just writes (but does
not erase).

I have checked the eraser definitions of the chip and they look fine. 
Therefore I have marked the flash chip as fully tested and will commit
that later together with other small changes.

-- 
Kind regards/Mit freundlichen Grüßen, Stefan Tauner

[The Raven]

Ha found again two "AT45DB011D" chips on a system board.
You can found many many "AT45DB011B" chips, but the "D" is very rare!
To bad that the "B" has no probe function and can not be supported by
flashrom.

Anyway, here are the results for the "D" with latest flashrom:

Probe: OK
Read: OK
Erase: OK
Write: OK

So i think this chip can be marked as supported.

I have attached the logs.

If you need more testing or logs -> Tell me what you need.

THX and Greetings

[Stefan Tauner]

On Sat, 16 Aug 2014 08:52:26 +0200
The Raven <originalraven(a)hotmail.com> wrote:

  Ha found again two "AT45DB011D" chips on a
system board.
 You can found many many "AT45DB011B" chips, but the "D" is very
rare!
 To bad that the "B" has no probe function and can not be supported by
 flashrom.
 
 Anyway, here are the results for the "D" with latest flashrom:
 
 Probe: OK
 Read: OK
 Erase: OK
 Write: OK
 
 So i think this chip can be marked as supported.
 
 I have attached the logs.
 
 If you need more testing or logs -> Tell me what you need.
 
 THX and Greetings

Hello,

thanks for your report!
I have marked the flash chip as fully tested and will commit that later
together with other small changes.
The chips without ID opcodes might be supported in the future so please
dont throw all of them away ;)

-- 
Kind regards/Mit freundlichen Grüßen, Stefan Tauner

[The Raven]

  Hello,

 thanks for your report!
 I have marked the flash chip as fully tested and will commit that later
 together with other small changes.
 The chips without ID opcodes might be supported in the future so please
 dont throw all of them away ;)
Sounds good! :-)
Some of them (the AT45DB011B for example) can be found very very often.
So it would be nice if we can force reading and programming with -f
option (without guarantee of course).
I keep it and if something changes let me know. ;-)

BTW: I have an AT45DB161E here which has the same device ID like the "D"
(id1 0x1f, id2 0x2600).

THX