Hello All,
I am trying uVision MDK-Lite Version: 5.12.0.0. for first time. My PC is running Windows XP. uVision seems to freeze very frequently when closing down. It must be forced to close and offers to send an error report to Microcoft. On next opening, an information box opens up with following text:
! uVision has not been properly closed due to code completion. Functionality will be deactivated until next start.
I have seached Keil website and Forums for information on these messages but did not find anything.
Thanks in advance for any information or help,
John O'Connor
Another easy and straight forward way to get the code completion of uVision 5 to crash:
If you are inside a function and insert the following code at start of the function:
const static BYTE ab[8]={ 0, 1, 2, 3, 4, 5, 6, 7};
After this the code completion will not work any more and uVision5 will crash on program end.
(I use cpp, STM32F407 with ST-Discovery, uVision 5.12, my PC is running WinXP).
bt and all others,
This is a problem with Windows XP. uVision5 is known to sometimes exhibit this behaviour if installed on a PC running Windows XP. Keil recommend upgrading to a newer version of Windows such as Windows7 or Windows8.
That doesn't seem to compute.
It's more much, much, much more likely to still be a bug with uVision, even if that bug might not trig on Windows 7.
Per,
You may very well be correct, but Windows XP is a "dead" OS now and I doubt if Keil will be very bothered about correcting any bug in uVision to enable us to run with Windows XP. I have the few IDEs, programmers, debuggers, etc I use, all running very OK on Windows XP now for a few years. I just quake in my boots at the thought of upgrading to a new Windows OS......
JO'C
Correct - no new development for XP.
But the post sounded like the issue was with XP when the issue is most probably with uVision or one of the libraries that Keil is designing uVision around.
In this case, it's well known that developers tends to like to keep older machines, just because older machines has better support for older hardware. Remember how people kept their Win95/Win98 machines for a very long time because lots of PROM programmers etc didn't work with Win2k.
Two important things. 1) Bugs are "easy" when they can be reproduced. 2) Products that are vital to the organization (uVision is for Keil) should be designed in a way where there is access to all source code just to allow bugs to be fixed without need for external support.
So it should be quite easy/cheap to take a look at the issue and release a fix. And if Keil does not have all required source code, then it's time to take two steps back and consider risk factors.
Try to disable "Dynamic syntax checking" in Configuration->Text completion tab. I have disabled this feature and my Keil is not freeze now
Yes of course - then it will be fine.
Just this "Dynamic syntax checking" is so terrificly nice. With V4.74 it works, so I still use V4.74.
PS: I am quite sure that I already tested it also on a Win7 some months ago, and there I had the same problems with V7. Therefore I cannot believe that it is due to the operating system.
I have a same problem with uVision 5.15. I'm working on Windows XP SP3. Very frequently when closing ARM-project, uVision IDE just hang and to do something next it's need to kill uVision process from task manager. But this is not the end. It's just the beginning. I found similar another problem. I have simple ARM-project. If I try to complicate project, for example, make one more output target, using #ifdef #else #endif syntax and creating this target in Manage Project Items dialog, then when I try to save project, then close project and uVision and open project again. At this moment uVision crashes with message box "uVision IDE has encountered a problem and needs to close. We are sorry for the inconvenience If you were in the middle of something, the information you were working on might be lost. For more information about this error, click here"
If I click the link "click here", I see next information. AppName: uv4.exe AppVer:5.15.0.0 ModName: unknown Modver: 0.0.0.0 Offset c737594e To view technical information about the error report, click here
Link "click here" show me next info: Exception information Code: 0xc0000005 Flags: 0x00000000 Record: 0x0000000000000000 Address: 0xffffffffc737594e ................ and so on
Can anyone something tell or help?