AnsweredAssumed Answered

STM32F7 debugging (stepping) impossible, IDE jumps into interrupts

Question asked by steinkamp.matthias on Jun 21, 2016
Latest reply on Jun 28, 2016 by nafikov.renat
Hi there,

I want to port my graphics application from the F4 discovery to the F7 (see setup below).

However I discovered that debugging is impossible because every time I want to step over a line of code, occuring interrupts are handled first. With the F4 they were handled in the background and the eclipse did not jump into the IRQHandler. On the F7 it directly jumps into the IRQHandler and step-out won't help. This is really inconvenient for a serious development. I also got this problem with my original toolchain (simple eclipse cdt with arm gnu plugin). The systick interrupt does not interfere with debugging the "main". Why is that?

What is the difference to the STM32F4? Does the GDB need to handle the breakpoints differently? Is the STM32F7 hardware (Cortex, NVIC, IRQ priorities) different regarding debugging? I don't know where to start?

Thanks for any help!!

Best regards,
Matthias

My setup:
STM32F7 discovery kit
Ac6 System Workbench for STM32
STM32Cube_FW_F7_V1.3.0\Projects\STM32746G-Discovery\Applications\STemWin\STemWin_HelloWorld

Outcomes