Forum Discussion
Can not program Agilex-5 device
Quartus programmer stops at 44% with error:
Error(18950): Device has stopped receiving configuration data
Error(18948): Error message received from device: Bitstream error. (Subcode 0x0093, Info 0x00000003, Location 0x00000800)
Error(18948): Error message received from device: Device specification (SKU ID) of the target device used in bitstream generation does not match physical device.
Error(23925): Debug suggestion: Verify that the device OPN selected in Quartus Prime matches exactly with the OPN of your hardware device.
Error(209012): Operation failed
What can be the cause, the device is selected correctly.
Problem solved I had to use special "CS" OPN. Then it all worked.
4 Replies
- AnttiLukats
Occasional Contributor
we tried flashing with wrong SOF, when we select proper device then SOF is not generated at all, with following:
Critical Warning(18636): Compilation Report contains advance information. Specifications for device A5EE013BB23BE6S are subject to change. Contact Altera for information on availability. No programming file will be generated.
Dear Altera what should we do?
- FakhrulA_altera
Regular Contributor
Hi AnttiLukats,
The errors you see match a known case where the timing models for this device are not yet final. Hence SOF generation also is not enabled yet..
Please review:
KDB: Why can’t the Agilex 5/7 programming file be generated?
https://community.altera.com/kb/knowledge-base/why-cant-the-agilex%E2%84%A2-5-or-agilex%E2%84%A2-7-fpga-programming-file-be-generated-in-the-qu/345059
Community thread showing the workaround via quartus.ini and correct OPN selection:
https://community.altera.com/discussions/quartus-prime/quartus-25-1-0-not-producing-sof-file/311247
Next steps:- In Quartus, select the exact Ordering Part Number printed on your device and recompile.
- Update to the latest Quartus Prime Pro with the Agilex 5 device pack.
- If Warning 18636 still blocks .sof, I will request the temporary INI from software team, then recompile and program.
Regards,
Fakhrul- AnttiLukats
Occasional Contributor
Problem solved I had to use special "CS" OPN. Then it all worked.