• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 81 subscribers
  • Views 4870 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP432 SWD Debugger

Christopher Carl
Intellectual 350 points
Other Parts Discussed in Thread: SEGGER

Hello,

I am having a lot of trouble trying to a find a debug emulator capable of supporting the SWD protocol as well as maintaining compatibility with Code Composer Studio v6.1.   It appears that all of the emulators that TI offers (XDS100, 200, and 560) do not support the SWD protocol.  So far, it seems as though the Segger J-Link emulator is the only device that is capable of utilizing the SWD protocol to interact with the msp432 as well as provide compatibility with CCSv6.  Would anybody be able to clarify any of this information and/or put me in line with a better solution that I am not aware of?

Thanks,

-Chris

  • 0
    Guru 92251 points

    Some comments:

    1) The XDS110-ET which comes with the MSP-EXP432P401R supports SWD - see MSP432 FAQ

    2) The Segger J-Link emulator is not officially supported or tested with CCS 6. E.g. I have had problems due to the Segger J-Link not working with other Cortex-M4F devices under CCS 6 such as CCS 6.1.0.00104 with Linux J-Link support v0.1.0.4 crashes when used with a EK-TM4C1294XL

  • 0 in reply to Chester Gillon
    Intellectual 350 points

    Thank you for the response!

    We have successfully utilized the XDS110-ET on the MSP-EXP432P401R to program a second  MSP-EXP432P401R using the SWD protocol, as well as debug through CCSv6.  I wasn't sure if there was a more "elegant" solution that didn't involve having to pull off the external output header on the XDS110-ET.  Also, it is very good to know that the J-Link does not play nicely with CCSv6.  It appears that at least for the time being the XDS110-ET will suffice for our application.  

    Is there any way to purchase the XDS110 as a stand alone emulator?  It appears not but I figured I would post the question regardless.  

    Thanks for the input I really appreciate it.

    -Chris

  • 0 in reply to Christopher Carl
    Prodigy 30 points
    Hi Chris,

    I will be interested to know exactly how you did to use the XDS110-ET from one lunchpad to program another one msp432, we have tried by connecting J103 connector to a board with msp432 we have designed.
    We have buyed a XDS100V2 programmer but not yet received, it will be usefull to find a way to programme the msp423 as soon as possible


    Thank you for you help.
  • 0 in reply to vinecnt vauchey
    Intellectual 350 points

    On the emulator supplying the SWD signals we did the following:

    • Removed the jumpers
    • Flipped the JTAG switch to Ext Debug in order to break the signals from the msp432 on that board
    • Pulled the GND, SWCLK, and SWDIO signals off the J103 header and over to the J102 header on the second emulator board that we wanted to program.

    On the emulator containing the msp432 that we wanted to program we did the following:

    • Connected the signals from the J103 header of the first emulator over to the J102 header on this board. The J102 header follows the standard defined by ARM, so you can obtain the correct pin mappings just by searching for the pinout. Pin 2 is SWDIO, Pin 3 is GND, and Pin 4 is SWDCLK
    • Flipped the JTAG switch to Ext Debug so the signals are routed to the msp432
    • Plugged in the USB cable.  This was necessary because the USB power is needed in order to "activate" the JTAG switch, as it is a digital switch (as can be seen in the schematic).

    Lastly, we used code composer studio to flash our board.  Within CCS, we had to make sure the right debug connection was chosen and that it was set to SWD Mode with SWO Trace disabled. (To change these settings, select your .ccxml target configuration and make sure the connection is set to Texas Instruments XDS110 USB Debug Probe.  Then in "advanced setup", click Target Configuration, select "Texas Instruments XDS110 USB Debug Probe" and then under connection properties select "Use SWD Mode with SWO Trace disabled" in the SWD Mode Settings.

    Hopefully this setup works for you if you get a chance to try it.

  • 0 in reply to Christopher Carl
    Intellectual 350 points
    I should also add that we had the USB cable on the first emulator plugged in as well. So if you have both plugged into your computer, you should make sure you have the correct one selected as your debug probe.

**Attention** This is a public forum