Using MCU = cortex-m7
Posted: Wed Jun 22, 2016 11:20 am
Using MCU = cortex-m7 with GCC 4.9 causes an _unhandled_exception, at least when using the USB driver. (for example in STM32F7xx/USB_CDC project). With GCC 5.3 it seems to be stable. According to the changelogs support for Cortex-M7 was added in 4.9, while Cortex-M7 performance tuning was added in 5.0, so it probably makes sense.
I didn't do performance tests yet, but theoretically it makes sense to have the compiler optimize for cortex-m7 with all the differences in execution.
Does anyone have experience with the Cortex-M7 performance tuning of GCC? (-mcpu=cortex-m7 option which is set by MCU variable)
I guess the default in the ChibiOS STM32F7 projects is kept at MCU = cortex-m4 for compatibility reasons?
I didn't do performance tests yet, but theoretically it makes sense to have the compiler optimize for cortex-m7 with all the differences in execution.
Does anyone have experience with the Cortex-M7 performance tuning of GCC? (-mcpu=cortex-m7 option which is set by MCU variable)
I guess the default in the ChibiOS STM32F7 projects is kept at MCU = cortex-m4 for compatibility reasons?