Visible to Intel only — GUID: dnk1616552984357
Ixiasoft
3.3.1. Configuration Bitstream Encryption Using the Programming File Generator Graphical Interface
3.3.2. Configuration Bitstream Encryption Using the Programming File Generator Command Line Interface
3.3.3. Partially Encrypted Configuration Bitstream Generation Using the Command Line Interface
3.3.4. Partial Reconfiguration Bitstream Encryption
4.1. Using SDM Provision Firmware
4.2. Using QSPI Factory Default Helper Image on Owned Devices
4.3. Authentication Root Key Provisioning
4.4. Programming Key Cancellation ID Fuses
4.5. Canceling Root Keys
4.6. Programming Counter Fuses
4.7. Secure Data Object Service Root Key Provisioning
4.8. Security Setting Fuse Provisioning
4.9. AES Root Key Provisioning
4.10. Converting Owner Root Key, AES Root Key Certificates, and Fuse files to Jam STAPL File Formats
Visible to Intel only — GUID: dnk1616552984357
Ixiasoft
2.2.2. Co-Signing SDM Firmware
You use the quartus_sign tool to extract, sign, and install the applicable SDM firmware .zip file. The co-signed firmware is then included by the programming file generator tool when you convert .sof file into a configuration bitstream .rbf file. You use the following commands to create a new signature chain and sign SDM firmware.
- Create a new signing key pair.
- Create a new signing key pair on the file system:
quartus_sign --family=agilex --operation=make_private_pem \ --curve=secp384r1 firmware1_private.pem
quartus_sign --family=agilex --operation=make_public_pem \ firmware1_private.pem firmware1_public.pem
- Create a new signing key pair in the HSM:
pkcs11-tool --module=/usr/local/lib/softhsm/libsofthsm2.so \ --token-label agilex-token --login \ --pin agilex-token-pin \ --keypairgen -–mechanism ECDSA-KEY-PAIR-GEN \ --key-type EC:secp384r1 \ --usage-sign --label firmware1 --id 1
- Create a new signing key pair on the file system:
- Create a new signature chain containing the new public key:
quartus_sign --family=agilex --operation=append_key \ --previous_pem=root0_private.pem \ --previous_qky=root0.qky \ --permission=0x1 --cancel=1 \ --input_pem=firmware1_public.pem firmware1_sign_chain.qky
quartus_sign --family=agilex --operation=append_key --module=softHSM \ --module_args="--token_label=agilex-token \ --user_pin=agilex-token-pin \ --hsm_lib=/usr/local/lib/softhsm/libsofthsm2.so" \ --previous_keyname=root0 \ --previous_qky=root0.qky \ --permission=1 --cancel=1 \ --input_keyname=firmware1 firmware1_sign_chain.qky
- Copy the firmware .zip file from your Intel® Quartus® Prime Pro Edition software installation directory ( <install_dir>/quartus/common/devinfo/programmer/firmware/agilex.zip ) to the current working directory.
quartus_sign --family=agilex --get_firmware=.
- Sign the firmware .zip file. The tool automatically unpacks the .zip file and individually signs all firmware .cmf files, then rebuilds the .zip file for use by the tools in the following sections:
quartus_sign --family=agilex --operation=sign \ --qky=firmware1_sign_chain.qky \ --cancel=svnA:0 \ --pem=firmware1_private.pem agilex.zip signed_agilex.zip
quartus_sign --family=agilex --operation=sign --module=softHSM \ --module_args="--token_label=agilex-token \ --user_pin=agilex-token-pin \ --hsm_lib=/usr/local/lib/softhsm/libsofthsm2.so" \ --keyname=firmware1 \ --cancel=svnA:0 \ --qky=firmware1_sign_chain.qky agilex.zip signed_agilex.zip
Did you find the information on this page useful?
Feedback Message
Characters remaining: