2024-01-18 11:46 PM
Hi,
I have been trying to add opus codec in my project. But I cannot able to build after adding the opus file. If anyone successfully added opus with their project help me out. I mostly get errors on 'Neon' which is used for FFT. As I searched neon is for cortex A, but the STM32WB5MMGHTR is cortex M based. I'm also adding my config file code for opus here
#ifndef CONFIG_H
#define CONFIG_H
/* Variable leng arays */
#define VAR_ARRAYS
/* Comment out the next line for floating-point code */
#define FIXED_POINT 1
#define OPUS_BUILD 1
#endif /* CONFIG_H */
Help me to add opus library with my project.
Solved! Go to Solution.
2024-02-07 09:54 PM - edited 2024-02-08 01:17 AM
Hi,
I integrated opus in my project.
Things I did:
1. I opened example project which present inside the "X-CUBE-OPUS.zip" and explored what are the files included from the opus library. To check this I read ".cproject" and ".project" from the example file, then I added those files in my project.
2. After that I checked the compiler options from the project build settings and I made changes in my project compiler options with that.
3. Also, I checked build output for "fpu" based compiler options and set in my project. Opus needs "-mfpu=fpv4-sp-d16" "-mfloat-abi=hard" options to get compiled. (Before adding this option verify your controller has support for FPU).
After all the above changes in my code I got compiled successfully.
Thanks and regards,
Laksh
2024-01-22 05:46 AM
Hi,
I'm having the same problem. Did you find a solution?
2024-01-22 09:01 PM
Hi Cavitcem,
No I couldn't find any solution. May I know what kind of error you are facing exactly.
Thanks & regards
2024-01-22 10:00 PM
Hi LR.2,
My error outputs are like this but I couldn't find a solution.
Thanks & Regards
2024-01-22 10:42 PM
Hi Cavitcem,
Mine is also similar error.
Thanks & Regards
2024-01-23 12:08 AM
Hi LR.2,
If you find the solution, I would be happy if you share it here.
Thanks & Regards
2024-01-23 12:35 AM
Sure Cavitcem. If I made any progress I'll update here.
2024-01-23 01:33 AM
Thank you for having reported this.
I escalated this issue for fix in the internal ticket number 171448.
(PS: Internal ticket number 171448 is not accessible or usable by customers).
2024-01-25 03:24 AM
2024-01-31 02:30 AM