CMSIS Version 5 will focus on improvements and further industry adoption. The license will be changed to the permissive Apache 2.0 license, to enable contributions from interested third parties.
Support for the new ARMv8-M architecture will be added as well as improvements for ARM Cortex-A/Cortex-M based hybrid devices (with a clear focus on Cortex-M interaction).
The CMSIS-RTOS API and RTX reference implementation with get several enhancements:
CMSIS-Pack will get additions for generic example projects, project templates, and multiple download portals. It will also adopt the Flash loader technology from IAR Systems.
As announced on embedded world, the development repository of CMSIS Version 5 is now available on GitHub: https://github.com/ARM-software/CMSIS_5
ARM invites all interested parties to contribute and/or to provide feedback for the CMSIS project using GitHub.
Embedded
> CMSIS version 4 and earlier had another license than CMSIS 5 and above. While Liviu is able to change the license for his CMSIS++ project as he wishes, this is not an option for us. Thus, we have decided to create the CMSIS_5 repo
uh? I'm not a lawyer, but what does the license has to do with the the source files being in the same Git or in two?
what is wrong if at a certain moment in time you replace the license notice in all files and push a new commit? up to that moment the files are covered by one license and after that moment the files are covered by another license.
how is this different from having multiple GitHub repos? what if in one month you decide that the MIT license is better? create a new repo? don't you see how meaningless is your approach?
Hello hrusch,
hopefully we do not need to change the license in the future, so no need for an additional repo. Please add your valuable input on the Issues page of CMSIS_5
Ok, license changes may be a valid argument. But why 5? There will never be a version 6? CMSIS-Next? CMIS-whatever?
And by the way: I would love to see if CMSIS is going the way Liviu started to go. With c++11 major roadblocks against c++ are gone.
A threadsafe c and c++ lib with threadsafe STL (libstdc++) and maybe some other allocators to choose (because the default allocator of e.g. gcc is not really matching for embedded systems of that size) would be great.
thanks for your comments. The Readme.md of CMSIS already states what to expect and what do do with it:
The reason for having two different repos is the last one here: CMSIS version 4 and earlier had another license than CMSIS 5 and above. While Liviu is able to change the license for his CMSIS++ project as he wishes, this is not an option for us. Thus, we have decided to create the CMSIS_5 repo for further development and collaboration. I hope you understand this.
Just call the repo CMSIS (or better use the old one, or fork it).
Use branches to seperate different development efforts.
As Liviu stated. Splitting up each version does not help. You already see that there are issues "dangling" in the CMSIS git and may never migrate to the new CMSIS-5 git.
Please consider doing stuff the git/github way if you expect to get feedback.