Updated to 4.21 last night checked it still compiled the current project which it does however this morning I need to debug on the target like I have been forever but everytime its about to switch over to the debug enviroment (i.e after the download+verifiy) in the IDE boom "uVision Ide has stopped working":
Problem Event Name: BEX Application Name: Uv4.exe Application Version: 4.21.0.0 Application Timestamp: 4dfb62ad Fault Module Name: StackHash_4c4a Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 00000000 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 2057 Additional Information 1: 4c4a Additional Information 2: 4c4ad7529a34983b6293625c48169922 Additional Information 3: 4c4a Additional Information 4: 4c4ad7529a34983b6293625c48169922
It was working fine on 4.20. Windows 7 Ultimate 64Bit, 8Gb Ram
anyone got any ideas other than step back to 4.20?
Same issue here. Debugging appears to be broken...RAM variables don't update. Memory window isn't correct.
Any solution other than to roll back?
Hi
I had the same issue with local RAM variables posted at:
http://www.keil.com/forum/19127/
I also reported this issue to the keil support team. They worked last week on it, but couldn't solve/reproduce it yet. I'll keep you informed if there are some news. I aslo rolled back to V4.20
Regards Raphael
Anybody hear if there is a fix in the works?
I've been sent a patch for my issue, I think you will have to approach Keil support directly
In the meantime there is a patch available from the Keil support team, which will solve this issue.
Hi,
you can always roll back if you have a look at the
c:\keil\Backup.xxx
folder.
BR, /th.
Whilst my original problem was solved via a patch I now find I variables local and otherwise are garbbage when viewed in the watch window, I've reverted to 4.20 for now until the next release which I hope gets tested better.
I would strongly suggest if your project is working and you don't have time to debug the the IDE etc don't load 4.21.
I noticed the same weirdness. I reverted to 4.20. Hopefully they will sort out the issues that grossly broke debugging
View all questions in Keil forum