Intel® Agilex™ Device Security User Guide

ID 683823
Date 10/31/2022
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

5.1. Secure Debug Authorization

To enable Secure Debug Authorization, the debug owner needs to generate an authentication key pair and use the Intel® Quartus® Prime Pro Programmer to generate a device information file for the device that runs the debug image:
quartus_pgm -c 1 -m jtag -o “ei;device_info.txt;AGFB014R24A” --dev_info
The device owner uses the quartus_sign tool or the reference implementation to append a conditional public key entry to a signature chain intended for debug operations using the public key from the debug owner, the necessary authorizations, the device information text file, and applicable further restrictions:
quartus_sign --family=agilex --operation=append_key \ 
--previous_pem=debug_chain_private.pem \
--previous_qky=debug_chain.qky \
--permission=0x6 --cancel=1 \
--dev_info=device_info.txt \
--restriction=”1,2,17,18” \
--input_pem=debug_authorization_public_key.pem secure_debug_auth_chain.qky
The device owner sends the full signature chain back to the debug owner, who uses the signature chain and their private key to sign the debug image:
quartus_sign --family=agilex --operation=sign \ 
--qky=secure_debug_auth_chain.qky \
--pem=debug_authorization_private_key.pem \
unsigned_debug_design.rbf authorized_debug_design.rbf 
The debug owner can then program the securely authorized debug design:
quartus_pgm -c 1 -m jtag -o “p;authorized_debug_design.rbf” 

The device owner may revoke the secure debug authorization by canceling the explicit key cancellation ID assigned in the secure debug authorization signature chain.

Did you find the information on this page useful?

Characters remaining:

Feedback Message