msp432 launchpad

Yes, when I plug msp432 launchpad I see (in window device manager)

under Ports (COM & LPT)

+) XDS110 Class Application/User UART

+) XDS110 Class Auxiliary Data Port

under Texas Instruments Debug Probes

+) XDS110 Class Data Port

+) XDS110 Class Debug Probe

david draper said:

I now have MSP-EXP432P401R launchpad BRICK.

Rebooted windows, that often helps. PLEASE someone tell me how to get past "Error connecting to the target"

Not sure if the same can happen with a MSP432 but maybe the the Unlock procedure described in section 7 Device Security of  will un-brick your device.

much thanks Chester Gillon. I have sucessfully "un-bricked" my launchpad.

Code Composer Studio has ALWAYS confused me especially the "debuging" stuff. Can you suggest a "tutorial" that might clarify things. For instance when I see the following I have no idea what it all means.

+ TI XDS110 USB Debug Probe_0

    + MSP432P401R

        + CS_DAP_0

            + subpath_0

                  + CORTEX_M4_0

david draper said:

For instance when I see the following I have no idea what it all means.

I haven't come across a "tutorial" for this. This thread https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/238654 provides some background information, but that the end user shouldn't need to edit the device XML files.

Hi, I have the same problem with de Launchpad. It was perfect, but i tried to set the VLOCLK as MCLK source.....then the debbuging session crash.

   CSKEY = CSKEY_VAL;       // This line pass OK

   CSCLKEN = VLO_EN;         // This line pass OK

   CSCTL1 = 0x00070001;     // Here was the crash.....and i was unable to reconect to the MSP since then.

  CSKEY = 0;

I tried the procedure described on slau575b.pdf, Section 7. But still don't work.

Regards,

Carlos Silva

And it's January 12, 2016, and I just reproduced this failure again with the steps below. My question is this:

    T E X A S  I N S T R U M E N T S:  How can you offer these launchpads for the low low price of $4.32 but fail to warn people that if they try to run the "out of box" demo under CCS they will brick their board? This is NOT A GOOD OUT OF BOX EXPERIENCE!

    What is the official TI bug number for this problem? Is there a workaround, or should I tell the seventeen people that have 21 new boards as of last night to simply avoid trying to run the out of box demo under CCS?

  Steps to reproduce:

   1) Connect board, play with demo

   2) Bring same demo up under CCS and use F11 to build/debug it

         (board's debug firmware update has to happen, but just this first time)

        BRICKING HAPPENS HERE

   3) Follow SLAU575B section 7 procedure to un-brick

   4) Do not return to step 2

(I reproduced this with a board bought  a few months ago as well as two I received yesterday: I got identical behavior, using latest CCS 6.1.2.00015 with all available updates on 64 bit Windows 7.)

-Pete

Hi Pete,

First off, I'm incredibly sorry to hear about the troubles that you and others had to go through debugging this issue. I can understand how frustrating it could be when you can't connect to the device despite doing everything right . Next, thank you for reporting this issue and letting us know that other folks are also experience similar issue. This really helped us timely investigate and locate the problem with the MSP432 no longer being able to connect to the IDE after flash programming.

ISSUE

Issue is not limited to just the MSP432 LaunchPad out-of-box experience code but several other MSP432 SW projects provided by MSPWare v2.40.00 (available for desktop environment via direct download or via CCSv6.1.2 installation) or CCS Cloud version 01/2016.

The software mismatch due to the release schedule difference between CCSv6.1.x + MSP432 Emulator v6.1.1.2/3 and the next MSPWare update resulted in this issue. Once one of the affected projects is compiled and downloaded to the MSP432 device, the IDE can no longer communicate or control the MSP432 until a factory reset is performed. 

Failing conditions:

- CCSv6.1.x IDE + MSP432 Emulator v6.1.1.2/3 update

- Any MSP432 software projects from MSPWare v2.40.00 desktop or TI-REX/ CCS Cloud 01/2016 versions. 

Note that MSPWare v3.10.00 beta users are NOT affected by the issue, as the software has been updated to work with CCSv6.1.2 + MSP432 Emulator v6.1.1.2/3. 

- MSP432 device whether stand-alone or part of the MSP432 LaunchPad

