• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 83 subscribers
  • Views 517 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.

TMS320F2802: Unable to connect TMS320F2802 processor with the onboard XDS110 USB Debug Probe which comes with the F280049C Launchpad

Preetham Venkatesh
Prodigy 40 points
Part Number: TMS320F2802

The CCS version used is version 10, and I am enclosing the screenshot of the target configuration below.

When I press the "Test Connection" button, I get the following error:

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


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

C:\Users\HP\AppData\Local\TEXASI~1\CCS\ccs1010\
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 'May 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
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]

Since, I am using an onboard XDS110 USB debug probe that comes with the F280049C Launchpad, that has only 10 pins, I am using a 10 pin to 14 pin connector for the JTAG as per the table given below.

I am attaching a photo of the onboard XDS 110 in the F280049C Launchpad that I have used. I have removed the jumpers present in J101 as well while connecting to an external target.

I would much appreciate it if someone can give me a solution for the aforementioned problem.

Thanks in advance.

  • 0
    Prodigy 40 points

    Sorry, the photos aren't attached in the previous question. I am attaching the photos here separately.

    Target Configuration:

    10 pin to 14 pin mapping table:

    Photo of the onboard XDS 110 in the F280049C Launchpad:

  • 0 in reply to Preetham Venkatesh
    TI__Guru* 77720 points

    Preetham,

    I'm including the link to J102 on the LAUNCHXL-F280049C for reference page 5.  

    The 10-14 pin connection is correct, however, the J102 connector does not bring out the EMU0/EMU1 signals that are used on the F2802 device. 

    I think we can connect without them, but you will need to tie them off at the 14 pin header with EMU0 grounded and EMU1 pulled to VDDIO(3.3V).  This will put the device in Wait In Reset mode, which will wait for the JTAG connection to release the internal reset strobe.

    There will be some analysis features you won't have access to, but all normal debug functions should work.

    Let me know if this allows you to connect.

    Best,
    Matthew

  • 0 in reply to MatthewPate
    Prodigy 40 points

    Hi Matt,

    I was under the impression that emulation pin 0 should be internally connected to 3.3V. After powering on the processor, I checked the voltage on emulation pin 0 of the target processor with a multimeter. It read 3.3V.

    Anyhow, I was able to remove the resistor that tied emulation pin 0 to 3.3V and I grounded the same pin. Yet, I wasn't able to connect to the target processor. The same error showed up.

  • 0 in reply to Preetham Venkatesh
    TI__Guru* 77720 points

    Preetham,

    EMU0/1  high/high is fine as well for normal operation; but in this case I wanted to try and see if activating the WIR mode helped us connect(which it didn't).  Can you advise on the connection you have from the in terms of the physical 10 pin header on the LAUNCHXL-F280049(not the generic 10-pin to 14-pin) to the 14-pin header you created.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    Prodigy 40 points

    Sorry for the late reply. Was caught up with some work. I'm still unable to resolve this issue.

    Here is a picture of the custom-made PCB that I used to map the 10-pin to 14-pin connector.

    Top View:

    Bottom View:

    Thanks in advance.

  • 0 in reply to Preetham Venkatesh
    TI__Guru* 77720 points

    Preetham,

    Based on the 14 pin JTAG signals here's what the mapping should be:

    J102 14-pin JTAG
    Pin 1 3.3V

    Pin 5 VCCS
    Pin 2 TMS

    Pin 1 TMS
    Pins 3/5/9 GND

    Pins 4/8/10/12 GND
    Pin 4 TCK

    Pins 9/11 TCK/RTCK
    Pin 6 TDO Pin 7 TDO
    Pin 8 TDI Pin 3 TDI
    Pin 10 TRSTn Pin 2 TRSTn
    Pins 13/14 tie off manually

    Best,
    Matthew