Can the unencrypted peipheral image for use with CvP be used when the anti-tamper bit is set? - Can the unencrypted peipheral image for use with CvP be used when the anti-tamper bit is set? Description When using Configuration via Protocol (CvP) Initialization mode, the periphery image generated by the Convert Programming Files tool is unencrypted. When the anti-tamper bit is set on a device which supports design security, only encrypted files may be used to configure the device. However, the unencrypted periphery image file may be used with a device where the anti-tamper bit has been set but the .rbf (raw binary file) that is used for the core image and is downloaded using the PCI Express® interface must be encrypted using the correct key. Custom Fields values: ['novalue'] Troubleshooting novalue False ['novalue'] ['novalue'] novalue novalue ['Arria® V GT FPGA', 'Arria® V GX FPGA', 'Arria® V GZ FPGA', 'Arria® V ST FPGA', 'Arria® V SX FPGA', 'Cyclone® V GT FPGA', 'Cyclone® V GX FPGA', 'Cyclone® V ST FPGA', 'Cyclone® V SX FPGA', 'Stratix® V GS FPGA', 'Stratix® V GT FPGA', 'Stratix® V GX FPGA'] ['novalue'] ['novalue'] ['novalue']