Secure Partition Manager
The Secure Partition Manager (SPM) sample provides a reference use of the System Protection Unit peripheral. This firmware sets up an nRF device with Trusted Execution (nRF5340 and nRF9160), so that it can run user applications that have Cortex-M Security Extensions enabled, with the resulting separation of firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE).
SPM is deprecated as of nRF Connect SDK v2.1.0 and will be removed in a future version of the SDK. Trusted Firmware-M (TF-M) has replaced SPM as the trusted execution solution.
To use the Secure Partition Manager instead of TF-M, do the following:
Disable the automatic inclusion of TF-M by setting the option
nin the project configuration.
Set the option
The sample supports the following development kits:
The sample uses the SPM to configure secure attributions and jump into the firmware in NSPE.
The SPM utilizes the SPU peripheral to configure security attributions for flash, SRAM, and peripherals. After the configuration setup is complete, the sample loads the application firmware that is located on the device.
See the Secure Partition Manager (SPM) subsystem for information about the security attribution configuration that is applied.
If your application requires a different security attribution configuration, you must update the SPM sample code to reflect this.
The SPM can provide the application firmware with access to Secure Services. See the Secure Partition Manager (SPM) library for information about the available services.
The application firmware must be located in the
slot_nsflash partition. For more details, see the partition configuration file for the chosen board (for example, nrf9160dk_nrf9160_partition_conf.dts for the nRF9160 DK). If you build your application firmware with the nRF Connect SDK, this requirement is automatically fulfilled.
The application firmware must be built for the build target that has CMSE enabled (for example,
nrf9160dk_nrf9160_nsfor the nRF9160 DK).
The sample is automatically built when you configure the application to include Secure Partition Manager and you select a build target with CMSE enabled (for example,
In such scenario, SPM is placed in SPE and the rest of the user application is located in NSPE.
Instead of programming SPE and NSPE at the same time, you might want to program them individually.
To do this, disable the automatic building of SPM by setting the option
CONFIG_SPM=n in the
prj.conf file of the application.
If this results in a single-image build, the start address of the application that has CMSE enabled will change. The security attribution configuration for the flash will change when SPM is not built as a sub-image.
This sample can be found under
samples/spm in the nRF Connect SDK folder structure.
To build the sample with Visual Studio Code, follow the steps listed on the How to build an application page in the nRF Connect for VS Code extension documentation. See Building and programming an application for other building and programming scenarios and Testing and debugging an application for general information about testing and debugging in the nRF Connect SDK.
Program both the sample and your application firmware to the development kit. After power-up, the sample starts your application firmware.
Observe that the application firmware operates as expected.
This sample uses the following nRF Connect SDK libraries: