Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cortex-R support #314

Open
apullin opened this issue Feb 4, 2018 · 9 comments
Open

Cortex-R support #314

apullin opened this issue Feb 4, 2018 · 9 comments
Assignees

Comments

@apullin
Copy link

apullin commented Feb 4, 2018

It appears there is no Cortex-R build support. Parts are on the market now. Is CR4 support planned?

@JonatanAntoni
Copy link
Member

Hi @apullin,

currently we do not have support for Cortex-R class. Adding support for it mainly depends on market pull. Do you have requirements you'd like to share? What would you expect CMSIS for Cortex-R delivers?

Thanks,
Jonatan

@apullin
Copy link
Author

apullin commented Feb 8, 2018

I am presently using a CM4 + CMSIS-DSP to do audio processing. The application is for calculating A-weighted SPL/noise, but many more solutions are on the table, e.g. if big IoT providers and Sensory/chip vendors/etc make trigger-word IP available.

Some CR4 parts are coming on the market in the IoT space, and I am considering options that use those cores. For example, Samsung now ships an "Artik" module that has a CR4 core as an intermediate solution before stepping up to a full Cortex-A Linux platform.

@JonatanAntoni
Copy link
Member

Hi @apullin,

Thanks for your insights to your application ideas based on CMSIS, that's very beneficial.
In other words you would like to see CMSIS-DSP to be available for Cortex-R4? Hence CMSIS-Core needs to be available as well. What about RTOS (RTX5)?

Would you be able and willing to contribute on this area? I.e. as a first step we would need to have a draft for CMSIS-Core(R) and some startup code for Cortex-R4.

Thanks,
Jonatan

@apullin
Copy link
Author

apullin commented Feb 11, 2018

That is beyond my technical abilities for now. It would be fun to explore it, but there's a lot I don't know there. I have been able to use the prebuilt CMSIS-DSP libraries on M4 just by dropping in the .a and .h files, and not having to go into the low levels of dealing with different programming models, exception models, etc.

But I will definitely contribute anything I come up with.

@JonatanAntoni
Copy link
Member

Hi @apullin,

I appreciate your collaboration. Let's keep this requirement on the backlog.

Please let us know about your questions when you start exploration. You'd be fine adopting CMSIS-Core and system startup code for Cortex-R in the first place.

Thanks,
Jonatan

@BabaJaguska
Copy link

CMSIS-NN would come in handy on Cortex-R too.

@alfedotov
Copy link

I had an attemt to upsteram Core-R about year ago with no luck. But I still see demand.
I have created new pull request there #945
Please support me if you are interested :)

@alfedotov
Copy link

@JonatanAntoni May be it worth to create new "future" branch (from devel) if you can't accept these changes on "devel" branch.
Seems to me it would be more beneficial to have such changes in one central repo instead of searching over github

@tomoveu
Copy link

tomoveu commented Jun 6, 2022

@JonatanAntoni from the CMSIS NN documentation it is implied that we could build without M-Profile Vector Extensions.

please see below this quote straight from the documentation

Each library project have different pre-processor macros.

ARM_MATH_DSP:
Define macro ARM_MATH_DSP, If the silicon supports DSP instructions(DSP extension).

ARM_MATH_MVEI:
Define macro ARM_MATH_MVEI, If the silicon supports M-Profile Vector Extension.

@alfedotov thank you for sharing this, I will take a closer look. There is definitely a demand for ML applications on Cortex-R

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants