Add Zephyr module metadata (#295)
Add zephyr/module.yml to allow CMSIS v6 to be consumed as a Zephyr module.
This enables Zephyr to use CMSIS-Core directly from upstream without requiring downstream changes in this repository, allowing straightforward synchronization with future updates (e.g. via standard GitHub fork sync workflows).
Use external CMake and Kconfig integration so that all Zephyr-specific build logic remains in the Zephyr repository. This keeps CMSIS_6 independent of any particular build system and preserves portability for non-Zephyr users.
The change is minimal and does not affect existing CMSIS_6 users or workflows.
For more details on Zephyr modules, see: https://docs.zephyrproject.org/latest/develop/modules.html
Signed-off-by: Sudan Landge sudan.landge@arm.com
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
CMSIS Version 6
Useful Links
Other related GitHub repositories
Directory Structure
Generate CMSIS Pack for Release
This GitHub development repository lacks pre-built libraries of various software components (RTOS, RTOS2). In order to generate a full pack one needs to have the build environment available to build these libraries. This causes some sort of inconvenience. Hence the pre-built libraries may be moved out into separate pack(s) in the future.
To build a complete CMSIS pack for installation the following additional tools are required:
Using these tools, you can generate on a Windows PC:
License
Arm CMSIS is licensed under
.
Contributions and Pull Requests
Contributions are accepted under
. 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: