STM32H7 Dual-Core Debugging: CM4 and CM7 Entry Points overlapping in CubeIDE v2.0.0

[AraceliGuerrero]

Hi everyone,

I'm experiencing a frustrating issue while debugging an STM32H755 using STM32CubeIDE v2.0.0.

When I launch a Launch Group (or start the debug sessions sequentially), the start point (Entry Point) in main often points to the exact same memory address for both the Cortex-M4 and Cortex-M7 cores (e.g., 0x81013be). This overlap obviously prevents a proper debug session.

This behavior seems random. Sometimes it starts correctly, but as I develop and recompile the code, they suddenly end up "stacked" on the same address.

Current Setup:

• IDE: STM32CubeIDE v2.0.0.

• GDB Server: Manually configured with separate ports (61234 and 61240).

• Guidelines: I've followed the official dual-core debugging recommendations.

Is there a specific configuration or "hidden" setting to prevent the IDE from overlapping these entry points? Or is this a known bug in v2.0.0? It’s becoming quite a bottleneck for my development.

Thanks in advance!

[Souhaib MAZHOUD]

Hello @AraceliGuerrero 

I suggest that you follow this application note AN5361 in 3.1.1- Launching the configurations section, that covers the configurations needed to debug STM32H7 Series dual-core in STM32CubeIDE.

BR, Souhaib