• 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 in reply to Johannes Bauer

    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.

    Regards,

    Marco

Reply
  • 0 in reply to Johannes Bauer

    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.

    Regards,

    Marco

Children
  • 0 Arm Employee Badge in reply to Marco

    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,

    Johannes

  • 0 in reply to Marco

    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