On Sat, 1 Mar 2014 23:12:15 +0400 Alex K lepik.stv@gmail.com wrote:
Hello I tested for cleaning work, reading, writing, memory AT25DF161 using Bus Pirate v4. Used: flashrom v0.9.6.1-r1704 on Windows 6.1 (x86) flashrom was built with GCC 4.7.2, little endian Baud rate is 115200. Detected Bus Pirate hardware v4 Detected Bus Pirate firmware 6.2 ("v6.2-beta1") Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4602 Found Atmel flash chip "AT25DF161" (2048 kB, SPI) on buspirate_spi. Ignoring security lockdown (if present) Ignoring status register byte 2 Chip status register is 0x0c. Chip status register: Sector Protection Register Lock (SRPL) is not set Chip status register: Bit 6 is not set Chip status register: Erase/Program Error (EPE) is not set Chip status register: WP# pin (WPP) is asserted Chip status register: Software Protection Status (SWP): all sectors are protected Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set ===
Initially, there was a problem with the use of long cables (> 20 cm). After verification of the firmware did not pass. Replaced wires from Bus Pirate at length (10cm), all turned out. Many thanks for the utility. I think that you can remove the status UNTESTED with this chip. Thank you again. I think it is reasonable to point out the page on the wiki that the length of wire for the Bus Pirate is very desirable <= 10 cm, to avoid many mistakes. This saves the trouble of starting recording, reading chips.
Sorry for my bad english, I'm from Russia.
Hello Alex,
thanks for your report! I am wondering a bit about the status register bits. According to your log the software write protection is enabled (and the parsing of the raw value 0x0c seems to be correct, so this is not only a cosmetic problem). Did you change anything since you wrote to the chip?
Regarding the cable lengths: The troubleshooting section of the bus pirate wiki page links to this: http://flashrom.org/ISP and the first problem mentioned there are too long cables ;)
Sorry, I do not quite understand your question, but I'll try to answer. I forgot when recording chip, specify a log file entry. Because I have a log file cleanup, and reading to compare the recorded information. To clean the chip pin WP, I connect to the GND. For writing and reading from the chip, pin WP connects to the VCC.
Here is the log when cleaning: ====================== flashrom v0.9.6.1-r1704 on Windows 6.1 (x86) flashrom was built with GCC 4.7.2, little endian Command line (7 args): flashrom.exe -p buspirate_spi:dev=COM12 -VE -c AT25DF161 -o write_e.txt Calibrating delay loop... OS timer resolution is 1000 usecs, 2185M loops per second, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 1000 us, 10000 myus = 10001 us, 4000 myus = 4000 us, OK. Initializing buspirate_spi programmer Baud rate is 115200. Detected Bus Pirate hardware v4 Detected Bus Pirate firmware 6.2 ("v6.2-beta1") Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4602 Found Atmel flash chip "AT25DF161" (2048 kB, SPI) on buspirate_spi. Ignoring security lockdown (if present) Ignoring status register byte 2 Chip status register is 0x0c. Chip status register: Sector Protection Register Lock (SRPL) is not set Chip status register: Bit 6 is not set Chip status register: Erase/Program Error (EPE) is not set Chip status register: WP# pin (WPP) is asserted Chip status register: Software Protection Status (SWP): all sectors are protected Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set === This flash part has status UNTESTED for operations: 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@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! Ignoring security lockdown (if present) Some block protection in effect, disabling... disabled. Erase/write done. Raw bitbang mode version 1 Bus Pirate shutdown completed.
Here is the log when reading for comparison: ================================ flashrom v0.9.6.1-r1704 on Windows 6.1 (x86) flashrom was built with GCC 4.7.2, little endian Command line (8 args): flashrom.exe -p buspirate_spi:dev=COM12 -Vr read_CAM-4020.bin -c AT25DF161 -o read_vr.txt Calibrating delay loop... OS timer resolution is 1000 usecs, 2158M loops per second, 10 myus = 0 us, 100 myus = 0 us, 1000 myus = 1000 us, 10000 myus = 11001 us, 4000 myus = 4000 us, OK. Initializing buspirate_spi programmer Baud rate is 115200. Detected Bus Pirate hardware v4 Detected Bus Pirate firmware 6.2 ("v6.2-beta1") Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f, id2 0x4602 Found Atmel flash chip "AT25DF161" (2048 kB, SPI) on buspirate_spi. Ignoring security lockdown (if present) Ignoring status register byte 2 Chip status register is 0x1c. Chip status register: Sector Protection Register Lock (SRPL) is not set Chip status register: Bit 6 is not set Chip status register: Erase/Program Error (EPE) is not set Chip status register: WP# pin (WPP) is not asserted Chip status register: Software Protection Status (SWP): all sectors are protected Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set === This flash part has status UNTESTED for operations: 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@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! Ignoring security lockdown (if present) Some block protection in effect, disabling... disabled. Reading flash... done. Raw bitbang mode version 1 Bus Pirate shutdown completed. ========================
I hope this information will help you.
2014-03-01 23:48 GMT+04:00 Stefan Tauner <stefan.tauner@student.tuwien.ac.at
:
On Sat, 1 Mar 2014 23:12:15 +0400 Alex K lepik.stv@gmail.com wrote:
Hello I tested for cleaning work, reading, writing, memory AT25DF161
using
Bus Pirate v4. Used: flashrom v0.9.6.1-r1704 on Windows 6.1 (x86) flashrom was built with GCC 4.7.2, little endian Baud rate is 115200. Detected Bus Pirate hardware v4 Detected Bus Pirate firmware 6.2 ("v6.2-beta1") Using SPI command set v2. SPI speed is 8MHz Raw bitbang mode version 1 Raw SPI mode version 1 The following protocols are supported: SPI. Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x1f,
id2
0x4602 Found Atmel flash chip "AT25DF161" (2048 kB, SPI) on buspirate_spi. Ignoring security lockdown (if present) Ignoring status register byte 2 Chip status register is 0x0c. Chip status register: Sector Protection Register Lock (SRPL) is not set Chip status register: Bit 6 is not set Chip status register: Erase/Program Error (EPE) is not set Chip status register: WP# pin (WPP) is asserted Chip status register: Software Protection Status (SWP): all sectors are protected Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set ===
Initially, there was a problem with the use of long cables (> 20 cm). After verification of the firmware did not pass. Replaced wires from Bus Pirate at length (10cm), all turned out. Many thanks for the utility. I think that you can remove the status UNTESTED with this chip. Thank you again. I think it is reasonable to point out the page on the wiki that the
length
of wire for the Bus Pirate is very desirable <= 10 cm, to avoid many mistakes. This saves the trouble of starting recording, reading chips.
Sorry for my bad english, I'm from Russia.
Hello Alex,
thanks for your report! I am wondering a bit about the status register bits. According to your log the software write protection is enabled (and the parsing of the raw value 0x0c seems to be correct, so this is not only a cosmetic problem). Did you change anything since you wrote to the chip?
Regarding the cable lengths: The troubleshooting section of the bus pirate wiki page links to this: http://flashrom.org/ISP and the first problem mentioned there are too long cables ;)
-- Kind regards/Mit freundlichen Grüßen, Stefan Tauner