Hello all,
I am using the MDK-Arm Version 5.24a (July 2017) on a Windows 10 Virtual Machine, and whenever I try to go into the debugger (for the second time) the program becomes not responding. The debugger works fine for the first time, it goes into the not responding state when I try the debugger for the second time in the same project. I can only use the debugger again when I restart the program but again it only allows me to use it for one time.
Thanks
Are we talking about the embedded "program", or the Keil uVision application here?
Which target board, debug adapter ?
What error do you see when you try to debug 2nd time ?
Sorry, yes, I meant the application uVision.
I do not see any specific warning - it just doesn't respond and later on crashes.
You didn't answer those.
If it's a 3rd-party debug adaptor, try the 3rd party's own utilities to establish whether it's a problem with the adaptor and/or target, or with Keil ...
Can you tell me where I can check those specifics so that I can let you know? Also I am not using an external 3rd party debugger. It's the simulation
I am having the same issue. I have Keil version MDK lite 4.74 , windows 10 It allows debug once, than I hope out to editor mode and again rebuild target, after that when I am clicking debugger option second time to debug, the keil software stop responding. Windows come with pop up -program Stop responding, wait for program or close program.