• State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 22 subscribers
  • Views 4968 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to use the uV4 Beta

David Planella

I have just downloaded the uVision4 Beta and I have been so far unable to use it with a uV3 project due to a consistent crash. Note that I did not remove the uVision3 installation.

I am using Windows XP Professional, SP2.

The steps to reproduce the problem are the following:

1. Start uV4
2. Open the .uv3 project through Project > OpenProject... (and selecting 'Previous project files' on the drop-down list)

And the results:

1. An error message pops up with the following information:

"uVision - Path for Toolset undefined

'C:\Keil\TOOLS.INI' does not contain a tool path

You have selected a device where no toolchain has been installed."

I click on 'OK' to close the dialog.

2. Since there is no toolchain selected, nor can the project be compiled neither can a device be selected from the Device database under the 'Target Options'.

3. I then proceed to open the 'Components, Environment and Books' dialog in order to have a look whether the
'C:\Keil\TOOLS.INI' '(which is valid and present in the system).

4. There I try to see whether I can see more information about TOOLS.INI.

5. When clicking on the 'Folders/Extensions' tab on the 'Components, Environment and Books', uVision4 crashes with a standard Windows crash dialog without further information than 'uVision IDE has encountered a problem and needs to be closed' (note that this is an approximate translation from the original German message).

Is this a known bug? Is there a workaround?

Many thanks in advance.

Parents Reply Children
  • 0 in reply to David Planella

    Hi,

    I installed the beta as well and got the same error message about the missing TOOLS.INI. There is an easy solution: copy the TOOLS.INI file from your original uVision directory and it works.

    There is another problem though that renders uVision4 unusable.

    Try the following procedure:
    - Open uVision4
    - Open an earlier project (uVision2 project file)
    - Close the project => you get a message the file will stored in the new format. Confirm that.
    - Then re-open the earlier project.

    You then get an error message something went wrong when opening the new project file. The error details are:

    Line 143
    Fatal message: invalid character 0x7

    After that the project content is incomplete and it is no longer possible to build it.

    Unfortunate: I was really hoping that uVision4 would work better under VISTA then uVision3 because that one keeps crashing when certain editor options are activated.

    Regards, Filip

  • 0 in reply to Filip Dossche

    Hi,

    In the mean time I have located the actual entry in the uvopt file produced by uVision4 that causes the problem. The last line is the actual culprit. I just hope it helps.

    Regards, Filip

            <SetRegEntry>
          <Number>0</Number>
          <Key>DLGTCYG</Key>
          <Name>8‘|ÿÿÿÿ2‘|«‘|ë‘|</Name>

  • 0 in reply to Filip Dossche

    Hi Filip,

    Please could you report this case to support.intl@keil.com

    Thanks,
    Richard

  • 0 in reply to Richard Sewell

    How about setting up a specific forum for the beta?

    Preferably one where issues like this could be tracked...