Can a target affect or crash Cube IDE via a debugger?
This has been reported by many Cube IDE users.
The most common manifestation is that Cube drops the comms, stating
This can be due to a bad STLINK debug cable, but the weird thing is that it varies according to target software.
I have posted more details here
https://www.eevblog.com/forum/microcontrollers/32f4-can-a-target-crash-or-affect-cube-ide/
Another thing I have found is that the use of the SWV ITM debug console breaks Cube with the above error, sometimes within seconds, but right now I am not using this feature.
The debugger is currently STLINK V3 ISOL but it happens with both STLINK V2 and V3, both ISOL.