The following table lists the Bootgen command options. Each option is linked to a longer description in the left column with a short description in the right column. The architecture name indicates what AMD device uses that command:
-
zynq: AMD Zynq™ 7000 SoC device -
zynqmp: AMD Zynq™ UltraScale+™ MPSoC -
fpga: Any 7 series FPGA or AMD UltraScale™ /AMD UltraScale+™ FPGA (except AMD Spartan™ UltraScale+™ FPGAs) and above devices -
versal: Versal adaptive SoC -
versal_2ve_2vm: Versal AI Edge Series Gen 2 and Versal Prime Series Gen 2 -
spartanup: AMD Spartan™ UltraScale+™
For more information, see Command Reference.
| Commands | Description and Options | Used by |
|---|---|---|
| arch <type> |
AMD device architecture.
Options:
|
All |
| authenticatedjtag <options> | Used to enable JTAG during secure boot. The arguments are:
|
|
| bif_help | Prints out the BIF help summary. | All |
| dual_qspi_mode <configuration> | Generates two output files for dual QSPI configurations:
|
|
| dual_ospi_mode stacked <size> | Generates two output files for stacked configuration. |
|
| dump <options> | Dumps the partition or boot header as per options specified.
The slave PDIs are not dumped by default. This option should be used if you want to debug or analyze the slave PDI separately. |
|
| dump_dir | Dumps components in specified directory. |
|
| efuseppkbits <PPK_filename> | Generates a PPK hash for eFUSE. |
|
| enable_auth_opt | Used to enable authentication optimization |
|
| encrypt <options> | AES Key storage in device. Options are:
|
|
| encryption_dump | Generates encryption log file, aes_log.txt. |
|
| fill <hex_byte> | Specifies the fill byte to use for padding. |
|
| generate_hashes | Generates file containing padded hash:
|
|
| generate_keys <key_type> | Generate the authentication keys. Options are:
|
|
| h, help | Prints out help summary. | All |
| image <filename(.bif)> | Provides a boot image format (.bif) file name. | All |
| log<level_type> | Generates a log file at the current working directory with following
message types:
|
All |
| nonbooting | Create an intermediate boot image. |
|
| o <filename> | Specifies the output file. The format of the file is determined by the
file name extension. Valid extensions are:
|
All |
| overlay_cdo <filename> | CDO overlay option provides a way to modify CDO files after they are generated. |
|
| p <partname> | Specify the part name used in generating the encryption key. | All |
| padimageheader <option> | Pads the image headers to force alignment of following partitions.
Options are:
|
|
| process_bitstream <option> | Specifies that the bitstream is processed and outputs as .bin or .mcs. For example, if encryption is selected for bitstream in BIF file, the output is an encrypted bitstream. |
|
| read <options> | Used to read boot headers, image headers, and partition headers based
on the options.
|
|
| split <options> | Splits the boot image into partitions and outputs the files as
.bin or .mcs.
|
|
| spksignature <filename> | Generates an SPK signature file. |
|
| verify <filename> | This option is used for verifying authentication of a boot image. All the authentication certificates in a boot image is verified against the available partitions. |
|
| verify_kdf | This option is used to validate the Counter Mode KDF used in Bootgen for generation AES keys. |
|
| w <option> | Specifies whether to overwrite the output files:
Note: The
-w without an
option is interpreted as –w
on. |
All |
| zynqmpes1 | Generates a boot image for ES1 (1.0). The default padding scheme is ES2 (2.0). | zynqmp |