The first contact with the CMSIS-RTOS encapsulation layer was back in 2013, and it has been a full 10 years now.The advantages of the encapsulation layer are obvious; it can effectively shield the learning time for everyone using their respective RTOS, requiring only mastery of a single API.
Last night, I was checking if the official version of the CMSIS6 encapsulation layer was released, and I happened to see this post, so I clicked in:
More and more systems are now supported:
In the future, if the underlying interfaces of each middleware also adopt the CMSIS-RTOS V2 encapsulation layer API, it would be like adding wings to a tiger. From then on, you can use whichever middleware you want without worrying about which RTOS or middleware to use. Of course, there are also drawbacks; compatibility is not as good as the original, and continuous iteration and upgrades are needed.
https://github.com/ARM-software/CMSIS_6 https://arm-software.github.io/CMSIS_6/latest/RTOS2/index.html
