[flashrom] PMC25LV010E

The Raven originalraven at hotmail.com
Sun Jun 1 20:27:11 CEST 2014


> So far the only difference is the way we probe for the chip
> The method used for the non-A model works for both; the one used for
> the A version is only supported by itself but not by the non-A
> (visible in your logs of the "Pm25LV010E").
> Therefore your Pm25LV010 is actually a Pm25LV010A, at least if my
> theory and hence the code is correct.
Ok, and now? :-)
If the method for the non-A works for both, can we use only this?
And let's say my "Pm25LV010" is an "A". Then it seems to work with
both definitions (tested).
I attached logs. This are only from the chip "Pm25LV010" (the non "E"
version,
you think this is "A" version).
One log with -c "Pm25LV010A" and the other (same chip!) with -c "Pm25LV010".

Strange thing this PMC-Chips! :-/
-------------- next part --------------
flashrom v0.9.7-r1805 on Linux 3.11-2-amd64 (x86_64)
flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian
Command line (8 args): ./flashrom -p serprog:dev=/dev/ttyACM0:2000000 -c Pm25LV010 -Vw test.rom -o Pm25LV010-Write.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 1309M loops per second, 10 myus = 9 us, 100 myus = 112 us, 1000 myus = 1043 us, 10000 myus = 10055 us, 4 myus = 4 us, OK.
Initializing serprog programmer
Baud rate is 2000000 now.
serprog: connected - attempting to synchronize
...
serprog: Synchronized
serprog: Interface version ok.
serprog: Bus support: parallel=off, LPC=off, FWH=off, SPI=on
Warning: Automatic command availability check failed for cmd 0x08 - won't execute cmd
Warning: Automatic command availability check failed for cmd 0x11 - won't execute cmd
serprog: Programmer name is "serprog-duino"
serprog: Serial buffer size is 65535
serprog: Warning: Programmer does not support toggling its output drivers
The following protocols are supported: SPI.
Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x9d, id2 0x7c
Found PMC flash chip "Pm25LV010" (128 kB, SPI) on serprog.
Chip status register is 0x80.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set
Chip status register: Bit 6 is not set
Chip status register: Bit 5 is not set
Chip status register: Bit 4 is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
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: 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 at 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!
serprog_delay used, but programmer doesn't support delays natively - emulating
Block protection is disabled.
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:W, 0x002000-0x002fff:W, 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:Wserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W
Erase/write done.
Verifying flash... serprog_delay used, but programmer doesn't support delays natively - emulating
VERIFIED.
-------------- next part --------------
flashrom v0.9.7-r1805 on Linux 3.11-2-amd64 (x86_64)
flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian
Command line (8 args): ./flashrom -p serprog:dev=/dev/ttyACM0:2000000 -c Pm25LV010 -Vr test.rom -o Pm25LV010-Read.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 1320M loops per second, 10 myus = 9 us, 100 myus = 112 us, 1000 myus = 1014 us, 10000 myus = 10082 us, 4 myus = 12 us, OK.
Initializing serprog programmer
Baud rate is 2000000 now.
serprog: connected - attempting to synchronize
...
serprog: Synchronized
serprog: Interface version ok.
serprog: Bus support: parallel=off, LPC=off, FWH=off, SPI=on
Warning: Automatic command availability check failed for cmd 0x08 - won't execute cmd
Warning: Automatic command availability check failed for cmd 0x11 - won't execute cmd
serprog: Programmer name is "serprog-duino"
serprog: Serial buffer size is 65535
serprog: Warning: Programmer does not support toggling its output drivers
The following protocols are supported: SPI.
Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x9d, id2 0x7c
Found PMC flash chip "Pm25LV010" (128 kB, SPI) on serprog.
Chip status register is 0x80.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set
Chip status register: Bit 6 is not set
Chip status register: Bit 5 is not set
Chip status register: Bit 4 is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
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: 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 at 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!
serprog_delay used, but programmer doesn't support delays natively - emulating
Block protection is disabled.
Reading flash... done.
-------------- next part --------------
flashrom v0.9.7-r1805 on Linux 3.11-2-amd64 (x86_64)
flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian
Command line (7 args): ./flashrom -p serprog:dev=/dev/ttyACM0:2000000 -c Pm25LV010 -VE -o Pm25LV010-Erase.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 1284M loops per second, 10 myus = 10 us, 100 myus = 109 us, 1000 myus = 1002 us, 10000 myus = 9839 us, 4 myus = 4 us, OK.
Initializing serprog programmer
Baud rate is 2000000 now.
serprog: connected - attempting to synchronize
...
serprog: Synchronized
serprog: Interface version ok.
serprog: Bus support: parallel=off, LPC=off, FWH=off, SPI=on
Warning: Automatic command availability check failed for cmd 0x08 - won't execute cmd
Warning: Automatic command availability check failed for cmd 0x11 - won't execute cmd
serprog: Programmer name is "serprog-duino"
serprog: Serial buffer size is 65535
serprog: Warning: Programmer does not support toggling its output drivers
The following protocols are supported: SPI.
Probing for PMC Pm25LV010, 128 kB: probe_spi_res2: id1 0x9d, id2 0x7c
Found PMC flash chip "Pm25LV010" (128 kB, SPI) on serprog.
Chip status register is 0x80.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set
Chip status register: Bit 6 is not set
Chip status register: Bit 5 is not set
Chip status register: Bit 4 is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
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: 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 at 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!
serprog_delay used, but programmer doesn't support delays natively - emulating
Block protection is disabled.
Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x001000-0x001fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x002000-0x002fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x003000-0x003fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x004000-0x004fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x005000-0x005fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x006000-0x006fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x007000-0x007fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x008000-0x008fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x009000-0x009fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00a000-0x00afff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00b000-0x00bfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00c000-0x00cfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00d000-0x00dfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00e000-0x00efff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00f000-0x00ffff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x010000-0x010fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x011000-0x011fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x012000-0x012fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x013000-0x013fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x014000-0x014fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x015000-0x015fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x016000-0x016fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x017000-0x017fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x018000-0x018fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x019000-0x019fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01a000-0x01afff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01b000-0x01bfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01c000-0x01cfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01d000-0x01dfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01e000-0x01efff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01f000-0x01ffff:Eserprog_delay used, but programmer doesn't support delays natively - emulating

