Why is the fail flag in the EMIF Traffic Generator 2.0 not asserted when the WORM mode is enabled, and a data mismatch is encountered? - Why is the fail flag in the EMIF Traffic Generator 2.0 not asserted when the WORM mode is enabled, and a data mismatch is encountered? Description When the TG_LOOP_COUNT register is greater than 1 and the Write Once Read Many (WORM) mode is enabled, the Traffic Generator Fail (TGF) flag is not asserted when a data mismatch is encountered due to a problem in the Intel® Quartus® Prime Pro Edition software version 20.4. Note that the WORM mode is disabled by default. Resolution The problem has been fixed in the Intel® Quartus® Prime Pro Edition software version 21.1 . Custom Fields values: ['novalue'] Troubleshooting 14012681904 False ['External Memory Interfaces Debug Component IP'] ['FPGA Dev Tools Quartus® Prime Software Pro'] 21.1 20.3 ['Agilex™ 7 FPGAs and SoCs'] ['novalue'] ['novalue'] ['novalue']