2022-10-09 08:02 AM
Since STM32H7 package include old CMSIS DSP library (1.7) and new DSP feature are included in new version (1.10), I want to know how to include the 1.10 CMSIS DSP library exists in github without conflict to stm32cubeIDE CMSIS core and other module's which are not update and are not availible through STM32cubeMX package manager for updating them? (This is fishing)
Also I have another question: Could we have hope for ST to update STM32H7's cube package to upgrade it's CMSIS library module, specially it's DSP? (This is fish)
I want to have fish and fishing manual at the same time.😁
STM32cube ecosystem is best ever though it have some little deficiency but this is really best ever made, Thank you STguys so much.
Solved! Go to Solution.
2022-10-10 08:19 AM
I got the answer that there is no plan to support new CMSIS version at short term.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2022-10-09 10:27 AM
I'd tend to use a file manager, rename the old directory, and unpack or copy in the new one
Lot of old cruft in the packages,especially middleware like FatFs
Constantly churning all the pieces can break backward compatibility, and a lot of QA and testing. I'd generally prefer the robustness of ST's code be the primary focus.
Most of us are perhaps not dependent on what ST chooses to do
2022-10-09 10:47 PM
I'm thinking like you that robustness is the best. But STM32H7 is most powerfull device series on DSP, They can upgrade it's DSP library themself or give us a solution on how to upgrade it with our own risk on campatibility. And some tips to evade incompatibilities. I mean they can surrend it and it consequenses to us.
Also have you ever seen keil uvision package manager? You can see all packages including CMSIS and you can manage their conflicts and their version. Then this can be handled in STM32cubeMX too. Though maybe the main reason for not implementing CMSIS package manager is that the HAL CMSIS version conflict. Though I think it must be so easy since we have only two folder in CMSIS subfolders, The device and the general CMSIS includes.
2022-10-10 02:14 AM
Hello @SeyyedMohammad
Your request is tracked internally, and we will get back to you soon.
About upgrading feature of CMSIS package in CubeMX, I let @Semer CHERNI to comment on this.
Internal ticket number: 135563 (This is an internal tracking number and is not accessible or usable by customers).
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2022-10-10 08:19 AM
I got the answer that there is no plan to support new CMSIS version at short term.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2022-10-12 05:25 AM
Hi @F.Belaid
Thank you so much but could you ask if they can provide manual procedure to upgrade CMSIS DSP component?
2022-10-14 01:22 AM
Hello @SeyyedMohammad ,
Check this article for integrating DSP libraries.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2022-10-14 06:23 AM
Hello @F.Belaid
Thats really perfect but tells how to just add current library included in the HAL, not the latest availible in the net. since maybe that requires to also update the core cmisis in the cubeIDE. It means also we need to know that.