EmBitz
How multi core - Newb questions - Printable Version

+- EmBitz (https://www.embitz.org/forum)
+-- Forum: IDE (https://www.embitz.org/forum/forum-1.html)
+--- Forum: Using EmBitz (https://www.embitz.org/forum/forum-2.html)
+--- Thread: How multi core - Newb questions (/thread-234.html)

How multi core - Newb questions - suryaiyer13 - 25-11-2025

I have managed to create new project from scratch for stm32h7, got both of them working. Now i want to setup simultaneous debugging for both cores. Please guide me in setting up the CM4 project to debug and how to do simultaneous debugging?

RE: Newb questions - embitz - 26-11-2025

  • Launch EBlink either from the context menu or via CLI. Note that it will start two GDB server instances on different ports (e.g., 2331 and 2332).
  • Launch EmBitz for the CM7 core and configure Remote Debugging to "localhost" on port 2331. Make sure to add "reset" under Reset → Remote Commands.
  • Launch another instance of EmBitz for the CM4 core and configure Remote Debugging to "localhost" on port 2332, again adding "reset" under Reset → Remote Commands.
  • You can now debug the two cores independently, as if they were separate MCUs.
  • If necessary, configure a trigger cell to reset both cores simultaneously (come back if you need help with this) or add extra reset commands in the reset script hook.

Note: I usually run it without synchronizing resets.


Example: https://www.embitz.org/downloads/stm32h7-dual-core-inter-cpu-async-communication-master.zip

   

RE: Newb questions - suryaiyer13 - 26-11-2025

(26-11-2025, 10:45 AM)embitz Wrote:
  • Launch EBlink either from the context menu or via CLI. Note that it will start two GDB server instances on different ports (e.g., 2331 and 2332).
  • Launch EmBitz for the CM7 core and configure Remote Debugging to "localhost" on port 2331. Make sure to add "reset" under Reset → Remote Commands.
  • Launch another instance of EmBitz for the CM4 core and configure Remote Debugging to "localhost" on port 2332, again adding "reset" under Reset → Remote Commands.
  • You can now debug the two cores independently, as if they were separate MCUs.
  • If necessary, configure a trigger cell to reset both cores simultaneously (come back if you need help with this) or add extra reset commands in the reset script hook.

Note: I usually run it without synchronizing resets.


Example: https://www.embitz.org/downloads/stm32h7-dual-core-inter-cpu-async-communication-master.zip
Thank you admin for this guide, exactly what i wanted.  Big Grin Big Grin Big Grin