5.2. HPS Debug Certificates
- Click the Intel® Quartus® Prime software Assignments menu and select Device > Device and Pin Options > Configuration tab.
- In the Configuration tab, enable the HPS debug access port (DAP) by selecting either HPS Pins or SDM Pins from the dropdown menu, and ensuring the Allow HPS debug without certificates checkbox is not selected.
Figure 14. Specify Either HPS or SDM Pins for the HPS DAP
- Compile and load the design with these settings.
- Create a signature chain with the appropriate permissions to sign an HPS debug certificate:
quartus_sign --family=agilex --operation=append_key \ --previous_pem=root_private.pem \ --previous_qky=root.qky \ --permission=0x8 --cancel=1 \ --input_pem=hps_debug_cert_public_key.pem hps_debug_cert_sign_chain.qky
- Request an unsigned HPS debug certificate from the device where the debug design is loaded:
quartus_pgm -c 1 -m jtag -o “e;unsigned_hps_debug.cert;AGFB014R24A”
- Sign the unsigned HPS debug certificate using the quartus_sign tool or reference implementation and the HPS debug signature chain:
quartus_sign --family=agilex --operation=sign \ --qky=hps_debug_cert_sign_chain.qky \ --pem=hps_debug_cert_private_key.pem \ unsigned_hps_debug.cert signed_hps_debug.cert
- Send the signed HPS debug certificate back to the device to enable access to the HPS debug access port (DAP):
quartus_pgm -c 1 -m jtag -o “p;signed_hps_debug.cert"
The HPS debug certificate is only valid from the time it was generated until the next power cycle of the device or until a different type or version of SDM firmware is loaded. You must generate, sign, and program the signed HPS debug certificate, and perform all debug operations, prior to power cycling the device. You may invalidate the signed HPS debug certificate by power cycling the device.
Did you find the information on this page useful?