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.
How does uVision3 decide where to locate tools.ini?
I have a full version of uVision3 installed at c:\kail\
I did install an evaluation version of the C51 compiler in a different directory, and now my ARM tools are "off-line" since uVision3 opens the tools.ini from the C51 installation.
There is no environment variable pointing to the keil tools, and there are no obvious registry settings that specify the tools.ini path.
It seems likely that I can just merge the c:\keil\tools.ini contents into the tools.ini that is right onw used, but do I have to reinstall MDK-ARM to get everything correct again?
uVision uses the .ini file located one folder level above the Uv3.Exe file, that is:
<whatever_drive_and_path>\Keil\Uv3\Uv3.Exe\..\Tools.Ini
You might create and use different shortcuts for Uv3.Exe, each of them using the 'private' tools.ini file of that particular installation.
OK. Then I have to see if something has happened with my shortcut, so that I started the uVision installed with C51.
Just to get going, I added all the ARM stuff to the C51 tools.ini. Bad method, but it was a working interim solution.