• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 825 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.

MSP432P401R: MSP_EXP432P401R Upload error

Kipton Moravec
Expert 1545 points

Part Number: MSP432P401R

I think am making progress this is the latest error when I try to Download and Debug from the IAR compiler. 

Thu Nov 08, 2018 10:54:22: Fatal error: Failed to connect to the XDS emulator (connect DAP)... (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and
serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 8.0.803.0) Session aborted!
Thu Nov 08, 2018 10:54:22: Unloaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\config\flashloader\TexasInstruments\FlashMSP432P4.mac
Thu Nov 08, 2018 10:54:23: IAR Embedded Workbench 8.32.1 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\bin\armproc.dll)

MSP_EXP432P401R is plugged into the USB port 

Device manager looks like XDS110 is using COM4 and COM5.

When I run xdfdfu -m 

C:\ti\ccs_base\common\uscif\xds110>xdsdfu -m

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2018 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

The requested device was not found on the bus.

  • 0
    Expert 1545 points
    Device manager says
    XDS110 Class Application/User UART (COM5)
    XDS110 Class Auxiliary Data Port (COM4)
  • 0 in reply to Kipton Moravec
    Expert 1545 points
    Looking closer, it does seem to see it.

    Thu Nov 08, 2018 11:12:49: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\config\flashloader\TexasInstruments\FlashMSP432P4.mac
    Thu Nov 08, 2018 11:12:49: Connecting to TI XDS110 ( Probe no: M4321005 ) COM[5/4]
    Thu Nov 08, 2018 11:12:49: Firmware: XDS110 Class Auxiliary Data Port
    Thu Nov 08, 2018 11:12:57: Fatal error: Failed to connect to the XDS emulator (connect DAP)... (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and
    serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the ReadMe.txt file there for instructions. (Emulation package 8.0.803.0) Session aborted!
    Thu Nov 08, 2018 11:12:57: Unloaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\config\flashloader\TexasInstruments\FlashMSP432P4.mac
    Thu Nov 08, 2018 11:12:57: IAR Embedded Workbench 8.32.1 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.2\arm\bin\armproc.dll)
  • 0 in reply to Kipton Moravec
    Expert 1545 points
    My colleague is telling me to disconnect the built-in debugger on the MSP-EXP430P410R board and make a cable to the IAR j-link debugger. Since I cannot seem to get an answer I am going to try that, as opposed to waiting.
  • 0 in reply to Kipton Moravec
    Expert 1545 points

    I guess the built-in debugger is not working on the MSP-EXP432P401R board. I can debug the MSP-EXP432P401R using the IAR j-link debugger.

    On the MSP-EXP432P401R i removed the jumpers on RST, TMS, TDI, TCK, TDO and put a female SIP socket on those pins on the MSP432P401R side of the board to wire to. I also put a SIP socket on Gnd and 3.3V on the end connector.

    I left the jumpers on 5V, 3.3V, GND, RXD and TXD so I would have power and the USB serial port.

    Here is how I wired it
    j-link
    1 Vref -> 3.3V
    3 nc
    5 TDI -> TDI
    7 TMS -> TMS
    9 TCK -> TCK
    11 RTCK -> Gnd
    13 TDO -> TDO
    15 RESET -> RST
    17 nc
    19 nc

    j-link 4, 6, 8, 10, 12, 14, 16, 18, 20 all tied to Gnd

    Project->Options->Debugger I selected Driver "J-Link/J-Trace"

    Project->Options->J-Link/J-Trace
    Reset "Normal"
    JTAG/SWD speed "Auto"
    everything else blank

  • 0 in reply to Kipton Moravec
    TI__Expert 8510 points

    Kipton,

     Were you able to successfully program the MSP432? It sounds like you may have a damage board on the XDS side, but before giving up completely, you might try looking at another post addressing the same "Error -260" issue, listed below:

    -Bob L.

  • 0 in reply to Bob Landers
    Expert 1545 points
    Yes I am programming and debugging the MSP-EXP432P401R board using the IAR j-link for ARM Processors. Not the built-in TI XDS110 ( Probe no: M4321005 ). There is a bug in the TI debugger somewhere and I am out of time chasing it. I have already lost over a week trying to get the tool working.

    It turns out my colleague in Austin could not get the built-in debugger on his MSP-EXP432P401R board to work either, and that is what he did.

    So rather than fight it, we wired in the j-link programmer/debugger. It worked immediately. So we are off and running.

    I do not want to call this "resolved" because it still does not work as advertised. But we have a work around for us since we have this other programmer/debugger.
  • 0 in reply to Kipton Moravec
    TI__Expert 8510 points
    Kipton,
    In this context, "resolved" simply means that there is no further action forthcoming on the thread. I'll go ahead and close the thread.
    -Bob

**Attention** This is a public forum