2025-05-27 2:55 PM
I am setting up my first m55 STM32 project using the NUCLEO-N657X0 dev board with the CMSIS DSP libraries. I have copied the CMSIS DSP libraries into my project and I have added the CMSIS-DSP include paths into my project, but I am receiving the following build error message,
arm_vec_fft.h: error: incompatible types when assigning to type 'uint32x4_t' from type 'int32x4_t'
Can you please provide a recommendation to resolve this error?
Thank you.
2025-05-27 4:07 PM
Did you follow How to integrate CMSIS-DSP libraries on a STM32 project ?
2025-05-27 4:23 PM
I believe I have followed the instructions per the link provided. My project will be using additional CMSIS-DSP library calls, so I have included them as well in CMSIS_DSP/Source.
I have successfully used CMSIS-DSP in my STM32 projects for the m0+, m4, m33, and m7 cores. This issue arose when I tried to build my first CMSIS-DSP libraries for the m55 with Helium vector support.
Is there an example of using the CMSIS-DSP with a Helium supported core?
2025-05-28 2:52 AM - edited 2025-05-28 2:52 AM
Hello @kag_embedded;
Make sure that you’re added the following flag -flax-vector-conversions in Project → Properties → C/C++ Build → Settings → MCU/MPU GCC Compiler → Miscellaneous → "Other flags" as mentioned here.
Thank you.
Kaouthar
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.
2025-05-28 3:25 PM
@KDJEM.1 Thank you for the recommendation of the -flax-vector-conversion flag. It has enabled me to get further into the project build process, but I am still having errors in the build of the CMSIS functions. It appears that the .c files are being built twice, and during the second build, it fails due to "multiple definitions." I have not had this issue on my previous CMSIS projects using m0+, m4, or m33. The path for both definitions appear to be identical.
Can you please recommendation a solution? Thank you.
solution?