I seem to be having the same issue as someone in this thread:
http://www.keil.com/forum/15652/
I had it before and got it to go away, I'm not sure how...
Now nothing I do works, I cant debug at all...
I can still see the disassembly and step through that, but that isn't that useful when debugging data structures etc.
Does anyone have any clue what could cause this?
It happens when simulating or debugging on chip (STM32F4xx)
I tried deleting all output files and regenerating as well as everything listed in the above thread.
No errors are printed at all.
Any help would be appreciated
You'd need to select a few peripherals in STM32CUBEMX, generate the code (simply generates startup code), set the processor to STM32F429II (though it happens no matter what processor is selected). Then try to debug with either the simulator or the debugger, my debugger is the ST-Link (I'm currently using the Disco board). It seemed to happen out of nowhere without changing a setting, very strange. I think other projects still work in the debugger so it is something isolated to this project somehow...thanks!
And are you using uVision 3 like the thread you cited, or something of more recent vintage? If so, what.
I've made progress!!! It seems that this only happens on my PC, which is a mac running windows in parallels...
I just installed uvision on my partner's regualar windows PC and I can step thorugh C code, but now it breaks on every statement even if there isn't a breakpiont there, any reason this could happen?
OK, I've narrowed it down...
When I compile on the mac (running parallels) it doesnt work in debug
When I compile on a standard PC, the the debug works on any computer.
This has to do with how the parallels mac outputs the debug information.
Any Ideas? It'd be a real pain to have to have my partner compile for me every time...
Have you compared all log output from a full build on your machine and the PC?
Same parameters? Same versions of binaries? No strange path used by your machine like possibly a name with space in it?