Honored Contributor
Honored ContributorI've seen all sorts of error messages with flash programmer. The message you mention pops up when we have fried flash chips or other HW failures, although you mention you can read/write ok with VHDL.
I've seen FlashProgrammer fail for all sorts of things: - Payload buffer too large - smaller payload buffers work better. Change in SOPC or with arguments to mk_target_board - CPU Clock speed. Altera recommends 50, I've seen it work with 36-64 - USB port - this is our biggest problem. Some ports work, some don't. Our laptops with hubs are worst. Our desktops with direct USB are best. I work for HP so that's all I get to try, maybe other PC vendors have different USB problems. - The hidden firmware in the FlashProgrammer makes assumptions about the exact chip. We use an AMD top booting chip and the flash programmer treats it as a bottom booting chip. Luckily it still works but it may not work at all for your chip. Not all CFI chips report their configuration in the same way. Altera, please, please publish the FlashProgrammer design!! Andrew
