Part Number:MSP432P401R
Tool/software: Code Composer Studio
I have a fair number of black MSP432 LaunchPads with the Rev. B silicon. I understand that these are being depreciated with the driver support being pulled sometime on or before June 2017.
However, I would like to avoid tossing these into the trash. So my hope is to lock down a properly versioned tool chain (under a VM) and prevent that tool chain from automatically being updated. My understanding is that the versions required are:
CCS 6.1.1 (Windows)
MSP432 device support files 6.1.0.6
MSPWare 3.30.00.18
MSP432 DriverLib 3.10.00.09
Are there any other files I need to archive to support not only the 432 target, but the XDS110 as well? How do I ensure that CCS never updates? Is there a way that I can do a reinstall of CCS after June 17 or do I need to archive a copy of the VM in case of failure of the CCS and/or the Windows installation?
Also with regard to Energia, is the XDS110 and MSP432 Rev. B support locked in time by the specific version of Energia? Or are those support files automatically updated in the distribution files, thereby potentially breaking support for the Rev. B version in the future?
Thank you in advance for considering my many questions.