• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 901 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/MSP432P401R: Locking down tool chain and drivers for XMS432P401R - Rev B

Dubnet
Intellectual 965 points
Part Number: MSP432P401R
Other Parts Discussed in Thread: ENERGIA, MSP-FET, SEGGER

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.

  • 0
    TI__Prodigy 595 points

    Hey,


    until MSP432P401R Rev B silicon is deprecated you can still update all components you would like to update.

    Once we drop the Rev B support you can still install an existing/older CCS version and pay attention to not install any updates on the following components (speaking of CCS7 components now):

    • MSP432 tool-chain
      • CCS MSP432 Flash files
      • CCS MSP432 support files
      • MSP Debug Probe drivers (only used for MSP-FET)
    • TI Emulators
    • SEGGER J-Link USB Driver

    I cannot exactly name the updates or CCS release versions that will remove support by default, but there will surely be a E2E post on that and probably  information about how to continue internal development on a TI website linked by the error message in CCS. Still we highly recommend to move to production material.

    Generally speaking I don't see a potential issue if you stick to CCS6.x. To be more future proof (especially if you want to continue with newer revisions of MSP432P4xx family devices), I would recommend to use the latest CCS7.x and move to the SimpleLink MSP432 SDK that already delivers DriverLib and examples.

    I'm not sure about the Energia strategy though. Maybe another TI employee can comment on that.

    Hope this helps you.

    Best regards,
    Bob Heilmaier

  • 0 in reply to Bob Heilmaier
    TI__Mastermind 25045 points
    Adding to Bob's comment, you may find this wiki useful processors.wiki.ti.com/.../XMS432_Support
  • 0 in reply to DavidL
    TI__Guru**** 171309 points
    Hi,

    Just adding to other's comments, please check the wiki page below that talks about how to create a consolidated package that includes CCS and other SW components. It also talks about how to disable CCS from checking for updates.

    processors.wiki.ti.com/.../Enterprise_distribution

    Regards,
    Rafael

**Attention** This is a public forum