Intel® Agilex™ Device Security User Guide

ID 683823
Date 1/20/2022
Public

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

Document Table of Contents

4.9.2.5. Location of the PUF in Flash Memory

The location of the PUF file is different for designs that support RSU and designs that do not support the RSU feature.

For designs that do not support RSU, you must include the .puf and .wkey files when you create updated flash images. For designs that support RSU, the SDM does not overwrite the PUF data sections during factory or application image updates.

Table 1.  Flash Sub-Partitions Layout without RSU Support
Flash Offset Size (in bytes) Contents Description
0 K 256 K Configuration Management Firmware Firmware that runs on SDM.
256 K 256 K Configuration Management Firmware
512 K 256 K Configuration Management Firmware
768 K 256 K Configuration Management Firmware
1M 32 K PUF data copy 0 Data structure for storing PUF helper data and PUF-wrapped AES root key copy 0
1M+32 K 32 K PUF data copy 1 Data structure for storing PUF helper data and PUF-wrapped AES root key copy 1
Table 2.  Flash Sub-Partitions Layout with RSU Support
Flash Offset Size (in bytes) Contents Description
0 K 512 K Decision firmware Firmware to identify and load the highest priority image.
512 K 512 K Decision firmware
1 M 512 K Decision firmware
1.5 M 512 K Decision firmware
2 M 8 K + 24K Padding Decision firmware data Reserved for Decision firmware use.
2 M + 32 K 32 K Reserved for SDM Reserved for SDM.
2 M + 64 K Variable Factory image A simple image that you create as a backup if all other application images fail to load. This image includes the CMF that runs on the SDM.
Next 32 K PUF data copy 0 Data structure for storing PUF helper data and PUF-wrapped AES root key copy 0
Next +32 K 32 K PUF data copy 1 Data structure for storing PUF helper data and PUF-wrapped AES root key copy 1
Next + 256 K 4 K Sub-partition table copy 0 Data structure to facilitate the management of the flash storage.
Next +32 K 4 K Sub-partition table copy 1
Next +32 K 4 K CMF pointer block copy 0 A list of pointers to application images in order of priority. When you add an image, that image becomes the highest.
Next +32 K   CMF pointer block copy 1 A second copy of the list of pointers to application images.
Variable Variable Application image 1 Your first application image.
Variable Variable Application image 2 Your second application image.