Why is the size of a generated compressed .rpd file the same as the uncompressed .rpd file? - Why is the size of a generated compressed .rpd file the same as the uncompressed .rpd file? Description The .rpd file size is generated depending on the .pof file size. The .pof file will always be the same size as the flash or configuration device it is targeting. The.rpd file size is dependent on the .pof file size, therefore the capacity of the .rpd file is the same as the flash or configuration device it is targeting. The size of the .rpd file will not change even though you enable compression mode. In order to identify if the generated .rpd file has been compressed or not, refer to the end address in the text .map file. You can compare the end address before and after compression mode is enabled. For the compressed .rpd file, the end address should be at a lower address location compared to the uncompressed .rpd file. Related Articles Is it possible to reduce the generated Raw Programming Data (.rpd) file size? How do I generate Raw Programming Data (.rpd) files for EPCS or EPCQ configuration devices which only contain configuration data? Custom Fields values: ['novalue'] Troubleshooting novalue False ['novalue'] ['novalue'] novalue novalue ['Programmable Logic Devices'] ['novalue'] ['Configuration Devices'] ['novalue']