• State Suggested Answer
  • Locked Locked
  • Replies 24 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 17872 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

Introducing a Python wrapper for CMSIS-DSP with biquads

Christopher Seidl
Arm Employee Badge

My colleagues from the Arm Digital Signal Processing (DSP) software team have introduced a Python wrapper for the CMSIS-DSP library that is compatible with NumPy. The CMSIS-DSP library is a rich collection of DSP functions that Arm has optimized for the various Arm Cortex-M processors. CMSIS-DSP is widely used in the industry, and also enables optimized C code generation from various third-party tools.

Please read their blog here: https://developer.arm.com/architectures/instruction-sets/dsp-extensions/dsp-for-cortex-m/how-to-use-the-python-wrapper-for-csmsis-dsp-with-biquads-as-an-example

Parents
  • 0 Arm Employee Badge in reply to LiseL

    Hello Lise,

    I was able to find a colleague with a Mac. He reported the following:

    "I did a quick test and the installation succeeded. I am using Python 3.7.0 on macOS Catalina 10.15. Couple of notes about macOS-specific changes to the README:

    • To activate the environment, I had to do "source env/bin/activate" instead of running "env\Scripts\activate" directly.
    • I was using "python3 -m pip" instead of just "pip", to make sure that the correct Python installation is used. Sometimes, on systems where both Python3 and Python2 are installed, just "pip" isn't obvious as to which version is being used."

    Hope this helps.

    Christopher

Reply
  • 0 Arm Employee Badge in reply to LiseL

    Hello Lise,

    I was able to find a colleague with a Mac. He reported the following:

    "I did a quick test and the installation succeeded. I am using Python 3.7.0 on macOS Catalina 10.15. Couple of notes about macOS-specific changes to the README:

    • To activate the environment, I had to do "source env/bin/activate" instead of running "env\Scripts\activate" directly.
    • I was using "python3 -m pip" instead of just "pip", to make sure that the correct Python installation is used. Sometimes, on systems where both Python3 and Python2 are installed, just "pip" isn't obvious as to which version is being used."

    Hope this helps.

    Christopher

Children