Cmsis v3p00

lpcware · ‎06-15-2016

Content originally posted in LPCWare by serge on Fri Mar 23 04:32:51 MST 2012
Today i got a copy of CMSIS V3P00. :p
Has anyone already used this version of CMSIS?:confused:
If yes is it a good idea to start using it myself?:cool:

And of course can it be used with the lpcxpresso IDE?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by serge on Sun Mar 25 23:37:43 MST 2012
Thanks for the answers. Since the project i am working on works fine (till this point, still adding functionality) with cmsis 2 i will just keep this version. I am not using rtos so i don't see the need to move.

Again thanks for the replys.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Rob65 on Sat Mar 24 00:03:34 MST 2012
I can only agree with this.
If there is no very good reason to change you current project then don't.
And even then ... if you have proven that your setup works, then don't change the base components of that system unless there is a very good reason.

Quote: CodeRedSupport
The main emphasis in this latest release is the CMSIS-RTOS API, and this is causing some "interesting debate".

I have been selecting OSes for their functionality, being speed, memory footprint or special options that we needed in an application.
It seems a bit strange to me to add an extra API to reduce speed and increase the memory footprint.

I do stuff like this on larger systems. For example using Qt as a user interface on Windows/Linux/Mac - but even on those system I cannot get by some system dependencies like device drivers and how to connect to my devices.

Regards,
[INDENT]Rob
[/INDENT]

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Fri Mar 23 15:36:26 MST 2012
CMSIS 3.00 was released by ARM a month ago, and if you want the original sources, then you can download these from www.onarm.com.

The interesting question here though is what do you actually gain from moving to CMSIS 3.00 from CMSIS 2.10 (or for that matter from CMSIS 2.00). And to be honest, the answer for many users is probably "not a lot" - as the core functionality (as provided in the CMSIS library project in LPCXPresso) has hardly changed. The main emphasis in this latest release is the CMSIS-RTOS API, and this is causing some "interesting debate". Those who are interested in what CMSIS RTOS-API provides may find this article interesting...

http://www.eetimes.com/electronics-blogs/industry-comment/4237614/Who-wins-when-Cortex-M-adds-RTOS-a...

Anyway at the current time, Code Red's policy is that we will use the release of CMSIS available at the time we add support for a new MCU family as the basis for the CMSIS library project provided in LPCXpresso. But we will only go back and update the CMSIS libraries for MCUs that we already support after a new CMSIS release when we see an explicit need to do so.

Of course, there is nothing to stop you pulling in the code from the latest CMSIS release from ARM into your own projects if you so desire.

Note - all of the above is talking about the "core" CMSIS functionality. We are not talking about NXP's driver libraries which then sit on top of CMSIS (but which are often referred to CMSIS libraries).

Regards,
CodeRedSupport