Hello, I've got serious problems with the uVision4 starting a debug session.
1. I hit the debug button in the toolbar. 2. uVision4 starts to upload the programmcode. 3. After successfull upload it says Window Layout in the statusbar and here the trouble start: Sometimes it takes uVision several seconds to get the windows setup. Sometimes it takes way over 30 seconds until uVision4 is ready to debug and sometimes uVision just crashes or freezes.
I must say this is quite an annoying problem with the uVision4 IDE. I like what I've seen so far except this serious problem!
Will this get fixed and is anyone else having similar problems?
Greetings Jan
Sometimes it takes uVision several seconds to get the windows setup. Sometimes it takes way over 30 seconds until uVision4 is ready to debug and sometimes uVision just crashes or freezes.
this is why I'm still working with uv3.
I've been using uv4 since it's formal release with our STR9 project.
Not noticed any problems like those described here.
It might be a Cortex-M3 related problem.
I am using uVision 4.0 and the uLink2 JTAG adapter.
Actually it is quite annoying and I am absolutely not satisfied with uVision 4 in this case.
I have just started to use UV4 via MDK 4.01 and I have both problems.
Sometimes debug in UV4 takes a long time to start, although sometimes its as quick as it is UV3. Initial I thought UV4 had crashed but it just stalls for 30+ seconds. The stalling seems to happen for no apparent reason to me.
I also have the problem with the flash programming. UV3 and UV4 stall and look crashed until program erase/flashing has completed. This has happened to me ever since I upgraded to MDK 3.80. It coincided with an update to our Unlink2 devices caused by the upgrade to MDK 3.80, not sure if this is related?
I think I will have to use UV3 until the first problem is resolved. The second one I can live with but would obviously like fixed.
Stuart
Oh should have said my project is based on an STR9
Jan, is your ULINK2 connected to the PC directly or via a USB hub?
"I've been using uv4 since it's (sic) formal release with our STR9 project."
More care with your punctuation you must take - bad attack of Greengrocer's Apostrophe you have!
I have tried the Unlink2 connected directly to the PC and via a USB hub, and both problems occur both ways.
Hi Matthias, I have the ULink 2 directly connected to the PC. I have not experienced this problem with uVision 3.
Best regards! Jan
This is what I have found.
When debugging for an LH75401 project the debugger returns focus after about 30 seconds but I cannot set or clear any breakpoints (menu selection grayed out).
When I start debugging for our LPC2148 projects the debugger returned focus after 48 minutes. I started the debugger at 3:36 PM, focus finally returned at 4:24 PM. I was able to set and remove breakpoints. I initially thought that UV4 had died but a co-worker suggested that I wait to see if focus ever returned. This is with UV4.01. I imagine that UV4.00 works the same.
Wow! That is a quite serious flaw I must say. I would not have had the patience to wait that long for my debugger to return. Hehe!
What do you guys suggest to do now? I contacted Keil and they wrote that they managed to reproduce the error. But since then I haven't got any answers.
Hello Jan and group,
Simply switch back to uVision3.
If you installed MDK-ARM V4.01 "over" an older version, uVision3 (if you launch it directly) will happily use the new (ARM-) compiler toolchain.
For me, this works: uVision3 (!) reports under "Help".."About" that it uses RealView MDK-ARM V 4.01; the same as uVision4 did, so I guess the code produces by the compiler/linker is exactly the same, regardless of the IDE.
Cheer, Wolf .
Hi Wolf, thanks for the tip! I will switch back to using uVision 3 I think. The current behaviour of uVision 4 is not helpfull right now.
Nevertheless I'd be really interested in Keil getting this fixed. Best regards Jan
It is simply amazing that Keil did release uv4 with these issues present. I mean, can you think of a worse way to antagonize users of an IDE?
Jan, can you provide a project that shows this issue to the Keil Support Team (support.intl@keil.com)? We will be happy to look at the issue if we can reproduce it.
Matthias
Matthias, I've been in contact with your colleague from Keil Support. He told me that they've managed to reproduce the issue we are discussing here.
I just got a version for testing which is supposed to correct the issue. Best regards Jan