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

uVision4 to uVision5 migration issue

I've been developing and maintaining a project using uVision 4 for quite a few years and recently updated to uVision 5 (MDK-ARM Professional license). This project is using the Infineon XE167 microprocessor. When I open the project using uVision 5, the application will not even start to compile because the Device is unknown. When I view the Project Options, and select the Device tab, the "uVision Legacy Device Support" message box is displayed indicating that the Device: XE167FM-72F is supported by the Legacy Pack and must be installed. I've installed the Legacy Packs as instructed and the issue remains unchanged. Can't compile because of unknown device.
There must be something I'm missing. Can anyone point me in the right direction?

Parents
  • OK... I think I have a solution.

    I copied most of the contents of the TOOLS.INI from uVision 4 directory (c:\keil). Specifically, I copied from "[C166]" to the end of the C166 section and from "[C51]" to the end of the C51 section into the TOOLS.INI file in the uVision 5 directory (C:\Keil_v5).

    I can now set the Device in the legacy project and the project compiles and links OK.

    It would be nice to hear from Keil as to the side-affects of doing this or if they have a different solution.

Reply
  • OK... I think I have a solution.

    I copied most of the contents of the TOOLS.INI from uVision 4 directory (c:\keil). Specifically, I copied from "[C166]" to the end of the C166 section and from "[C51]" to the end of the C51 section into the TOOLS.INI file in the uVision 5 directory (C:\Keil_v5).

    I can now set the Device in the legacy project and the project compiles and links OK.

    It would be nice to hear from Keil as to the side-affects of doing this or if they have a different solution.

Children