Error on debug after repeated debugging sessions "Failed to execute MI command: monitor reset core"

[Tobe]

Hi,

i never had to much trouble with errors while debugging. But its getting exessive.

It only happens, when i debug a session, after i had already debugged a session. It makes no difference, if i manually terminate the last session before. I already tried different reset methods, which seemed to have no effect either.

It only applies to starting the debug session with the "bug" button (which would include the rebuild).

Sometimes i have to restart the IDE to make it work again.

I never had such problems before, and i did not really change much with the settings.

This issue is not present, when using a Nucleo board, but there is another issue (hard fault on debug only).

I am using this: https://www.st.com/en/development-tools/stlink-v3mods.html

Bought from reichelt.de

[Imen.D]

Hello @Tobe ,

Did you try to update and use the latest ST-LINK driver?

Are you using an old Windows version?  CubeIDE is only supported Windows 10 and 11. So, if you are using an old Windows version this might affect the IDE functionality.

[Tobe]

I am using not the most updated drivers/IDE. But i cant remember it working that bad before, so i think there might be some setting that cause this problem. Or even some state when debugging?

[Andrew Neil]

---

@Tobe wrote:

This issue is not present, when using a Nucleo board

---

So what board are you using ?

How to write your question to maximize your chances to find a solution

[SofLit]

---

@Andrew Neil wrote:
So what board are you using ?

---

Indeed.

[Tobe]

Its a custom made PCB.

It works without issue on the first debug session. Where could there be the problem?

[Andrew Neil]

---

@Tobe wrote:

Its a custom made PCB.

---

So give full details - schematic, etc - as noted in the link.