5.2. HPS Debug Certificates
You then compile and load the design with these settings.
quartus_sign --family=agilex --operation=append_key \ --previous_pem=root_private.pem --previous_qky=root.qky \ --permission=0x8 --cancel=1 \ hps_debug_cert_public_key.pem hps_debug_cert_sign_chain.qky
quartus_pgm -c 1 -m jtag -o “e;unsigned_hps_debug.cert;AGFB014R24A”
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
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?