Even in the latest release uv4 crashes constantly, it seems to me none of the problems report directly to Keil or via this forum have been resolved.
3 machines, ulink2 and ulink me, 3 different targets all with one common link, uv4.
Only in desktop software could you get away with this...
It stinks.
I am looking forward to the next update. I am not using the uv4 suppulied with MDK 4.01 (but rather uv3) - it is slow, crashes often, unhandy. Simply amazing Keil even released it (what was the rush?). my advise: wait...
I've started using Keil 3 month ago and, befor, i used to debug with TRACE32 IDE and lauterbach emulator :(
We need another debugger to debug this keil
DO NOT HIJACK THREADS, START A NEW THREAD WHEN NEW SUBJECT
I've started using Keil 3 month ago and, befor, i used to debug with TRACE32 IDE and lauterbach emulator
no, you don't
Erik
The debugger is fine in when working its just the crashing that is not good.
Hi,
Can you give specific examples so that we can reproduce the crashes?
BR, /th.
using an LPC24xx, switch to debugging mode. after the object code is loaded, there are delays, occasional crashes, the whole smack...
If you modify source file(s) whilst the target is running, then attempt to stop the target in order to build, more often than not it will crash. On occasion the the taget will stop but the screen remain in debug mode, but you can build using F7, it then normally crashes.