Sure Anastasia, I've attached a log of a couple invocations. Let me know
if you'd rather I run it with different parameters.

I'm also wondering if the "parity violation" is relevant. I don't know
what that means but find it odd that that message is only included
sometimes but not always.
$ sudo flashrom --programmer ch341a_spi -c W25Q64.W -VV
flashrom v1.3.0 on Linux 6.1.45-hardened1 (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
flashrom was built with GCC 12.2.0, little endian
Command line (5 args): flashrom --programmer ch341a_spi -c W25Q64.W -VV
Initializing ch341a_spi programmer
Device revision is 3.0.4
The following protocols are supported: SPI.
Probing for Winbond W25Q64.W, 8192 kB: RDID byte 0 parity violation. 
compare_id: id1 0x00, id2 0x8c0
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.

$ sudo flashrom --programmer ch341a_spi -c W25Q64.W -VV
flashrom v1.3.0 on Linux 6.1.45-hardened1 (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
flashrom was built with GCC 12.2.0, little endian
Command line (5 args): flashrom --programmer ch341a_spi -c W25Q64.W -VV
Initializing ch341a_spi programmer
Device revision is 3.0.4
The following protocols are supported: SPI.
Probing for Winbond W25Q64.W, 8192 kB: compare_id: id1 0x58, id2 0x4068
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
_______________________________________________
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

Reply via email to