Note:
AMD recommends that you generate your own keys
and seeds for fielded systems using a high-quality entropy source and then provide those
values to the development tools. Bootgen key generation is intended for development and
prototyping use. Keys or seeds not generated from a high-quality entropy source can be
weak, which means they can be predictable or could be brute-forced. Auto-generated
values can be useful during development or test flows when production values are not yet
available to engineers, but they are not intended for fielded systems.
Note: When the tool generates a seed automatically for supported
KDF-based flows, the current implementation uses OpenSSL RAND_Bytes. AMD
incorporates a snapshot of the OpenSSL library as-is for this purpose. For fielded
systems, this implementation detail does not change the recommendation to provide your
own keys or seeds from a high-quality entropy source.
- AMD recommends that you generate your own keys for fielded systems and then provide those keys to the development tools. See AR76171 for more information.
- Starting with Versal adaptive SoC 2022.2, we reduced the
maximum number of partitions from 32 to 20 to cut PLM size and ensure it fits in PPU
RAM. We also reduced the maximum number of images/subsystems from 32 to 10. If the
limit exceeds, Bootgen errors out while creating the Boot Image.
The option for disabling this error is to use the
BOOTGEN_SKIP_MAX_PARTITIONS_CHECKenvironment variable.Ensure that you handle changes in the PLM code as well, and then proceed to create PDIs with any number of partitions/images.
- AMD Versal™ Bootgen Support Updates: Refer to Answer Record 34634 for more details.
- You might see the following warning when using a bootimage in the bif:
In contradiction to this warning, Bootgen is using[WARNING]: ID code is taken from base PDI, ignoring 'id_code' specified in the BIFid_codefrom BIF instead of base pdi. AMD recommends using properid_codein the bif.