Skip to content

Commit a64d535

Browse files
authored
Update spm.md
1 parent 3dedaab commit a64d535

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/porting/psa/spm.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ These is demonstrated in the example below:
5858

5959
#### Memory layout
6060

61-
Typically, PSA platforms share the same RAM and flash between secure and nonsecure cores. To provide PSA isolation level 1 or higher, you need to partition both RAM and flash in a way the following image describes:
61+
Typically, PSA platforms share the same RAM and flash between secure and nonsecure cores. To provide PSA isolation level 1 or higher, you need to partition both RAM and flash to secure and nonsecure parts, in a way the following image describes:
6262

6363
```text
6464
RAM
@@ -77,6 +77,8 @@ Typically, PSA platforms share the same RAM and flash between secure and nonsecu
7777

7878
To achieve RAM and flash partitioning, you must add start and size values to a target configuration in `targets.json` as in the example above.
7979

80+
Note that for isolation levels higher than 1, on top of the partitioning between secure and nonsecure parts, secure flash and RAM must have an inner level of partitioning, creating sections per secure partition.
81+
8082
### Linker scripts
8183

8284
Linker scripts must include `MBED_ROM_START`, `MBED_ROM_SIZE`, `MBED_RAM_START` and `MBED_RAM_START` macros for defining memory regions. You can define a shared memory region by reserving RAM space for shared memory use. The shared memory location is target specific and depends on the memory protection scheme applied.

0 commit comments

Comments
 (0)