On Mon, 22 Apr 2013 13:24:44 -0700 Skip WB6YMH wb6ymh@gfrn.org wrote:
I'd like to let you know that I successfully programmed the above chip using a ft2232 based "TUMPA" interface card. I've programmed two chips on two separate boards, but worked fine and booted Linux.
I did get one "get_buf failed: 1 ftdi_write_data: -19, usb bulk write failed send_buf failed at end: 1 FAILED."
Error, but that probably has nothing to do with the MX25L12805(D) chip.
Thanks for the code !
Skip
Hello Skip,
thanks for your report! I have marked the flash chip as fully tested and will commit that later together with other small changes.
Please include the complete log in future reports (and an additional one with verbose output (-V) if the normal run did not include that). That's especially interesting for error cases such as the one you mentioned. Do you remember when the error occurred exactly?
Sorry, I didn't create a log. If I didn't have to solder wires to my flash chip I'd try to recreate it for you. My soldering "skills" aren't !
The best I can do is the following which was still on my screen. Run under Ubuntu 10.04 on a Dell Optiplex 745 with a Intel Pentium D CPU 3.40GHz.
Code was pulled from svn on 4/16 (rev 1669).
Skip
--- skip@lucid:~/flashrom/new$ sudo ../flashrom -p ft2232_spi:type=tumpa,port=B -w new.bin flashrom v0.9.6.1-r1669 on Linux 2.6.32-37-generic-pae (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Macronix flash chip "MX25L12805(D)" (16384 kB, SPI) on ft2232_spi. === 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! Reading old flash chip contents... ftdi_read_data: -19, usb bulk read failed get_buf failed: 1 ftdi_write_data: -19, usb bulk write failed send_buf failed at end: 1 FAILED. skip@lucid:~/flashrom/new$ sudo ../flashrom -p ft2232_spi:type=tumpa,port=B -w new.bin flashrom v0.9.6.1-r1669 on Linux 2.6.32-37-generic-pae (i686) flashrom is free software, get the source code at http://www.flashrom.org
Calibrating delay loop... OK. Found Macronix flash chip "MX25L12805(D)" (16384 kB, SPI) on ft2232_spi. === 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! Reading old flash chip contents... done. Erasing and writing flash chip... Erase/write done. Verifying flash... VERIFIED. skip@lucid:~/flashrom/new$ ---
On Mon, Apr 22, 2013 at 2:37 PM, Stefan Tauner < stefan.tauner@student.tuwien.ac.at> wrote:
On Mon, 22 Apr 2013 13:24:44 -0700 Skip WB6YMH wb6ymh@gfrn.org wrote:
I'd like to let you know that I successfully programmed the above chip using a ft2232 based "TUMPA" interface card. I've programmed two chips on two separate boards, but worked fine and booted Linux.
I did get one "get_buf failed: 1 ftdi_write_data: -19, usb bulk write failed send_buf failed at end: 1 FAILED."
Error, but that probably has nothing to do with the MX25L12805(D) chip.
Thanks for the code !
Skip
Hello Skip,
thanks for your report! I have marked the flash chip as fully tested and will commit that later together with other small changes.
Please include the complete log in future reports (and an additional one with verbose output (-V) if the normal run did not include that). That's especially interesting for error cases such as the one you mentioned. Do you remember when the error occurred exactly? -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner