Knowledge Base Article

Why Does the Jam Player Report "Unable to Read IDCODE" or "Unrecognized Device" When Programming an Agilex® 5 or Agilex® 3 FPGA device with a JAM File Generated Using Quartus® Prime Pro Edition Software Earlier Than Version 26.1?

Description

When executing a JAM file generated for an Agilex® 5 / Agilex® 3 device, the programming process may fail with an "Unable to read IDCODE" or "Unrecognized device" error. This occurs because the device IDCODE programmed into the JAM file does not match the IDCODE reported by the target device revision.

Example errors:

Device #1 unable to read IDCODE
Unrecognized device
Exit code = 6... Unrecognized Device
Resolution

To work around this problem, use the DO_IGNORE_IDCODE_ERRORS option when executing the JAM file. This option bypasses IDCODE verification and allows the programming process to continue.

Jam Player command:

quartus_jli -c <cable> -a <action> <jam> -e DO_IGNORE_IDCODE_ERRORS
Example:
quartus_jli -c 1 -a CONFIGURE demo.jam -e DO_IGNORE_IDCODE_ERRORS
Additional Information

Note: The DO_IGNORE_IDCODE_ERRORS option is applied at runtime and does not require recompilation of the design, regeneration of the SOF file, or regeneration of the JAM file. Users can simply add the option to the existing command line when executing the JAM file.

Updated 2 months ago
Version 2.0
No CommentsBe the first to comment