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

CCS/MSP432P401R: Error connecting to the target: (Error -1170 @ 0x0)

Yadhukrishnan V M72
Expert 1875 points

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hi,

      I am working with MSP432P401R Launchpad using CCS studio. I had this error when clicked debug button. The error is as shown below.Error connecting to the target:

(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 6.0.14.5)

I don't have any idea about this error. I tried the factory reset also but the same error displayed. I couldn't do atleast an led toggle with this error. Please provide me a solution for this.

  • 0
    TI__Mastermind 39150 points
    Yadhukrishnan,

    Can you tell me what your settings are when you follow these directions?
    View -> Target Configurations -> User Defined -> NewTargetConfiguration.ccxml (I renamed this file) -> Basic tab (select XDS110 debugger, MSP432) -> Advanced tab -> Texas Instruments XDS110 USB Debug Probe_0
    Configure the Connection Properties.

    This is where you can lower your JTAG TCLK frequency if needed. I would specificaly be interested to hear what your JTAG/SWD/cJTAG mode is also.
  • 0 in reply to Evan Wakefield
    Expert 1875 points

    Hi Evan,
    I can see following things below connection properties,
    Board Data File : auto generate
    Debug Probe Selection : only one XDS110 installed
    SWD Mode Settings : Use 1149.1 JTAG, SWD Mode is disabled

    When I click the Test connection following messages appeared,

    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-233' (0xffffff17).
    The title is 'SC_ERR_PATH_BROKEN'.

    The explanation is:
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

    [End: Texas Instruments XDS110 USB Debug Probe]

  • 0 in reply to Yadhukrishnan V M72
    TI__Mastermind 39150 points
    Yadhukrishnan,

    According tot hat error, it's possible that one of the JTAG lines has a short to GND or VCC. Can you send me a picture of your setup? Speciifcally the jumpers at the top of the launchpad and your configuration? It should look like the photo on the front page of this document. www.ti.com/.../slau597c.pdf

    Also, for general advice on debugging JTAG connectivity, this link is good:processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems
  • 0 in reply to Yadhukrishnan V M72
    TI__Mastermind 39150 points
    Yadhukrishnan,

    Rev 1.0 (Black LaunchPad) contains pre-release experimental silicon. Our recommendation is to use the Rev 2.0 (Red LaunchPad) for all projects moving forward before diving further into this. Do you have one on hand? There are a number of updates to the LaunchPad's hardware and the device on the Rev 2.0 launchpad is Rev C (updated) silicon. Currently our software and tools are moving away from the black launchpads as there have been a number of updates in both hardware on the LaunchPad, hardware in the silicon and software supporting the silicon.

    For migrating from Rev B to Rev C and beyond, as well as seeing the differences that exist, it's good to reference this document: www.ti.com/.../slaa700

**Attention** This is a public forum