RISAB internal peripheral

Applicable for

Unknown MPU, Unknown MPU, STM32MP25x lines

---

1. Article purpose

The purpose of this article is to:

• Briefly introduce the RISAB peripheral and its main features.
• Indicate the peripheral instances assignment at boot time and their assignment at runtime (including whether instances can be allocated to secure contexts).
• List the software frameworks and drivers managing the peripheral.
• Explain how to configure the peripheral.

2. Peripheral overview

The RISAB peripheral is part of the RIF. It is used to protect internal RAMs.
Its main features are:

• Configuration at fixed size memory blocks (512 B) and pages (4 KB)
• Access filtering per:
  • secure level
  • CID filtering
  • privilege level per CID
  • read-only, write-only, or read/write per CID
• Possibility to delegate page configuration to a specified execution context defined by delegated configuration CID. Useful to manage memory region access right at software component level instead of requiring changes to TDCID secure OS.

Refer to the STM32 MPU reference manuals for the complete list of features, and to the software frameworks and drivers, introduced below, to see which features are implemented.

3. Peripheral usage

This chapter is applicable in the scope of the OpenSTLinux BSP running on the Arm^® Cortex^®-A processor, and the STM32CubeMPU Package running on the Arm^® Cortex^®-M processor.

On STM32MP25x lines  and STM32MP23 unknown microprocessor device, there are six RISAB instances. On STM32MP21 unknown microprocessor device, there are only four (RISAB4 and RISAB6 are removed). The following table shows RISAB - internal SRAM mapping and provides information regarding RISAB programming owner and default hardware configuration.
RISAB registers are accessible in read by all execution context to check memory can be accessed or not.

RISAB instance	Internal SRAM	Owner	Default configuration
RISAB1	SYSRAM1 (lower 128 KB)	Cortex-A35 secure	Secure, unprivileged, any CID
RISAB2	SYSRAM2 (upper 128 KB)	Cortex-A35 secure	Secure, unprivileged, any CID
RISAB3	SRAM1 (lower 128 KB)	TDCID secure	Nonsecure, unprivileged, any CID
RISAB4	SRAM2 (upper 128 KB)	TDCID secure	Nonsecure, unprivileged, any CID
RISAB5	RETRAM	TDCID secure	Secure, unprivileged, any CID
RISAB6	VDERAM	TDCID secure	Nonsecure, unprivileged, any CID

RISAB configurations are done during bootflow according to memory usage. The ROM code and the FSBL perform an initial RISAB configuration to allow and secure their execution. The RISAB configuration for runtime execution is applied afterwards by the TDCID secure OS.

3.1. Boot time assignment

3.1.1. On STM32MP21 unknown microprocessor device

Click on to expand or collapse the legend...

• ☐ means that the peripheral can be assigned to the given boot time context.
• ☑ means that the peripheral is assigned by default to the given boot time context and that the peripheral is mandatory for the STM32 MPU Embedded Software distribution.
• ⬚ means that the peripheral can be assigned to the given boot time context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
• ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.

The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32MP25 reference manuals.

Domain	Peripheral	Boot time allocation				Comment
		Instance	Cortex-A35 secure (ROM code)	Cortex-A35 secure (TF-A BL2)	Cortex-A35 non-secure (U-Boot)
Security	RISAB	RISAB1	✓	✓	⬚
		RISAB2	✓	✓	⬚
		RISAB3	✓	⬚	⬚	Used by ROM code only in serial boot for USB buffer management
		RISAB5	✓	⬚	⬚	Used by ROM code only during cold boot

3.1.2. On STM32MP23 unknown microprocessor device

Click on to expand or collapse the legend...

• ☐ means that the peripheral can be assigned to the given boot time context.
• ☑ means that the peripheral is assigned by default to the given boot time context and that the peripheral is mandatory for the STM32 MPU Embedded Software distribution.
• ⬚ means that the peripheral can be assigned to the given boot time context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
• ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.

The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32MP25 reference manuals.

Domain	Peripheral	Boot time allocation				Comment
		Instance	Cortex-A35 secure (ROM code)	Cortex-A35 secure (TF-A BL2)	Cortex-A35 non-secure (U-Boot)
