CMSIS-Zone

The branch main of this GitHub repository contains the CMSIS-Zone Utility that supports the multi-step approach for splitting complex multi-core systems into sub-systems. The CMSIS-Zone documentation is available under https://arm-software.github.io/CMSIS_5/Zone/html/index.html.

CMSIS-Zone is flexible and supports multiple use-cases, for example the setup of MPU (memory protection unit) or TrustZone. It implements the infra-structure that is required for:

• Split of a multi-processor system for single processor views and secure/non-secure views
• TrustZone setup (SAU, Interrupt assignment to Secure/Non-Secure)
• Setup of device specific Memory Protection Controller (MPC)
• Setup of device specific Peripheral Protection Controller (PPC)
• Setup of Memory Protection Unit (MPU)
• Generation of linker scatter files.

The source code of the CMSIS-Zone is released under open source license and part of cmsis-pack-eclipse.

Use Issues to provide feedback and report problems for the CMSIS-Zone Utility and the CMSIS-Zone project examples.

Note: The branch develop of this GitHub repository reflects our current state of example projects and is constantly updated. It allows you to review the work and provide feedback or create pull requests for contributions.

For further details see also the Slides of the Embedded World CMSIS Partner Meeting.

Tool Installation

The installation of CMSIS-Zone is described here https://arm-software.github.io/CMSIS_5/Zone/html/zTInstall.html.

For first steps refer to:

• Configuring Armv8-M systems with CMSIS-Zone - this blog contains a video (at the end) that shows how to operate the CMSIS-Zone utility
• CMSIS-Zone Utility - Examples - the documentation contains examples for different hardware platforms. To get started with a new hardware platform a *.rzone system resource file is required.

Directory Structure

License

Arm CMSIS and the CMSIS-Zone examples in this repository are licensed under Apache-2.0.

Contributions and Pull Requests

Contributions are accepted under Apache-2.0. Only submit contributions where you have authored all of the code.

Issues and Labels

Please feel free to raise an issue on GitHub to report misbehavior (i.e. bugs) or start discussions about enhancements. This is your best way to interact directly with the maintenance team and the community. We encourage you to append implementation suggestions as this helps to decrease the workload of the very limited maintenance team.

We will be monitoring and responding to issues as best we can. Please attempt to avoid filing duplicates of open or closed items when possible. In the spirit of openness we will be tagging issues with the following:

• bug – We consider this issue to be a bug that will be investigated.

• wontfix - We appreciate this issue but decided not to change the current behavior.

• enhancement – Denotes something that will be implemented soon.

• future - Denotes something not yet schedule for implementation.

• out-of-scope - We consider this issue loosely related to CMSIS. It might by implemented outside of CMSIS. Let us know about your work.

• question – We have further questions to this issue. Please review and provide feedback.

• documentation - This issue is a documentation flaw that will be improved in future.

• review - This issue is under review. Please be patient.

• DONE - We consider this issue as resolved - please review and close it. In case of no further activity this issues will be closed after a week.

• duplicate - This issue is already addressed elsewhere, see comment with provided references.

• Important Information - We provide essential informations regarding planned or resolved major enhancements.

Copyright (c) 2019, ARM Limited and Contributors. All rights reserved.