I have an existing copy of CrossWorks and I want to upgrade to a later version, what do I need to do?
CrossWorks is designed to allow multiple versions to be installed at any one time, you just need to make sure that you install the new version of CrossWorks to a different directory. It is not necessary to uninstall the previous version of CrossWorks before installing the next.
If you are upgrading to a new major or minor version of CrossWorks (e.g. 1.6 to 1.7, or 1.7 to 2.0), the default behaviour of the installer will be to install CrossWorks to a unique directory with a unique shortcut. If however you are upgrading to a new build revision (e.g. 1.7 build 2 to 1.7 build 3) the installer will select the same directory and shortcut as the previous version, so if you want the two versions to coexist you should modify the Destination Folder to select a different installation directory and Program Folder (Windows only) to select a different shortcut.
Please note that with CrossWorks version 1.x the support packages and target interface settings are not shared between installations so you will need to re-install support packages and re-apply any changes you made to the target settings in the new installation. This does not apply to CrossWorks version 2.x or later.
Comments
8 comments
Do I need to uninstall the previous version before I install the new version, or will the installer take care of this?
There is no requirement to remove a previous version.
I upgraded from 2.1 to 2.2 on Windows 7, 64bit. The previous K60 tower projects had some files overwritten, but the main problem is that the build fails on a missing Linker or Memmap file. I can still run the code on 2.1 under Mac Osx. Are there any places to find sample linker files or mappings for the K60 or K40 Tower boards? When I tried to create a map file, the errors were that there was not enough space for the vectors, and pretty much every section.
You'll need to reselect the Target processor - rather than enumerate each processor the Target is now based on the processor family - which corresponds to the CMSIS support that Freescale provide.
Regards
Michael
Thanks for the above. I updated the processor and am back to debugging on the K60. I feel for you folk having to track the CMIS stuff and all the vendors changes. Not easy to decide which uController to #define in the preprocessor, as the names are not exactly the same as the target device.
I'm upgrading from CrossWorks for ARM V2.1 to V2.2 on Windows XP 32-bit. But now my license is de-activated.
Is this a normal situation?
Must I now request a new license?
Thanks in advance and kind regards,
AJ
Yes you'll need to request another activation key for 2.2.
Regards
Michael
I'm upgrading from a very old version 1.7 to 4.2 and get "targets/LPC2000.h: No such file or directory" when importing the old project. I know it has something to do with where the packages are installed but I can not find where to change that.
Please sign in to leave a comment.