From 96d6da4e252b06dcfdc041e7df23e86161c33007 Mon Sep 17 00:00:00 2001 From: rihab kouki Date: Tue, 28 Jul 2020 11:24:49 +0100 Subject: Official ARM version: v5.6.0 --- docs/Zone/html/zTUIZonePart.html | 151 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 151 insertions(+) create mode 100644 docs/Zone/html/zTUIZonePart.html (limited to 'docs/Zone/html/zTUIZonePart.html') diff --git a/docs/Zone/html/zTUIZonePart.html b/docs/Zone/html/zTUIZonePart.html new file mode 100644 index 0000000..169556b --- /dev/null +++ b/docs/Zone/html/zTUIZonePart.html @@ -0,0 +1,151 @@ + + + + + +Zone Partitioning +CMSIS-Zone (Preview): Zone Partitioning + + + + + + + + + + + + + + +
+
+ + + + + + + +
+
CMSIS-Zone (Preview) +  Version 0.9.2 +
+
System Resource Management
+
+
+ +
+
    + +
+
+ + + +
+
+ +
+
+
+ +
+ + + + +
+ +
+ +
+
+
Zone Partitioning
+
+
+

Every CMSIS-Zone project consists of one or more zones. The basic flow to create zones is as follows:

+
    +
  • In case of multi-core devices, create a zone for each processor.
    • +
  • Then create at least one zone for each processor to be able to assign memories and peripherals. If your device contains Arm Cortex-M cores supporting TrustZone for Armv8-M, create a secure and a non-secure partition for each of these cores.
    • +
+

+Create Zones

+

To split a multi-processor system into single-processor sub-systems, you need to create new zones. Switch to the Zones tab and click the Add new zone button:

+
+AddNewZoneButton.png +
+

In the new window, you need to specify a name for the zone, select the applicable core, and choose the security level (secure/non-secure).

+

In the Musca example, a new zone called "CM33_0" was created and attached to processor core 0 without any security attribute (not specified):

+
+NewZoneCM33_0.png +
+

Similarly, an additional zone called "CM33_1" was created and attached to processor core 1, without security attribute.

+

Save your settings:

+
+SaveButton.png +
+
Note
+

Adding zones only works for the currently opened .azone file. The information about the zones is stored in the /azone/zones element element of the *.azone file.

+
+
+ + + + -- cgit