uVision4 Beta 3 Bugs

 uVision4 Beta 3 Bugs

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

 RE: uVision4 Beta 3 Bugs

Jan;
I have not seen this particular problem. What version of MDK are you running?
Have you reported this bug to Keil Support?
They will need full info of your toolset and your computer enviornment.
Remember that Keil does not check this forum on a regular basis.
Bradford

 RE: uVision4 Beta 3 Bugs

Hello Bradford,
I am using the following toolchain:
IDE-Version:
µVision V4.00 Beta 3.1
Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2009

Tool Version Numbers:
Toolchain: RealView MDK-ARM: x user Version: 3.80a
Toolchain Path: BIN40\
C Compiler: Armcc.Exe V4.0.0.524
Assembler: Armasm.Exe V4.0.0.524
Linker/Locator: ArmLink.Exe V4.0.0.524
Librarian: ArmAr.Exe V4.0.0.524
Hex Converter: FromElf.Exe V4.0.0.524
CPU DLL: SARMCM3.DLL V3.80a
Dialog DLL: DARMSTM.DLL V1.43
Target DLL: BIN\UL2CM3.DLL V1.50
Dialog DLL: TARMSTM.DLL V1.43

I am contacting the technical support. I tried to gather as much informations as possible first.
Best regards!
Jan

 RE: uVision4 Beta 3 Bugs

Greetings all,

I can confirm the same problem.
Installed the MDK-ARM V4.01 update, and in uVision4,
it's impossible to begin a debug session.
The IDE (uVision4) completely freezes,
windoze wants to send a bug report (no, thanks..).

Switched back to uVision3 for the time being: No problem there, repeatedly.

Target: LPC2478 with an own hardware,
using both the LPC's internal FLASH, plus external FLASH.
Debugger: uLink2 .

While downloading the code into FLASH (via uLink2), it's advisable NOT to switch the focus away from the uVision main window because the window seems to freeze (it doesn't, it just stops to update the progress bar). But this was a minor error which also existed in uVision3; the FLASH download completes some time later and the main window gets alive again.
Not so with the debugger - the uVision4 window freezes, and doesn't return no matter how long I wait.

Cheers, Wolfgang "Wolf" .

 RE: uVision4 Beta 3 Bugs

There is actually an issue when downloading to flash (which exists with UV3 too, but is less likely to happen). On Windows XP (and newer) Windows itself sometimes marks the uVision window as "Not responding", if you click on it while the flash download is in progress. This does not affect the download itself, but does bring up a dialog that asks to close the "not responding" application.
If you ignore that the download will just finish and the debugger should run normal.
Is this the issue you describe?

 RE: uVision4 Beta 3 Bugs

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.

 RE: uVision4 Beta 3 Bugs

I've been using uv4 since it's formal release with our STR9 project.

Not noticed any problems like those described here.

 RE: uVision4 Beta 3 Bugs

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.

 RE: uVision4 Beta 3 Bugs

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

 RE: uVision4 Beta 3 Bugs

Oh should have said my project is based on an STR9

Stuart

 RE: uVision4 Beta 3 Bugs

Jan,
is your ULINK2 connected to the PC directly or via a USB hub?

 RE: uVision4 Beta 3 Bugs

I have tried the Unlink2 connected directly to the PC and via a USB hub, and both problems occur both ways.

Stuart

 RE: uVision4 Beta 3 Bugs

"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!

 RE: uVision4 Beta 3 Bugs

Hi Matthias,
I have the ULink 2 directly connected to the PC.
I have not experienced this problem with uVision 3.

Best regards!
Jan

 RE: uVision4 Beta 3 Bugs

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.

 RE: uVision4 Beta 3 Bugs

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.

Best regards!
Jan

 RE: uVision4 Beta 3 Bugs

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 .

 RE: uVision4 Beta 3 Bugs

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

 RE: uVision4 Beta 3 Bugs

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?

 RE: uVision4 Beta 3 Bugs

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

 RE: uVision4 Beta 3 Bugs

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

 RE: uVision4 Beta 3 Bugs

Hello forum,
I just got an update Version of uVision 4 and tested it on my computer. The behaviour has improved and the huge freeze times seem to have vanished so far (I will go on testing though).
I got this update from Mr. Zaech from Keil support. You might want to drop him a message to test this version on your machines as well(KeilSupportIntl@arm.com).

Best regards
Jan

 RE: uVision4 Beta 3 Bugs

Jan,

I obtained and applied the update (UV4.03) from Keil but I am still experiencing the same problem. Entering the UV4 debug session still takes maybe 30 seconds.

So I still cant use this until this is resolved.

Thanks anyway,

Stuart.

 RE: uVision4 Beta 3 Bugs

Stuart,
sadly that doesn't sound well!
I must say that the version 4.3 did not fix every problem here. It feels smoother for me though.
So I think Keil fixed a few but not all problems with starting debug sessions.

I will keep you informed if about any news I get and hope you guys do likewise :)

Best regards!
Jan

 RE: uVision4 Beta 3 Bugs

Just to let everyone know.
Keil have now fixed my problem with UV4 delays in going into debug with an updated version - mkd402ao

Stuart.

 RE: uVision4 Beta 3 Bugs

Stuart,

When can we expect it to hit the market...?

 RE: uVision4 Beta 3 Bugs

Dear All,

a new release will be available in December 2009 which address this issue.

BR
Alex

 RE: uVision4 Beta 3 Bugs

Nice one! I am looking forward to that version and am curious about the improvements!

Greetings
Jan

 RE: uVision4.02 Bugs

MDK402.exe still contains the debug hang-up problem :-(

After the debug starts, I have to wait several minutes before I can start with the debugger...

 RE: uVision4.02 Bugs

Yes I can confirm this behaviour after several hours of intense usage of uVision 4.02.

I switched back to 3.x weeks ago since uVision 4.x is unuseable.

 RE: uVision4.02 Bugs

I installed MDK 4.03 (=4.02i) which comes along uv4 4.00r. I did not use it too much yet, but it looks good to me.

 RE: uVision4.02 Bugs

Sounds good.
I am gonna try that in the afternoon.

Best regards
Jan

 RE: uVision4.03 no Bugs

MDK 4.03 with the ULINK2 firmware update works fine :-)

 RE: uVision4.03 no Bugs

That sounds interesting.
Is there a dedicated firmware update for the uLink2 Device?
If so... how do I download the firmware upgrade onto the uLink2 device?

Best regards
Jan

 uVision4.03 no Debug Bug

The firmware update starts at the first use of the ULINK2 after the installation of MDK403.exe

 RE: uVision4.03 no Debug Bug

Uhh okay! I will try that in the afternoon then.
When it's useable I can finally switch to uVision 4.

 RE: uVision4.03 no Debug Bug

A much better IDE with a lot of new features :-)