You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @MaJerle ,
I would like to port a project to vcode from a STM32H745 (dual core M7 and M4). I am kinda of vscode fan
I have been looking now for some time, I read that it should be possible to debug both cores with the https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug extension. But so far no example on-line.
Do you believe with you method would be possible to make it work for a dual core system?
Did you came further with the python script for dual cores ?
My Project works fine under STM32CubeIDE for both cores (can flash and debug without much hassle).
The text was updated successfully, but these errors were encountered:
I did not work for dual-core as script is meant for simple porting.
Dual core project has to be compiled twice, once for each core. You can do it with single or dual cmakelists.txt file. I have never tested the dual-core tho.
I took a look in the debug widget for dual-core. It says that every core has its own instance of debug interface. If you use ST-Link and STLINK-Server for debugging, then make sure you use the shared option. To allow multiple processes connecting to same instance of ST-Link for both cores.
I cannot verify if it works well but that's an option to consider.
Hi @MaJerle ,
I would like to port a project to vcode from a STM32H745 (dual core M7 and M4). I am kinda of vscode fan
I have been looking now for some time, I read that it should be possible to debug both cores with the https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug extension. But so far no example on-line.
Do you believe with you method would be possible to make it work for a dual core system?
Did you came further with the python script for dual cores ?
My Project works fine under STM32CubeIDE for both cores (can flash and debug without much hassle).
The text was updated successfully, but these errors were encountered: