We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello,
I recently installed Keil MicroVision 5.0 and started working with an STM32 MCU.
I was impressed by the highly standardized environment that lets you use peripheral in minutes. However I understand that this environment is quite preliminary, at least as stated in the CMSIS documentation site: "It is intended to standardize these Peripheral Driver Interfaces as part of a future CMSIS release." on the Driver API main page and the Software Packs Concept description labeled "Release for beta review".
Actually, I already found (and easily fixed) a few bugs in the library. Anyway, I am really willing to go on using it, since it is so a way better approach than anything around before it.
In short, my question is: how long should we wait for this thing to go mainstream and fully supported?
Thanks and regards.
Marco
Hello Marco,
it's great to hear that you like the new Software Pack concept in MDK v5.
We are still discussing the CMSIS-DRIVER and CMSIS-PACK concepts with our ecosystem partners, but you can consider CMSIS-PACK as practically complete. Any final modifications will be small and backwards-compatible.CMSIS-DRIVER also is well advanced, and we don't expect any compatibility issues with the final release.
A public announcement is expected in Q1 next year.
Regards,
Johannes
Hello Johannes,
thank you for your reply, so I can rely on a final version of CMSIS-DRIVER becoming available in the next months.
I don't know to what extent ecosystem partners (e.g. ST) are involved in the development. If it can be useful, I would like to share the changes I made to the libraries in order to have them work correctly.
As for the API, I would suggest extending a bit the SPI driver to cover more use cases, namely allowing more configuration options (e.g. Master or Slave operation) and adding a multiple-byte Read-while-Write transfer API managed with interrupt and DMA like the Read and Write APIs already present.
Hi Marco,
thank you for your suggestions.
I would like to discuss how we can incorporate your improvements to the library - could you please message me privately for details?
Thanks,
Hi Marco
I'm facing the same situation as you. So I'm just waiting for the first drop of the drivers.
In the meanwhile, I'm trying to sketch my application with the preliminary release, but some stuff (i.e. the SPI) is not working properly.
Can you share somehow (in prv, if you prefer) the bugfixes you made so I can go on with my debug?
That would be really appreciated.
Best regards,
Nicola
Hi johannes,
For one of my projects i am planning to include CMSIS Drivers. I did a study on that and understand various benefits of it, but i have the following doubts. It would be great if you can clarify me.
CMSIS pack comes with a CMSIS driver API(Driver_UART.h, Driver_SPI.h etc), I believe that this header files should be adapted by the silicon vendor while they develop CMSIS compliant drivers. But when i download CMSIS compliant driver from ST(STM32F10x series) this header files are not used at all.
1. Can you please clarify how can i get the same or is it under development?.
2. If so when can we expect the CMSIS Driver API for all the peripherals?
Hi vijithn,
we have published the CMSIS-Driver API and you understood correctly that the goal is for the silicon vendors to include compliant drivers with the device support they supply.
We are in active discussions to make this happen, and there are a few partners who are close to releasing Device Family Packs (DFPs) with drivers included, and a few more who are considering it or started working on it.
For Keil MDK, we supply DFPs for some device families where we added CMSIS-Drivers.
For example, take a look at the Device Database page for STM32F100C4. It shows which drivers are available in the DFP and gives you a download link.
Mind you, these drivers are not fully compatible to the CMSIS-Driver API that was published in CMSIS Version 4, but we are working on that together with ST Micro.
We will publish more DFPs with drivers within the next four weeks.
The long-term goal, however, is for the silicon vendors to pick up and embrace CMSIS-Drivers.If you think CMSIS-Drivers will be useful for you, I encourage you to approach the silicon vendor of your choice about it to make sure they see a demand for it.
Thanks,Johannes
Is there any chance Keil will update the Freescale Kinetis series, specifically K20, with a 2.00 CMSIS Driver update?
Kevin
Hi Kevin,
updated CMSIS drivers for Freescale Kinetis K20 are currently not planned.