HOW TO FIX

Here are the quick instructions to get your MSP432 LaunchPad back up and running, for detailed explanation and background information, please scroll down below.

1. Immediate fix for your old/existing project or any MSP432 software from MSPWare version 2.40.00.xx or earlier.

Open the file startup_msp432_ccs.c in your project and add the following line of code 

#pragma RETAIN(interruptVectors)

right before this line of code:

#pragma DATA_SECTION(interruptVectors, ".intvecs")
void (* const interruptVectors[])(void) =
{ . . .

2. Long-term fix for MSP432 development on the desktop  (CCS, IAR, Keil, or gcc developers)

 Update your MSP432 software with the new MSP432 CMSIS software update, either with the beta version at ti.com/MSP432CMSIS today or on the official branch of MSPWare  v3.20.00 to be released in 02/2016.

3. Solution for TI Cloud developers 

 TI Resource Explorer and CCS Cloud will be updated with the new msp432 software once MSPWare v3.20.00 is released in 02/2016. Until then, apply the fix #1 for your existing cloud projects.

DETAILED EXPLANATION 

The root cause is related to the unfortunate timings  of the CCSv6.1.x + MSP432 Emulator Update v6.1.1.2/3 and the MSPWare software update. Specifically, a small but critical change to the msp432 linker command file was introduced in MSP CCSv6.1.2 (released a few weeks ago).

The MSP432 interrupt vector table is defined in the msp432_startup_<ide>.c:

#pragma DATA_SECTION(interruptVectors, ".intvecs")
void (* const interruptVectors[])(void) =
{
    (void (*)(void))((uint32_t)&__STACK_END),
    . . . . . 

but since it is not called by any function anywhere in the code, it needs to be retained by the linker using the #pragma retain.

Up until CCSv6.1.1, this is achieved via the --retain=interruptVectors directive in the msp432p401r.cmd linker command file 

--retain=interruptVectors
--retain=flashMailbox

MEMORY
{
    MAIN       (RX) : origin = 0x00000000, length = 0x00040000

Starting with CCSv6.1.2, the interrupt vector references have been streamlined and the retain directive has been removed from the msp432p401r.cmd and relocated to the startup_msp432_<ide>.c as follows.

#pragma RETAIN(interruptVectors)
#pragma DATA_SECTION(interruptVectors, ".intvecs")
void (* const interruptVectors[])(void) =
{ . . .

New CCS projects will use new linker & startup files following the new convention, no problem there. Problem arises when an old project using an old startup file is imported into the workspace, this process often also pulls in the new linker command file from CCS. This specific file combination does not have the retain directive, resulting the linker optimizing away the interrupt vector table. With an empty interrupt vector table, the device would immediately run into fault condition, forcing you to use the factory reset routine to recover device connection. This also explains cases where the code 'seems' to work the moment you hit debug from CCS, but not connectable after reset, power cycle, debugger disconnection.  

This MSP432 change has already been addressed in all of MSP432 software content, all MSP432 projects have added the interrupt vector directive to the startup_xxxx.c files. The update was implemented and incorporated in the MSPWare v3.10.00 beta released in 11/2015. This change was part of the MSP432 CMSIS Software update, more information on this sticky thread here or at www.ti.com/MSP432CMSIS.  

This beta release will become mainstream and get merged with the official MSPWare v2.40.xx line in the MSPWare v3.20.00 release planned for 02/2016. Both MSPWare v3.10.00beta (available now) & MSPWare v3.20.00 (available ~02/2016) will work with CCSv6.1.2+ with respect to MSP432 software. 

 CCS Cloud will also follow with MSP432 software content update.

As the first section laid out, short term (desktop/cloud) fix is to add the retain directive to your startup_ccs.c, and long-term solution is either to update to MSPWare v3.10.00-beta and benefit from CMSIS TODAY or MSPWare v3.20.00 ~ 02/2016.

Thanks again for reporting the issue and hopefully the fix will get you back on track to evaluate the MSP432 LaunchPad!

Regards,
~Dung 

Thank you for the comprehensive, candid reply. You've provided all the information we need to deal with this and I can help to get the (now 20) new users of the dev board in this area off to a proper start.

-Pete