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
I've been using uv4 since it's formal release with our STR9 project.
Not noticed any problems like those described here.
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?
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.
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" .
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
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
View all questions in Keil forum