Yes. Nothing changes. I slowed it down in an attempt to get probing to work.
I’ve upgraded the pirate to v7.11 firmware, and that got rid of the need to reset it every time, but it still doesn’t work.
I’ve attempted to add support for the chip into flashchips.c - to at least get it to recognize the 0x7017 ID, but that doesn’t work either.
%./flashrom --programmer buspirate_spi:dev=/dev/tty.usbmodem000000011,spispeed=1M -c W25Q64.V..M -V -V -V […] The following protocols are supported: SPI. Probing for Winbond W25Q64.V..M, 8192 kB: programmer_map_flash_region: mapping W25Q64.V..M from 0x00000000ff800000 to 0x0000000000000000 buspirate_sendrecv: write 6, read 4 Sending 0x04 0x00 0x01 0x00 0x03 0x9f, receiving 0x01 0x00 0x00 0x00 RDID returned 0x00 0x00 0x00. RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0x00, id2 0x00 programmer_unmap_flash_region: unmapped 0x0000000000000000 No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.
It’s as if flashrom isn’t talking to the chip properly at all. I do see it lighting up “mode” and “pwr” LEDs briefly while trying to probe, but it just doesn’t work.
But standalone, it works fine:
SPI>[ 0x9f r r r ] /CS ENABLED WRITE: 0x9F READ: 0xEF READ: 0x70 READ: 0x17 /CS DISABLED
On Aug 7, 2019, at 7:04 PM, awokd via flashrom flashrom@flashrom.org wrote:
Nick Sayer via flashrom:
% flashrom --programmer buspirate_spi:dev=/dev/tty.usbmodem000000011,spispeed=30k
That spispeed looks unusual. Have you tried spispeed=1M? _______________________________________________ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-leave@flashrom.org