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/TMDSCNCD28035ISO: Piccolo TMS320F28035 Target not connected

Part Number: TMDSCNCD28035ISO
Other Parts Discussed in Thread: TMS320F28035, C2000WARE,

Tool/software: Code Composer Studio

Hello, T community,
I have received Piccolo TMS320F28035 isolated card whose link is http://www.ti.com/tool/TMDSCNCD28035ISO.
Also I have a Docking station (I don't think i need it for programming the isolated card). For first use, i tried to flash a ti

code to check it but i receive this error :
"C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.1.0.00007) " .

I found another threads but it was in vain for my case. 
my trials to solve this problem:
1- configuration file was set.
2- POWER LED is on (while trying with card switches) 
3- Tried the the 3 versions of xds100 probe.
4- Tried bare metal TMS320F28035 and Experimenter's Kit- piccolo f28035
5- Tried using Docking station usb and Isolated card usb.
6- All drivers I have cuz it is not my first time working on ti products. also the IDE is the last version ( Version: 9.0.1.00004 ).

All tries gives the same error as i stated before and this the result of connection test:

[Start: Texas Instruments XDS100v1 USB Debug Probe_0]

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\Hosam\AppData\Local\TEXASI~1\CCS\
ccs901\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 'jioserdesusb.dll'.
The library build date was 'Mar 25 2019'.
The library build time was '17:36:26'.
The library package version is '8.1.0.00007'.
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).

-----[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 test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

-----[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
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG IR Integrity scan-test has failed.

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

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
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End: Texas Instruments XDS100v1 USB Debug Probe_0]

 

regards
Hosam

  • Hi Hareesh,
    I know what happen cuz i have used many ti launchpads like, F28379D Delfino, msp430, tivac and so on. my problem with Piccolo as i stated in details.

    regards
    Hosam
  • Hi Hareesh,
    Do u have any new suggestions?

    regards
    Hosam
  • Hosam,
    For all of our control CARDs we typically include a infosheet that has some getting started type info in it. Depending on the version of C2000Ware you have the infosheet for the F28035ISO is located here: C:\ti\c2000\C2000Ware_1_00_06_00\boards\controlCARDs\TMDSCNCD28035ISO\F28035_ISOcontrolCARD_InfoSheet.pdf

    As we read through this document there are two main care-abouts that can cause what you are seeing:

    1)Supplying 5V power to the control CARD: Since this is an isolated JTAG implementation the F28035 MCU does NOT get power from the USB connector on the control CARD, but rather must be supplied 5V from the docking station. You can verify which domain is powered from the LEDs, LD1 indicates the F28035 MCU is powered, LD4 indicates that the XDS100 is powered

    2)SW3 - TRSTn control: Since the TRSTn pin is also dual purposed as a boot pin there is an option to disconnect this pin from the XDS100 for cases when the user wants to boot without an emulation connection(when the flash is programmed for instance). In order to connect to the XDS100 emulator we need to make sure this switch is in the "on" position.

    Let me know if you have completed both the above steps and are still seeing an issue. The app note that Hareesh mentioned will be helpful if we need to debug further.

    Best,
    Matthew
  • Hello Matthew
    Thank u very much for your time. Yes, I have tested your above steps before and right now but still the issue is remaining.

    Thanks
    Hosam
  • Hello Matthew
    Is there any new suggestion?

    Thanks
    Hosam
  • Hello TI employees,
    Is this hardware issue?

    regards
  • Hosam,
    How far were you able to get in the app note that Hareesh mentioned near the beginning of the thread. If you could let me know the step you were able to reach we can start from there. From above it looks like you have confirmed the controlCARD is powered properly.

    Best,
    Matthew
  • Hosam,
    Wanted to check back in with regard to my last post, in terms of using the JTAG debug guide to diagnose the issue.

    Best,
    Matthew
  • Hi Matthew
    thank u for your interest. i wasted too much time checking this board but no success. u can close this thread. 

    regards
    hosam