Why Can't We Read the Usercode After Executing an Action Followed by the Optional Procedures? - Why Can't We Read the Usercode After Executing an Action Followed by the Optional Procedures? Description A combination of executing an action followed by the optional procedures command can lead to unexpected errors. For instance, when enabling a procedure tied to an action statement with the following command syntax: quartus_jli.exe -a verify -d do_read_usercode <file name>.jbc In this case, an unexpected error may occur, resulting in an incorrect USERCODE output, such as: Device #1 USERCODE is FFFFFFF This suggests that an error may arise during the process, leading to the incorrect usercode being displayed. Resolution This issue occurs specifically when using the Quartus® Lite version. To resolve this, please use either Quartus® Prime Standard or Quartus® Prime Pro versions, which should prevent the error and allow for correct USERCODE reading. Custom Fields values: ['novalue'] Troubleshooting 15016770220 False ['novalue'] ['FPGA Dev Tools Quartus® Prime Software QUARTUS-ALITE'] No plan to fix No plan to fix ['Programmable Logic Devices'] ['novalue'] ['novalue'] ['novalue']