Why does the Intel® Quartus® Prime Pro/Standard Edition Programmer generate an incorrect chain description file (.cdf) when using a custom helper image to flash QSPI? - Why does the Intel® Quartus® Prime Pro/Standard Edition Programmer generate an incorrect chain description file (.cdf) when using a custom helper image to flash QSPI? Description Due to a problem in the Intel® Quartus® Prime Pro/Standard Edition Programmer tool version 23.1 and earlier, an incorrect .cdf of a chain path to program a QSPI Flash device may be generated. This happens when using a custom helper image as a flasher and a QSPI device different from the EPCS, EPCQ, and N25Q families. Resolution To work around this problem, manually edit the .cdf file . Add SFLPath() argument inside MfrSpec() and reference the flash file path inside SFLPath(). For example: P ActionCode(Cfg) Device PartName(1SG280HU2F50) Path("/output_files/") File("qspi_helper_image.rbf") MfrSpec(OpMask(1) SEC_Device(MT25QU01G) Child_OpMask(1 1) SFLPath("/output_files/flash_file.jic"); ChainEnd; This problem is scheduled to be fixed in a future release of the Intel® Quartus® Prime Pro/Standard Edition Programmer. Custom Fields values: ['novalue'] Troubleshooting 14018454764 False ['novalue'] ['FPGA Dev Tools Quartus® Prime Software'] 23.2 22.3 ['Agilex™ FPGA Portfolio', 'Arria® 10 Bare Die', 'Cyclone® Bare Die', 'MAX® CPLDs', 'Stratix® FPGAs'] ['Quartus® Prime Pro Edition Programmer and Tools'] ['novalue'] ['novalue']