Why is my JTAG user code changed to 0xFFFFFFFF in the SRAM Object File (.sof), Programmer Object File (.pof), and report files? - Why is my JTAG user code changed to 0xFFFFFFFF in the SRAM Object File (.sof), Programmer Object File (.pof), and report files? Description This problem occurs in the Quartus ® II software version 5.0 when your design targets a Cyclone ™ II device. The Quartus II software uses the wrong assignment names for the JTAG user code in the Quartus II Settings File ( .qsf ), as shown in the following example. set_global_assignment -name APEX20K_JTAG_USER_CODE <JTAG user code> set_global_assignment -name APEX20K_CONFIG_DEVICE_JTAG_USER_CODE <JTAG user code> These assignments are incorrect. Change the incorrect assignment names from APEX20K to STRATIX (when targeting a Cyclone II device) as shown in the following example: set_global_assignment -name STRATIX_JTAG_USER_CODE <JTAG user code> set_global_assignment -name STRATIX_CONFIG_DEVICE_JTAG_USER_CODE <JTAG user code> This issue has been fixed in the Quartus II software version 5.1. Custom Fields values: ['novalue'] Troubleshooting novalue False ['novalue'] ['novalue'] novalue novalue ['Cyclone® FPGAs', 'Cyclone® II FPGAs'] ['novalue'] ['novalue'] ['novalue']