4.1. Using SDM Provision Firmware
The Intel® Quartus® Prime Programmer automatically creates and loads a factory default helper image when you select the initialize operation and a command to program something other than a configuration bitstream.
- Provisioning helper image—consists of one bitstream section containing the SDM provisioning firmware.
- QSPI helper image—consists of two bitstream sections, one containing the SDM main firmware and one I/O section.
You may create a factory default helper image file to load into your device prior to performing any programming command. After programming an authentication root key hash, you must create and sign a QSPI factory default helper image because of the included I/O section. If you additionally program the co-signed firmware security setting eFuse, you must create provisioning and QSPI factory default helper images with co-signed firmware. You may use a co-signed factory default helper image on an unprovisioned device as the unprovisioned device ignores non-Intel signature chains over SDM firmware. Refer to Using QSPI Factory Default Helper Image on Owned Devices for more details about creating, signing, and using the QSPI factory default helper image.
quartus_pfg --helper_image -o helper_device=AGFB014R24A -o subtype=PROVISION \ -o fw_source=signed_agilex.zip signed_provision_helper_image.rbf
quartus_pgm -c 1 -m jtag -o “p;signed_provision_helper_image.rbf” --force
You may omit the initialize operation from examples provided in this chapter if you have already programmed a provision helper image.
Did you find the information on this page useful?