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

old license in uVision4

Hi,
We have just bought uVision4 and STM32 dev. suit for new projects. We already have uVision2 and C51 and C166 from some years ago (using printer port dongles) to support older products.

How can I put the old product codes into the new uVision4 system so I can run everything from one Development Environment? It would save me having to run uVision2 and uVision4 on the same PC.

thanks for any help
PhilipJ

Parents
  • I have multiple installation directories like c:\Keil_xxx\ where xxx is the version.

    This means that I have multiple TOOLS.INI files - one for use with the older ARM compiler and one for the newer ARM compiler. When updating older projects, I continue to use the same tool chain that was used during the original acceptance testing.

    The Keil installer on the other hand will do:
    c:\Keil\xxx\
    which means that a newer installation will backup the tool chain directory but overwrite some files. I'm not too fond of getting files overwritten without knowing for sure what the files does.

Reply
  • I have multiple installation directories like c:\Keil_xxx\ where xxx is the version.

    This means that I have multiple TOOLS.INI files - one for use with the older ARM compiler and one for the newer ARM compiler. When updating older projects, I continue to use the same tool chain that was used during the original acceptance testing.

    The Keil installer on the other hand will do:
    c:\Keil\xxx\
    which means that a newer installation will backup the tool chain directory but overwrite some files. I'm not too fond of getting files overwritten without knowing for sure what the files does.

Children
No data