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.

SIMPLELINK-MSP432-SDK: SimpleLink SDK deployed as part of image

Part Number: SIMPLELINK-MSP432-SDK

Hi

I was hoping someone could answer my question regarding the TI Code Composer Studio and MPS432-SDK software

The software is added to our lab image where students are using the MSP432 board.

I believe i installed the SDK software successfully after installed the TI CCS software.  However, there seems to be additional manual steps to make use of it once a new profile logs into the Windows computer.

How can this be avoided or corrected during the installation phase?


Prior to image capture, if I sign in under the profile and do this step manually, do these changes get applied to the Default User so that any new user that signs in will adopt this automatically?

thank you,

  • I was hoping someone could answer my question regarding the TI Code Composer Studio and MPS432-SDK software

    Hi,

      Which MSP432 are you talking about? MSP432E or MSP432P. You have opened a post a while back asking about MSP432P. https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1252939/tm4c1294ncpdt-using-ssi-and-gpio-edge-interrupt

    As I explained before this is an EOL'd MCU and we have neither the LaunchPad available nor any technical support for this MCU on e2e. So please clarify which MCU are you referring to? If you are talking about MSP432P then I strongly suggest you consider the replacement MCU like TM4C123. TM4C123 has been used by quite a few universities as a introductory course to embedded programming. 

    I believe i installed the SDK software successfully after installed the TI CCS software.  However, there seems to be additional manual steps to make use of it once a new profile logs into the Windows computer.

    How can this be avoided or corrected during the installation phase?


    Prior to image capture, if I sign in under the profile and do this step manually, do these changes get applied to the Default User so that any new user that signs in will adopt this automatically?

     I'm at a lost as to what additional manual steps you are talking about here and how a new user login will affect CCS bring up. Can you show some screenshots on what you are seeing?