• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 301 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/TIDM-BIDIR-400-12: TIDM-BIDIR-400-12

Kyoungtak Kim
Intellectual 620 points
Part Number: TIDM-BIDIR-400-12
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

Hello. 

I have a problem while I follow TIDM-BIDIR-400-12 design. 

I can run the debug mode with internal xds100v1. 

I have JTAG emulator which is based on xds200. 

I want to use JTAG emulator for the TIDM-BIDIR-400-12 design.

  

In this boot mode selection table above, I can run with the onboard xds100v1 in mode 1,SCI mode.

I think If i want to run with JTAG emulator, then I should activate TRST as '1'.

In tidrhs9 document, I can find the TRST related jumper called J13.

I dis-populated that J13 jumper, tried to run Test connection button in tmsf28035.ccxml file. 

But error message showed that...

[Start: Texas Instruments XDS2xx 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\user\AppData\Local\TEXASI~1\CCS\
ti\0\0\BrdDat\testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Jul 27 2016'.
The library build time was '17:54:51'.
The library package version is '6.0.407.3'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
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]-----------------------------

This emulator does not create a reset log-file.

-----[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 XDS2xx USB Debug Probe_0]

what can I do for this error? Am I configure the correct jumper?

  • 0
    TI__Guru**** 168422 points

    Hi,

    Given you had an isolated controlCARD in your previous post, I am pretty sure this will not work with an external Debug Probe.

    The reason is that some isolated controlCARDs do not have the JTAG pins connected to the DIMM socket, thus preventing any connection other than the built-in isolated XDS100v1. 

    You can be certain by checking the scematics diagram of your controlCARD (usually available in the controlSUITE SW package). 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 620 points

    Thank you for your reply. 

    Actually I'm not using ISO type control card. 

    My control card is TMDSCNCD28035.

    ISO part exists on the baseboard. 

  • 0 in reply to Kyoungtak Kim
    TI__Guru**** 168422 points
    Hi,

    Please apologize; I missed your last reply. Are you still having this issue?

    By looking at the schematics diagram of the design, the only thing I can think it may be getting in the way of a reliable connection using the XDS200 is the TCLK speed, which is set by default to 10MHz but, given it goes through the ISO ICs, it will certainly require to be set to a slower speed.

    In this case, I strongly suggest you to look into the short clip below that helps you experiment with this parameter.
    https://youtu.be/mKxaztkCsYw

    Apart from this, I am really not sure what else is happening short of a problem on the design or assembly of your board.

    Hope this helps,
    Rafael