The Arm Cortex-M7 processor is the most recent and highest performance member of the versatile Cortex-M processor family. The Cortex-M7 processor is code compatible with other Cortex-M devices and uses the same exception model for interrupt handling. However, there some areas to consider when migrating from a Cortex-M3 or Cortex-M4 to a Cortex-M7 based device.
Previously we ran a series of webinars to help you get started with Cortex-M7 devices. The first webinar introduced the Cortex-M7 architecture and its advantages and the second and third focused on the devices available from our silicon partners Atmel (the SAM V71 Xplained Ultra board) and STMicroelectronics (the STM32F7 Discovery board). The webinars contained live demos on how to connect to the hardware and how to create your first application using MDK Version 5.
Missed the webinars? Watch them here!
Visit keil.com for more information about Arm Cortex-M7 software development support.
Got a question? Ask our speakers in the comments section below!
I have been doing development on the ST F7 Discovery board. It is a very nice platform with a good size full color touch screen display and of course the F7 microcontroller. The issue is that the interrupt handling mechanism of the F7 is different from the previous ARM M cores (perhaps due to the SuperScalar instruction issue?) in that when interrupts are occurring, single stepping keeps trapping into interrupt handler routines rather than proceeding to a next line as one would expect. The only work-around is to continuously use the "Run to cursor" command to execute and break at the next line in the routine you want to debug. Otherwise you are in interrupt handler purgatory. Is there any plan to address this issue?
I am using the SW4STM32 Eclipse toolchain but I understand the issue occurs with the Keil tools as well.