Why do I have to run number of manual steps to create a signed aocx file in Intel® Acceleration Stack 2.0.1? - Why do I have to run number of manual steps to create a signed aocx file in Intel® Acceleration Stack 2.0.1? Description There is a bunch of manual steps described in section 3.7.1 Signing OpenCL Images under the Security User guide for Intel® FPGA Programmable Acceleration Card D5005. Resolution This process has been automated by creating a script that runs all these steps for you. sign_aocx.sh Copy the script at a known location with the Intel® Acceleration Stack installation. Usage information as below: 1) For creating signed aocx run command : ./sign_aocx.sh [[[-H hsm_manager] [-i input_file ] [-r rootpublickey][-k cskkey] [-o output_file]]]| [-h]] 2) For creating unsigned images run command : ./sign_aocx.sh [[[-H hsm_manager] [-i file ] [-r NULL] [-k NULL] [-o output_file] Custom Fields values: ['novalue'] Troubleshooting N/A False ['novalue'] ['FPGA Dev Tools Quartus® Prime Software Pro'] novalue 19.2 ['Programmable Logic Devices'] ['novalue'] ['novalue'] ['novalue']