Ben Larson

I'm sorry about my impoliteness earlier. What you said reminded me of my experience reporting issues with Docker, where there were issues that the very opinionated devs refused to do anything about. That and other bad experiences also made me hesitant to reach out. I intend to submit a couple patches soon, one to support Zetta NOR flash devices, and one for adding helpful information to the error message.

With -d3, I get the following, surrounded by information: Error: 499 8935 rp2040.c:455 rp2040_flash_probe(): Unknown flash device (ID 0x001560ba) Error: 500 8935 core.c:316 get_flash_bank_by_addr(): auto_probe failed Debug: 501 8935 command.c:544 run_command(): Command 'flash mdw' failed with error code -4 First thing to note is that it does not point to spi.c, nor does it suggest anything about the user adding code to support the flash device. It is very common that errors are not indicative of...

Yeah, I'm aware of the list, and I added the following line to mine (src/flash/nor/spi.c): FLASH_ID("zetta zd25q16b", 0x03, 0x00, 0x02, 0xd8, 0xc7, 0x001560ba, 0x100, 0x10000, 0x200000), For a long-term solution, I wasn't thinking of making OpenOCD silent when it couldn't identify the flash chip. That would be obnoxious. But OpenOCD should at least emit a warning, e.g. Attempting to write to flash using generic method, and try using the generic method to write to the flash memory, as long as it successfully...

No support for generic SPI flash