You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/porting/psa/spm.md
+6-7Lines changed: 6 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -8,15 +8,14 @@ For more information about SPM, please refer to [the SPM overview page](/docs/de
8
8
9
9
### New target configuration
10
10
11
-
When adding a new target, a new root target node should be added to mbed-os/targets/targets.json file.
12
-
For PSA support, specific PSA related fields should be defined for this target:
11
+
When adding a new target, a new root target node should be added to the `mbed-os/targets/targets.json` file. For PSA support, define specific PSA-related fields for this target:
13
12
14
-
1. Secure target must inherit from `SPE_Target`meta-target.
13
+
1. Secure target must inherit from `SPE_Target`metatarget.
15
14
2. Nonsecure target must inherit from `NSPE_Target`.
16
15
3. Only for multicore architectures:
17
-
- Both targets must add "SPM_MAILBOX" component. Mailbox mechanism is explained in [Mailbox section](#mailbox)
18
-
- Both targets must override the default configuration by specifying flash RAM and shared RAM regions. This is explained in more details in [Memory layout section](#memory-layout)
19
-
- Secure target must declare which is its corresponding nonsecure target using the "deliver_to_target" field.
16
+
- Both targets must add the `SPM_MAILBOX` component. You can read more about the mailbox mechanism in the [mailbox section](#mailbox).
17
+
- Both targets must override the default configuration by specifying flash RAM and shared RAM regions. The [memory layout section](#memory-layout) explains this in more detail.
18
+
- Secure target must declare its corresponding nonsecure target using the `deliver_to_target` field.
20
19
21
20
These is demonstrated in the example below:
22
21
@@ -210,7 +209,7 @@ These are the guidelines you should follow if you have multicore systems:
210
209
- For each core, implement the IPC event handler (usually interrupt handler):
211
210
- The handler must call an Arm callback function. Refer to [HAL functions section](#hal-functions) for more details.
212
211
- For each core, implement the HAL function that notifies the peer processor about a mailbox event occurrence. This is a part of the HAL, and the section below explains this in more detail.
213
-
- For each core, add the "SPM_MAILBOX" component field for its target node in mbed-os/targets/targets.json file.
212
+
- For each core, add the `SPM_MAILBOX` component field for its target node in the `mbed-os/targets/targets.json` file.
0 commit comments