H63C2 Error Connection to the target

Mustafa Bayram

Other Parts Discussed in Thread: CONTROLSUITE, F28M36P63C2

Hello I have tried to debug blinky_c28 but i got error message. I'm new in these issues. Is this my target configuration or connection error. Can the kit has been damaged? I have gotten all the ESD precautions. Besides that, it is new. Could you please help me to start to use this kit. I am waiting for your help. thank you

over 11 years ago

0 Gautam Iyer over 11 years ago

Guru 192875 points

Hi,

Don't worry. Can you please attach screenshot of the error? This would help me check into the issue.

Regards,

Gautam.

0 Mustafa Bayram over 11 years ago in reply to Gautam Iyer

Prodigy 105 points

I have attached the screenshot.

thank you Guatam

0 Gautam Iyer over 11 years ago in reply to Mustafa Bayram

Guru 192875 points

One thorough check you'll have to do is: check all the voltage levels on the board wrt the schematics controlSuite. Check if any of the hardware components are getting over heated esp. MCU and LDO.

Also check this link out for XDS100 troubleshooting :

http://processors.wiki.ti.com/index.php/XDS100

Regards,

Gautam

0 Mustafa Bayram over 11 years ago in reply to Gautam Iyer

Prodigy 105 points

I will review the situation and report.

thanks a lot :)

0 Mustafa Bayram over 11 years ago in reply to Mustafa Bayram

Prodigy 105 points

Problem not solved :(

I think, it shouldn't be challenging. it should be plug and play, like the mps430.

TARGET TEST RESULT :

[Start]

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\HP\AppData\Local\.TI\693494126\
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 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.0'.
The library component version is '35.34.40.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 512 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 512 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 512 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] like the MPS30 launchpad, does it? I think, it shouldn't be challenging.

0 Brett Larimore over 11 years ago in reply to Mustafa Bayram

TI__Guru 57255 points

Mustafa,

If you have not already, take a look at the controlCARD infosheet found at the below once controlSUITE is installed:
\controlSUITE\development_kits\~controlCARDs\TMDSCNCD28M36_v1_2\R1_1\

The key things to check are:
* the USB mini cable is plugged in (A:D2 will turn on)
* the MCU receives power (D3 will turn on)
* A:SW1 is configured the right way.

Thank you,
Brett

0 Mustafa Bayram over 11 years ago in reply to Brett Larimore

Prodigy 105 points

I have imported blinky project for c28 from the v201 controlsuite folder. my test setup is in the picture attached. ,

Debug has started and finished with the error messeages which can be seen in the picture attached. And nothing has happened on the board. what is "Error during DVT action : ......." ?

Thank you to everyone who tried to help me.

I think target test is correct now, am I right. what is my fault now and how can i fix it?

[Start]

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\MB26C0~1.BAY\AppData\Local\.TI\
693494126\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 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.0'.
The library component version is '35.34.40.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 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

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

This test will use blocks of 512 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.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

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

This test will use blocks of 512 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.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End]

0 Brett Larimore over 11 years ago in reply to Mustafa Bayram

TI__Guru 57255 points

Mustafa,

The debugger now appears to be working. So you are getting closer.

A few thoughts:
1) What is your CCS target configuration?
(it should be 'Texas Instuments XDS100v2 USB Emulator' + 'F28M36P63C2')

2) Can you try the M3 blinky example and see if you get the same issues?

3) Note that in order to get the C28 blinky example to work you will also need to load and run the 'setup_m3' example on the M3. The M3 on the Concerto devices is the master and must give resources (like GPIO pins) to the C28x core in order for it to do much.

Thank you,
Brett

0 Mustafa Bayram over 11 years ago in reply to Brett Larimore

Prodigy 105 points

1) target configuration is correct.

2) M3 blinky works this is good :)

3) where can i find 'setup_m3' example

and "H63C2 Error Connection to the target" problem is solved

then my new problem is how to use it :)

Thanks a lot.

0 Brett Larimore over 11 years ago in reply to Mustafa Bayram

TI__Guru 57255 points

Hello Mustafa,

3) The setup_m3 example can be found here:
\controlSUITE\device_support\f28m36x\v???\F28M36x_examples_Control\setup_m3\

Thank you,
Brett

0 Mustafa Bayram over 11 years ago in reply to Brett Larimore

Prodigy 105 points

Hello Brett

It is working now.

Thanks to everyone who helped me.

Mustafa

C2000™︎ microcontrollers

C2000 microcontrollers forum

H63C2 Error Connection to the target