You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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.
The text was updated successfully, but these errors were encountered:
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 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.
The text was updated successfully, but these errors were encountered: