We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi,
The following problem renders the uV4 Bete IDE unusable for downloading and debugging an application with my setup.
Note that I have installed the uV4 Beta under the same folder where the toolchain is installed, as recommended.
I would be grateful for any information regarding this bug, especially any about workarounds.
Thanks.
Steps to reproduce:
1. Open a working project (formerly configured for debugging and flash download with ULINK under uV3).
2. Build the project.
3. Connect the ULINK to the computer and the target.
4. Press the LOAD button on the toolbar in order to download the application to FLASH memory.
Result:
1. An error dialog with the followong message pops up:
"Error: Flash Download failed - This old version of 'S166.DLL' is incompatible with uVision (UV3.EXE).
Please use a consistent installation!"
2. After acknowledging the message by clicking 'OK', the dialog is closed, and the application cannot be downloaded ito FLASH.
Current setup:
System: Windows XP Professional, SP2
ULINK: S/N U1948C7E
IDE-Version: µVision V4.00 Beta 1 Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2009
License Information: (hidden)
Tool Version Numbers: Toolchain: PK166 Prof. Developers Kit Version: 6.04 Toolchain Path: D:\Keil\C166\BIN\ EC++ Compiler: EC166.Exe V1.09a C Compiler: C166.Exe V6.04 Assembler: A166.Exe V5.20 Linker/Locator: L166.Exe V5.21 Librarian: LIB166.Exe V4.26 Hex Converter: OH166.Exe V4.7a CPU DLL: S166.DLL V2.50 Dialog DLL: D167.DLL V2.45b Target DLL: BIN\UL2OCDS.DLL V1.08 Dialog DLL: T167.DLL V2.46
David,
If this is indeed a problem, I guess we were right yesterday warning Keil that installation into the same folder as the existing tool-chain is, lets be charitable and say, "a little dangerous".
Tamir,
I do not think this has anything to do with "how dangerous" installing uv4 under the same folder as the toolchain might be, buth rather with DLL compatibility problems between uv4.exe, uv4.dll or msvcr80.dll with S166.DLL.
In fact, the uv4 IDE is installed separately from the toolchain in its own folder, in exactly the same way as uV3. In my system it looks like this:
D:\Keil +-- C166 | +-- uV3 | +-- uV4
Even the dlls are all installed locally in its own folder (again, as with uv3), so I do not think this can disturb or be influenced by an existing uv3 setup (unless any registry settings are shared).
Fine. For me, it is very simple really: make a totally separate installation environment for the new IDE. Only then the product can truly be evaluated. Any other combination introduces too many question marks.