Upgrading to a new CrossWorks version

Follow

Comments

7 comments

  • Avatar
    Peter Klemm

    Do I need to uninstall the previous version before I install the new version, or will the installer take care of this?

  • Avatar
    Paul Curtis

    There is no requirement to remove a previous version.

  • Avatar
    Ian Clark

    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.

  • Avatar
    Michael Johnson

    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

  • Avatar
    Ian Clark

    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.

  • Avatar
    AJ de Vries

    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

  • Avatar
    Michael Johnson

    Yes you'll need to request another activation key for 2.2.

     

    Regards

    Michael

Please sign in to leave a comment.