Topic : STM32F4xx: Compiler uses -mcpu=cortex-m3 instead of cortex-m4

Forum : ARM

Original Post
Post Information Post
April 18, 2013 - 1:42pm
Guest

Hello,

is this a bug in Ride7?

Although I choose an Cortex M4 device (e.g. STM32F4xxxG) in the project settings, Ride7 executes the GCC-compiler with the option

Replies
Post Information Post
+1
-1
-1
April 19, 2013 - 3:15pm
Raisonance Support Team

Hello,

The cortex M4 has the same characteristic as the M3 but with more specificity. read the GCC compiler documentation.
To use as Cortex M3 you can specify in:
GCC compiler -> ARM Specific Options -> FPU type -> Hard EABI

From the build log window in the compiler you will find:
-mcpu=cortex-m3 -mfpu=fpv4
means for compatibility with older versions of GCC

regards,

+1
0
-1
April 18, 2013 - 1:55pm
Guest

..."-mcpu cortex-m3". I encountered this issue, when I tried using the CMSIS DSP-library. Work-around is: - In ..\Ride\Config\ARM\ARM.config change Line 169 to targetstr= "-mcpu=cortex-m4"; has_fpu =1; However, Ride will certainly now compile EVERYTHING for Cortex M4 devices expecting an FPU.

+1
0
-1
April 18, 2013 - 2:08pm
Raisonance Support Team

hello,
Your message is snipped, can you post it again.

regards,

+1
0
-1
April 18, 2013 - 2:53pm
Guest

Hello, is this a bug in Ride7? Although I choose an Cortex M4 device (e.g. STM32F4xxxG) in the project settings, Ride7 executes the GCC-compiler with the option "-mcpu cortex-m3". I encountered this issue, when I tried using the CMSIS DSP-library.

Work-around is: In ..\Ride\Config\ARM\ARM.config change Line 169 to targetstr= "-mcpu=cortex-m4"; has_fpu =1; However, Ride will certainly now compile EVERYTHING for Cortex M4 devices expecting an FPU.

best regards