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

AM2634 Control Card - unable to connect to XDS110 DAP in CCS11

Jon Wingfield
Prodigy 215 points

Error output from "Test Connection" button in CCS11

[Start: Texas Instruments XDS110 USB Debug Probe_0] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity [Result] -----[Print the board config pathname(s)]------------------------------------ C:\Users\JOWING~1\AppData\Local\TEXASI~1\ CCS\ccs1110\0\0\BrdDat\testBoard.dat -----[Print the reset-command software log-file]----------------------------- This utility has selected a 100- or 510-class product. This utility will load the adapter 'jioxds110.dll'. The library build date was 'Dec 8 2021'. The library build time was '11:16:32'. The library package version is '9.6.0.00172'. 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 '-230' (0xffffff1a). The title is 'SC_ERR_PATH_MEASURE'. The explanation is: The measured lengths of the JTAG IR and DR scan-paths are invalid. This indicates that an error exists in the link-delay or scan-path. [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0
    TI__Guru**** 463541 points

    Hello Jon,

    Jon Wingfield said:
    [An error has occurred and this utility has aborted]-------------------- This error is generated by TI's USCIF driver or utilities. The value is '-230' (0xffffff1a). The title is 'SC_ERR_PATH_MEASURE'. The explanation is: The measured lengths of the JTAG IR and DR scan-paths are invalid. This indicates that an error exists in the link-delay or scan-path. [End: Texas Instruments XDS110 USB Debug Probe_0]

    There are several potential causes for this type of error. Many of them are documented in the below link:

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#path-measure

    I would check that your target configuration file is configured correctly and the device is properly powered and in a good state. If that has already been confirmed valid, try lowered the TCLK speed as mentioned in the below article.

    If you are still having issues, please attach the ccxml file that you are using and also provide which host OS is being used. I assume some version of Windows based on one of the paths in the message you posted above (which version of Windows?). I also assume you are using CCS 11.1 based on the installation directory.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 463541 points

    Hi Jon,

    Based on our experience with the controlcard, it looks like you will need to lower TCLK to 1MHz (or less) for best stability. Please give that a try.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Mastermind 27355 points

    Hi ki,

    That guidance is correct. This is a limitation due to the the isolators used. The later batch of boards have an alternative isolator part installed that enables a much higher data rate.

    Regards,
    Sahin