NXP Semiconductors SLN-LOCAL2-IOT, User Manual

Page: 74 / 87

— <ca_name>.root.ca.crt.pem
• ./ca/private/
— <ca_name>.app.a.key.pem
— <ca_name>.app.b.key.pem
— <ca_name>.root.ca.key.pem
11.2.2 Installing the CA and application certificates
For the device to verify the image signature, the device must have the root CA and application certificates. Before
programming it into the device, it must be converted into a binary format for the filesystem to use it. To do this, run the
“generate_image_crt_files.py” script. Pass in the name of the generated CA in the command line.
Execute the command with the "-ft H" attribute for the HyperFlash and "-ft Q" for the QSPI, as shown in
Figure 82 .
Figure 82. Signing artifacts binary files generation for HyperFlash
The output of this script are two binary files – ca_crt.bin and app_crt.bin. Move these files to the Image_Binaries folder of the Ivaldi
package, as shown in
Figure 83 . They will be programmed into the SLN-LOCAL2-IOT kit by a boot programming tool.
Figure 83. Moving ca_crt.bin and app_crt.bin to Image_Binaries folder
11.3 Open Boot Programming tool
The Open Boot Programming tool is responsible for connecting to the device and programming it with the correct images and
certificates. This method is a quick and easy way to take a device/product from the assembly line and prepare it for shipping. It is a
good practice to run the Open Boot Programming script before enabling the HAB to ensure all images and artifacts are in working
order. Before running the script, complete the following items:
• The files and folders shown in Figure 84 should be in the “Image_Binaries” folder in the Ivaldi root.
NXP Semiconductors
Automated manufacturing tools
SLN-LOCAL2-IOT Developer’s Guide, Rev. 0, 19 April 2021
User's Guide 74 / 87