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

tables/function placement macros/options #45

Open
ehughes opened this issue Sep 13, 2022 · 1 comment
Open

tables/function placement macros/options #45

ehughes opened this issue Sep 13, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@ehughes
Copy link

ehughes commented Sep 13, 2022

On Cortex M7 targets such the i.MXRT10xx family, it is important to be able to control memory placement of the functions/tables for best performance. For example, the default placement of functions and twiddle tables into the QSPI flash region. IN previous versions of the CMSIS DSP, I would keep a local copy of the source in my repo and "patch" functions and tables like this:

FAST_DATA_RAM const q15_t ALIGN4 realCoefAQ15[8192] = {
    (q15_t)0x4000, (q15_t)0xc000, (q15_t)0x3ff3, (q15_t)0xc000, (q15_t)0x3fe7, (q15_t)0xc000, (q15_t)0x3fda, (q15_t)0xc000,
 .
.
.

FAST_DATA_RAM would be defined elsewhere so I easily place the table in DTCM, etc.

It would be beneficial for the library to have some mechanism for specifying placement of the routines & tables. I am migrating to the latest version of CMSIS DSP with the cmake build flow and would like to minimize how much manually modify the library.

@christophe0606 christophe0606 added the enhancement New feature or request label Sep 14, 2022
@christophe0606
Copy link
Contributor

@ehughes It is a very good idea. I'll definitely add such a feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants