Здравствуйте, Flashrom.
I try read chip cFeon EN25P64 - 16 pins, through adapter SPI 16 to 8 but flashrom show two INVALID variants:
#flashrom -p ft2232_spi:type=arm-usb-tiny-h
flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Eon flash chip "EN25B64" (8192 kB, SPI) on ft2232_spi. Found Eon flash chip "EN25B64T" (8192 kB, SPI) on ft2232_spi. Multiple flash chip definitions match the detected chip(s): "EN25B64", "EN25B64T" Please specify which chip definition to use with the -c <chipname> option.
read normally:
date flashrom -p ft2232_spi:type=arm-usb-tiny-h -c EN25B64 -r 234 date
1 min 5 sec
write okey:
flashrom -p ft2232_spi:type=arm-usb-tiny-h -c EN25B64 -w 3883 flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Eon flash chip "EN25B64" (8192 kB, SPI) on ft2232_spi. === 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@flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.
my OS is debian 32bit, programmer ARM-USB-TINY-H
i have tested other my chips - all ok:
:~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h -c "MX25L3205(A)" -r MX25L3205 flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Macronix flash chip "MX25L3205(A)" (4096 kB, SPI) on ft2232_spi. Reading flash... done. :~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Micron/Numonyx/ST flash chip "M25P64" (8192 kB, SPI) on ft2232_spi. No operations were specified. :~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h -r M25P64 flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Micron/Numonyx/ST flash chip "M25P64" (8192 kB, SPI) on ft2232_spi. Reading flash... done. :~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h -r 25X32VF flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Winbond flash chip "W25X32" (4096 kB, SPI) on ft2232_spi. Reading flash... done. :~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h -r W25Q32BV flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Winbond flash chip "W25Q32.V" (4096 kB, SPI) on ft2232_spi. Reading flash... done. :~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h -r FL032 flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Spansion flash chip "S25FL032A/P" (4096 kB, SPI) on ft2232_spi. Reading flash... done. :~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h -r W25Q64BV flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ft2232_spi. Reading flash... done. :~/spi# flashrom -p ft2232_spi:type=arm-usb-tiny-h -r W25Q64FV flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ft2232_spi. Reading flash... done.
On Mon, 5 Jan 2015 07:36:42 +0500 novoagansk@gmail.com wrote:
Здравствуйте, Flashrom.
I try read chip cFeon EN25P64 - 16 pins, through adapter SPI 16 to 8 but flashrom show two INVALID variants:
#flashrom -p ft2232_spi:type=arm-usb-tiny-h
flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Eon flash chip "EN25B64" (8192 kB, SPI) on ft2232_spi. Found Eon flash chip "EN25B64T" (8192 kB, SPI) on ft2232_spi. Multiple flash chip definitions match the detected chip(s): "EN25B64", "EN25B64T" Please specify which chip definition to use with the -c <chipname> option.
read normally:
date flashrom -p ft2232_spi:type=arm-usb-tiny-h -c EN25B64 -r 234 date
1 min 5 sec
write okey:
flashrom -p ft2232_spi:type=arm-usb-tiny-h -c EN25B64 -w 3883 flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Eon flash chip "EN25B64" (8192 kB, SPI) on ft2232_spi. === 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@flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.
Здравствуйте! :)
Thank you for your report. The reason why you see the "EN25B64" and "EN25B64T" variants be detect is that they have the same RDID as the EN25P64, which is not uncommon. However if I interpret your email correctly, then you have written your EN25P64 successfully and without warnings or error messages by using the flash chip definition of EN25B64. This is confusing for me because it should actually not work. The EN25P64 and EN25B64 have very different block layouts. The P variant has a unified sector size of 64kB while the B variants have "Two 4-Kbyte, one 8-Kbyte, one 16-Kbyte, one 32-Kbyte, and one hundred twenty-seven 64-Kbyte sectors".
Did I miss something?
Здравствуйте, Stefan.
Вы писали 6 января 2015 г., 4:32:44:
Hi, Stefan!!
Sorry, i tested write twice and i tested also full erased chip cFeon EN25P64
all ok with it with "EN25B64" variant.
about size ot sector i may say nothing.
If you want - send me flashrom debug variant and i run it and i send report to you.
What you say?
P.S.
If you want - i may use rayer_spi or arm-usb-tiny-h devices.
----------
Sorry, Stefan, i can inadequate question to you?
I need read unique ID info and OTP zones from W25Q64BV, W25Q64CV and W25Q64FV chips. also, MX25L6405
Please, maybe is it patch or OTP_version of flashrom to read it datas?
On Mon, 5 Jan 2015 07:36:42 +0500 novoagansk@gmail.com wrote:
Здравствуйте, Flashrom.
I try read chip cFeon EN25P64 - 16 pins, through adapter SPI 16 to 8 but flashrom show two INVALID variants:
#flashrom -p ft2232_spi:type=arm-usb-tiny-h
flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Eon flash chip "EN25B64" (8192 kB, SPI) on ft2232_spi. Found Eon flash chip "EN25B64T" (8192 kB, SPI) on ft2232_spi. Multiple flash chip definitions match the detected chip(s): "EN25B64", "EN25B64T" Please specify which chip definition to use with the -c <chipname> option.
read normally:
date flashrom -p ft2232_spi:type=arm-usb-tiny-h -c EN25B64 -r 234 date
1 min 5 sec
write okey:
flashrom -p ft2232_spi:type=arm-usb-tiny-h -c EN25B64 -w 3883 flashrom v0.9.7-r1852 on Linux 3.2.66 (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Eon flash chip "EN25B64" (8192 kB, SPI) on ft2232_spi. === 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@flashrom.org if any of the above operations work correctly for you with this flash chip. Please include the flashrom log file for all operations you tested (see the man page for details), and mention which mainboard or programmer you tested in the subject line. Thanks for your help! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED.
Здравствуйте! :)
Thank you for your report. The reason why you see the "EN25B64" and "EN25B64T" variants be detect is that they have the same RDID as the EN25P64, which is not uncommon. However if I interpret your email correctly, then you have written your EN25P64 successfully and without warnings or error messages by using the flash chip definition of EN25B64. This is confusing for me because it should actually not work. The EN25P64 and EN25B64 have very different block layouts. The P variant has a unified sector size of 64kB while the B variants have "Two 4-Kbyte, one 8-Kbyte, one 16-Kbyte, one 32-Kbyte, and one hundred twenty-seven 64-Kbyte sectors".
Did I miss something?
On Tue, 6 Jan 2015 05:30:11 +0500 novoagansk@gmail.com wrote:
Sorry, Stefan, i can inadequate question to you?
I need read unique ID info and OTP zones from W25Q64BV, W25Q64CV and W25Q64FV chips. also, MX25L6405
Please, maybe is it patch or OTP_version of flashrom to read it datas?
No, current there is no OTP support in flashrom and no patch available. It would not be too hard to add it though... I just had no time yet. SPIPGM (the original DOS program for the rayer programmer) apparently got support for reading the unique IDs of winbond chips lately. Maybe that is enough for your purposes. You can find it here: http://rayer.g6.cz/programm/programe.htm
I was wondering for a long time when/if the OTP zones would be used. Did you encounter them "in the wild" in some product?
Здравствуйте, Stefan.
Вы писали 6 января 2015 г., 15:26:56:
Thank you for exhaustive answer. I find rayer..
OTP used in Ubiquiti wifi devices, ethernet cameras.. ID use for Mikrotik serial number for geniuine..
On Tue, 6 Jan 2015 05:30:11 +0500 novoagansk@gmail.com wrote:
Sorry, Stefan, i can inadequate question to you?
I need read unique ID info and OTP zones from W25Q64BV, W25Q64CV and W25Q64FV chips. also, MX25L6405
Please, maybe is it patch or OTP_version of flashrom to read it datas?
No, current there is no OTP support in flashrom and no patch available. It would not be too hard to add it though... I just had no time yet. SPIPGM (the original DOS program for the rayer programmer) apparently got support for reading the unique IDs of winbond chips lately. Maybe that is enough for your purposes. You can find it here: http://rayer.g6.cz/programm/programe.htm
I was wondering for a long time when/if the OTP zones would be used. Did you encounter them "in the wild" in some product?
On Tue, 6 Jan 2015 05:30:11 +0500 novoagansk@gmail.com wrote:
Здравствуйте, Stefan.
Вы писали 6 января 2015 г., 4:32:44:
Hi, Stefan!!
Sorry, i tested write twice and i tested also full erased chip cFeon EN25P64
all ok with it with "EN25B64" variant.
about size ot sector i may say nothing.
If you want - send me flashrom debug variant and i run it and i send report to you.
What you say?
You can use the -V option (multiple times) to increase the verbosity of flashrom. You can also create log files with the -o option. I would like to see the log file created by flashrom -p ft2232_spi:type=arm-usb-tiny-h -VVV -o EN25P64_probe_spew.log The programmer does not really matter... they should behave the same regarding this chip.
Why do you know that this is a EN25P64 and not a EN25B64? Maybe you misinterpreted the letter on the package? I will add support for the P variants to flashrom anyway, but this requires that I understand what is going on in your case.
-
novoagansk＠gmail.com -
Stefan Tauner