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

TMS320F28379D: Code Composer Studio

AMIT KUMAR
Prodigy 50 points
Part Number: TMS320F28379D

Tool/software:

I am using CCS Version 12.0.4.0 for MATLAB Simulink and CCS Version 20.1.1 for CCS code debugging and my use. However, it is causing issue an connection error is coming related JTAG connection. 

So I want to know if using both version on my PC is causing error, because while opening CCS 20.1.1 it not initialising properly and error dialog is opening as in attached image. Along with this during test connection below error message is coming:-

[Start: Texas Instruments XDS100v2 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\amit1\AppData\Local\Texas Instruments\
CCS\ccs1220\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Sep 26 2024'.
The library build time was '10:09:41'.
The library package version is '20.0.0.3178'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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 FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 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).

 

Regards

Amit

  • 0
    Prodigy 50 points

    additiona error log which is missing in above question:-


    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 64 32-bit words.

    The JTAG IR instruction path-length was not recorded.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0

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

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

    The value is '-150' (0xffffff6a).
    The title is 'SC_ERR_FTDI_FAIL'.

    The explanation is:
    One of the FTDI driver functions used during
    configuration returned a invalid status or an error.

    [End: Texas Instruments XDS100v2 USB Debug Probe]

  • 0 in reply to AMIT KUMAR
    TI__Mastermind 36526 points

    Hi,

    Are you using the launchpad? 

    Do you see the XDS110v2 in your PC device manager?

    Thanks,

    Ben Collier 

  • 0 in reply to Benjamin Collier
    Prodigy 50 points

    Thanks for your reply Ben. However, It was CCS error, which was resolved when I reinstalled the CCS. 

    Regards

    Amit Kumar