Erase/write done.
-------------- next part --------------
flashrom v0.9.7-r1805 on Linux 3.11-2-amd64 (x86_64)
flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian
Command line (8 args): ./flashrom -p serprog:dev=/dev/ttyACM0:2000000 -c Pm25LV010A -Vw test.rom -o Pm25LV010A-Write.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 1294M loops per second, 10 myus = 9 us, 100 myus = 108 us, 1000 myus = 1043 us, 10000 myus = 9910 us, 4 myus = 4 us, OK.
Initializing serprog programmer
Baud rate is 2000000 now.
serprog: connected - attempting to synchronize
...
serprog: Synchronized
serprog: Interface version ok.
serprog: Bus support: parallel=off, LPC=off, FWH=off, SPI=on
Warning: Automatic command availability check failed for cmd 0x08 - won't execute cmd
Warning: Automatic command availability check failed for cmd 0x11 - won't execute cmd
serprog: Programmer name is "serprog-duino"
serprog: Serial buffer size is 65535
serprog: Warning: Programmer does not support toggling its output drivers
The following protocols are supported: SPI.
Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x7f9d, id2 0x7c
Found PMC flash chip "Pm25LV010A" (128 kB, SPI) on serprog.
Chip status register is 0x80.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set
Chip status register: Bit 6 is not set
Chip status register: Bit 5 is not set
Chip status register: Bit 4 is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
Chip status register: Write Enable Latch (WEL) is not set
Chip status register: Write In Progress (WIP/BUSY) is not set
serprog_delay used, but programmer doesn't support delays natively - emulating
Block protection is disabled.
Reading old flash chip contents... done.
Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:W, 0x001000-0x001fff:W, 0x002000-0x002fff:W, 0x003000-0x003fff:W, 0x004000-0x004fff:W, 0x005000-0x005fff:W, 0x006000-0x006fff:W, 0x007000-0x007fff:W, 0x008000-0x008fff:W, 0x009000-0x009fff:W, 0x00a000-0x00afff:W, 0x00b000-0x00bfff:W, 0x00c000-0x00cfff:W, 0x00d000-0x00dfff:W, 0x00e000-0x00efff:W, 0x00f000-0x00ffff:W, 0x010000-0x010fff:W, 0x011000-0x011fff:W, 0x012000-0x012fff:W, 0x013000-0x013fff:W, 0x014000-0x014fff:W, 0x015000-0x015fff:W, 0x016000-0x016fff:W, 0x017000-0x017fff:W, 0x018000-0x018fff:W, 0x019000-0x019fff:W, 0x01a000-0x01afff:W, 0x01b000-0x01bfff:W, 0x01c000-0x01cfff:W, 0x01d000-0x01dfff:W, 0x01e000-0x01efff:W, 0x01f000-0x01ffff:W
Erase/write done.
Verifying flash... serprog_delay used, but programmer doesn't support delays natively - emulating
VERIFIED.
-------------- next part --------------
flashrom v0.9.7-r1805 on Linux 3.11-2-amd64 (x86_64)
flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian
Command line (8 args): ./flashrom -p serprog:dev=/dev/ttyACM0:2000000 -c Pm25LV010A -Vr test.rom -o Pm25LV010A-Read.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 1325M loops per second, 10 myus = 10 us, 100 myus = 112 us, 1000 myus = 973 us, 10000 myus = 9844 us, 4 myus = 5 us, OK.
Initializing serprog programmer
Baud rate is 2000000 now.
serprog: connected - attempting to synchronize
...
serprog: Synchronized
serprog: Interface version ok.
serprog: Bus support: parallel=off, LPC=off, FWH=off, SPI=on
Warning: Automatic command availability check failed for cmd 0x08 - won't execute cmd
Warning: Automatic command availability check failed for cmd 0x11 - won't execute cmd
serprog: Programmer name is "serprog-duino"
serprog: Serial buffer size is 65535
serprog: Warning: Programmer does not support toggling its output drivers
The following protocols are supported: SPI.
Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x7f9d, id2 0x7c
Found PMC flash chip "Pm25LV010A" (128 kB, SPI) on serprog.
Chip status register is 0x80.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set
Chip status register: Bit 6 is not set
Chip status register: Bit 5 is not set
Chip status register: Bit 4 is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
Chip status register: Write Enable Latch (WEL) is not set
Chip status register: Write In Progress (WIP/BUSY) is not set
serprog_delay used, but programmer doesn't support delays natively - emulating
Block protection is disabled.
Reading flash... done.
-------------- next part --------------
flashrom v0.9.7-r1805 on Linux 3.11-2-amd64 (x86_64)
flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian
Command line (7 args): ./flashrom -p serprog:dev=/dev/ttyACM0:2000000 -c Pm25LV010A -VE -o Pm25LV010A-Erase.txt
Calibrating delay loop... OS timer resolution is 1 usecs, 1288M loops per second, 10 myus = 9 us, 100 myus = 110 us, 1000 myus = 955 us, 10000 myus = 9733 us, 4 myus = 4 us, OK.
Initializing serprog programmer
Baud rate is 2000000 now.
serprog: connected - attempting to synchronize
...
serprog: Synchronized
serprog: Interface version ok.
serprog: Bus support: parallel=off, LPC=off, FWH=off, SPI=on
Warning: Automatic command availability check failed for cmd 0x08 - won't execute cmd
Warning: Automatic command availability check failed for cmd 0x11 - won't execute cmd
serprog: Programmer name is "serprog-duino"
serprog: Serial buffer size is 65535
serprog: Warning: Programmer does not support toggling its output drivers
The following protocols are supported: SPI.
Probing for PMC Pm25LV010A, 128 kB: probe_spi_rdid_generic: id1 0x7f9d, id2 0x7c
Found PMC flash chip "Pm25LV010A" (128 kB, SPI) on serprog.
Chip status register is 0x80.
Chip status register: Status Register Write Disable (SRWD, SRP, ...) is set
Chip status register: Bit 6 is not set
Chip status register: Bit 5 is not set
Chip status register: Bit 4 is not set
Chip status register: Block Protect 1 (BP1) is not set
Chip status register: Block Protect 0 (BP0) is not set
Chip status register: Write Enable Latch (WEL) is not set
Chip status register: Write In Progress (WIP/BUSY) is not set
serprog_delay used, but programmer doesn't support delays natively - emulating
Block protection is disabled.
Erasing and writing flash chip... Trying erase function 0... 0x000000-0x000fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x001000-0x001fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x002000-0x002fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x003000-0x003fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x004000-0x004fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x005000-0x005fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x006000-0x006fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x007000-0x007fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x008000-0x008fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x009000-0x009fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00a000-0x00afff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00b000-0x00bfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00c000-0x00cfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00d000-0x00dfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00e000-0x00efff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x00f000-0x00ffff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x010000-0x010fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x011000-0x011fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x012000-0x012fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x013000-0x013fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x014000-0x014fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x015000-0x015fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x016000-0x016fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x017000-0x017fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x018000-0x018fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x019000-0x019fff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01a000-0x01afff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01b000-0x01bfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01c000-0x01cfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01d000-0x01dfff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01e000-0x01efff:Eserprog_delay used, but programmer doesn't support delays natively - emulating
, 0x01f000-0x01ffff:Eserprog_delay used, but programmer doesn't support delays natively - emulating

Erase/write done.


More information about the flashrom mailing list