• State Accepted Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 119 subscribers
  • Views 11408 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CMSIS Driver API and Software Packs status

Marco

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

Parents
  • 0 Arm Employee Badge in reply to Vijith

    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

Reply
  • 0 Arm Employee Badge in reply to Vijith

    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

Children