Security	RISAB	RISAB1	✓	✓	⬚
		RISAB2	✓	✓	⬚
		RISAB3	✓	⬚	⬚	Used by ROM code only in serial boot for USB buffer management
		RISAB4		⬚	⬚
		RISAB5	✓	⬚	⬚	Used by ROM code only during cold boot
		RISAB6		⬚	⬚

3.1.3. On STM32MP25x lines 

Click on to expand or collapse the legend...

• ☐ means that the peripheral can be assigned to the given boot time context.
• ☑ means that the peripheral is assigned by default to the given boot time context and that the peripheral is mandatory for the STM32 MPU Embedded Software distribution.
• ⬚ means that the peripheral can be assigned to the given boot time context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
• ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.

The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32MP25 reference manuals.

Domain	Peripheral	Boot time allocation				Comment
		Instance	Cortex-A35 secure (ROM code)	Cortex-A35 secure (TF-A BL2)	Cortex-A35 non-secure (U-Boot)
Security	RISAB	RISAB1	✓	✓	⬚
		RISAB2	✓	✓	⬚
		RISAB3	✓	⬚	⬚	Used by ROM code only in serial boot for USB buffer management
		RISAB4		⬚	⬚
		RISAB5	✓	⬚	⬚	Used by ROM code only during cold boot
		RISAB6		⬚	⬚

3.2. Runtime assignment

3.2.1. On STM32MP21 unknown microprocessor device

| rowspan="4" | Security | rowspan="4" | RISAB | RISAB1 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB2 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB3 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB5 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |-

|}

3.2.2. On STM32MP23 unknown microprocessor device

| rowspan="6" | Security | rowspan="6" | RISAB | RISAB1 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB2 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB3 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB4 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB5 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |- | RISAB6 | ☑^OP-TEE | ⬚ | ☐ | ⬚ | |-

|}

3.2.3. On STM32MP25x lines 

Click on to expand or collapse the legend...

STM32MP25 internal peripherals

Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:

• ☐ means that the peripheral can be assigned to the given runtime context.
• ☑ means that the peripheral is assigned by default to the given runtime context and that the peripheral is mandatory for the STM32 MPU Embedded Software distribution.
• ⬚ means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
• ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.

Refer to How to assign an internal peripheral to an execution context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32MP25 reference manuals.

Domain	Peripheral	Runtime allocation						Comment
		Instance	Cortex-A35 secure (OP-TEE / TF-A BL31)	Cortex-A35 non-secure (Linux)	Cortex-M33 secure (TF-M)	Cortex-M33 non-secure (STM32Cube)	Cortex-M0+ (STM32Cube)
Security	RISAB	RISAB1	☑OP-TEE	⬚	☐	⬚
		RISAB2	☑OP-TEE	⬚	☐	⬚
		RISAB3	☑OP-TEE	⬚	☐	⬚
		RISAB4	☑OP-TEE	⬚	☐	⬚
		RISAB5	☑OP-TEE	⬚	☐	⬚
		RISAB6	☑OP-TEE	⬚	☐	⬚

4. Software frameworks and drivers

Below are listed the software frameworks and drivers managing the RISAB peripheral for the embedded software components listed in the above tables.

• TF-A: bl2_el3_plat_arch_setup()
• OP-TEE: RISAB driver
• TF-M: Unsupported domain!
• Linux: RISAB dump driver

5. How to assign and configure the peripheral

The STM32CubeMX graphical tool proposes an interface to configure the different RISAB memory regions.
It is possible to select for each region:

• the security level
• the privilege level
• if the region is encrypted or not (depends on RISAF capability)
• the master CID

The STM32CubeMX will generate the associated device tree configuration for the FSBL and secure OS running on the TDCID processor.

Microprocessor unit

Resource Isolation Slave unit for Address space protection (Block-based) - NEW

Resource Isolation Framework

Compartment IDentifier: identifier added to any bus master peripheral transaction for emitter identification and filtering.

Trusted Domain Compartment IDentifier - NEW

Operating system

Board support package

Arm^® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.

Cortex^®

Read only memory

First stage boot loader

Trusted firmware for Arm^® Cortex^®-A

Boot loader stage 2

Das U-Boot -- the universal boot loader (see U-Boot)

Open portable trusted execution environment

Linux^® is a registered trademark of Linus Torvalds.

Resource Isolation Slave unit for Address space protection (Full version) - NEW