Why does the Device ID format of the configuration device not follow the standard sequence of Manufacturer ID, Memory Type, and Memory Density in the Programming File Generator? - Why does the Device ID format of the configuration device not follow the standard sequence of Manufacturer ID, Memory Type, and Memory Density in the Programming File Generator? Description The Device ID is displayed incorrectly when the bytes are mistakenly ordered as: the first byte the Memory Density, the second byte the Memory Type, and the third byte the Manufacturer ID. Resolution Please follow the correct order of 4.1 Generating Programming Files using Programming File Generator . On the Configuration Device tab, click Add Device . Select <<new device>> from the Configuration Device list, key in a few inputs as below: Device name – a new part name for your QSPI flash device. Device ID—the ID that can be found in the flash device datasheet. The order should follow the first byte, the Manufacturer ID, the second byte, the Memory Type, and the third byte, the Memory Density, for example 0xC2 0x20 0x19. Device density– follow the density of the flash device. Other inputs are not needed; they are designed for non-SDM devices. This issue will be fixed in the Quartus® Prime Pro Software version 25.3. Custom Fields values: ['novalue'] Troubleshooting 15017923983 False ['novalue'] ['FPGA Dev Tools Quartus® Prime Software Pro'] 25.3 25.1 ['Agilex™ FPGA Portfolio', 'Stratix® 10 FPGAs and SoCs'] ['Quartus® Prime Pro Edition Programmer and Tools'] ['novalue'] ['novalue']