Error in connecting Motor Control and PFC Developer's Kit

KinLok,

The connection may be failing for several reasons, including a hardware problem; the page below explains how to use the low-level connect utility dbgjtag, which is useful to rule out any CCS issues.

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

If the utility above is also failing, then you may have a hardware problem. If you have another emulator available can you try connecting to it?

Also, can you carefully inspect the jumpers on your dev kit? I have a high-voltage motor control kit and I keep having problems because I change the jumper configurations everytime and forget to put them back....

Hope this helps,

Rafael 

Hi Rafael

I double checked all jumpers, they were in their default states. The USB cable I used was in good condition.

I ran several tests using dbgjtag, and got following error messages :

C:\CCStudio_v3.3\cc\bin>dbgjtag -f brddat\ccbrd0.dat -rv -S pathlength

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'jioserdesusb.dll'.
The emulator adapter is titled '(null)'.
The emulator adapter is version '(null)'.
The emulator adapter is using 'Normal-Mode'.
The controller has a version number of '4' (0x0004).
The controller has an insertion length of '0' (0x0000).
The cable+pod has a version number of '0' (0x0000).
The cable+pod has a capability number of '0' (0x0000).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '1048576' (0x100000).
This utility will now attempt to reset the controller.
This utility has successfully reset the controller.

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

The bridge library used to access the controller
and adapter does not read their log-files.

-----[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.

C:\CCStudio_v3.3\cc\bin>dbgjtag -f brddat\ccbrd0.dat -rv -S brokenpath

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'jioserdesusb.dll'.
The emulator adapter is titled '(null)'.
The emulator adapter is version '(null)'.
The emulator adapter is using 'Normal-Mode'.
The controller has a version number of '4' (0x0004).
The controller has an insertion length of '0' (0x0000).
The cable+pod has a version number of '0' (0x0000).
The cable+pod has a capability number of '0' (0x0000).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '1048576' (0x100000).
This utility will now attempt to reset the controller.
This utility has successfully reset the controller.

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

The bridge library used to access the controller
and adapter does not read their log-files.

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

This error is generated by TI's USCIF driver.

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.

Did these error messages told what was going wrong in my board ?

Regards,

Kinlok

Kinlok,

The message indicates the JTAG emulator is detecting some data channels are stuck in high ("stuck-at-ones"). This is can be caused by several factors, among them pull-up resistors shorted or a damage to the JTAG isolation circuit (the kit you are using has one).

If you have an external emulator you can try to connect to the development kit and see if you get a different result (don't forget to put a jumper in J5 to disable the existing one); otherwise a hardware repair will be needed.

Unfortunately I am not the most knowledgeable person to talk about this development board, but a quick glance at the schematics for my dev kit (yours may be similar) show that either one of the two ISO724x parts may be damaged. You may have better luck asking the experts in the C2000 forum, as they have better understanding about this.

Hope this helps, 

Rafael

Hi, I also have a very similar problem with "High Voltage Motor Control and PFC Developer's Kit" (TMDSHVMTRPFCKIT).

• I'm using Code Composer Studio Version: 4.2.1.00004 on Win7 (64bit).
• USB cable works good and double checked jumper and connection.
• TI XDS100 Channel A, TI XDS100 Channel B are detected normally.
• Board TMDSHVMTRPFCKIT is new and never been used. 
• Bulding of a simple "Hello Word" .c file works good.
• Board is supplied.

When try to connect  target (Alt+C), CCS displays following error:

"Error connecting to the target:

Error 0x00001200/-1135

Error during: OCS, Target, 

Unrecoverable emulation error"

Clicking on "Retry" button, CCS says:

"Error connecting to the target:

Error 0x80000200/-1041

Fatal Error during: OCS, 

Device driver: Problem with the Emulation Controller.

It is recommended to RESET EMULATOR.  This will disconnect each 

target from the emulator.  The targets should then be power cycled

or hard reset followed by an emureset and reconnect to each target."

Clicking on "Retry" button n-times, CCS always says:

"Error connecting to the target:

Error 0x80000200/-1041

Fatal Error during: OCS, 

Device driver: Problem with the Emulation Controller.

It is recommended to RESET EMULATOR.  This will disconnect each 

target from the emulator.  The targets should then be power cycled

or hard reset followed by an emureset and reconnect to each target."

I've tested JTAG with "dbgjtag" as follow:

Entering:

• "C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif\ccBoard0.dat" -rv -S brokenpath

dbgjtag says:

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

This utility has selected a 100- or 510-class pr

This utility will load the adapter 'jioserdesusb

The library build date was 'Sep  1 2010'.

The library build time was '03:03:45'.

The library package version is '5.0.158.0'.

The library component version is '35.34.29.0'.

The controller does not use a programmable FPGA.

The controller has a version number of '4' (0x00

The controller has an insertion length of '0' (0

This utility will now attempt to reset the contr

This utility has successfully reset the controll

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

The scan-path will be reset by toggling the JTAG

The controller is the FTDI FT2232 with USB inter

The link from controller to target is direct (wi

The software is configured for FTDI FT2232 featu

The controller cannot monitor the value on the E

The controller cannot monitor the value on the E

The controller cannot control the timing on outp

The controller cannot control the timing on inpu

The scan-path link-delay has been set to exactly

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

This error is generated by TI's USCIF driver.

The value is '-233' (0xffffff17).

The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:

The JTAG IR and DR scan-paths cannot circulate b

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."

Entering:

• "C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif\ccBoard0.dat" -rv -S pathlength

dbgjtag says:

"-----[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 'Sep  1 2010'.

The library build time was '03:03:45'.

The library package version is '5.0.158.0'.

The library component version is '35.34.29.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 now 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).

-----[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."

Entering:

• "C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\Program Files (x86)\Texas Instruments\ccsv4\common\uscif\ccBoard0.dat" -rv -S integrity

dbgjtag says:

"-----[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 'Sep  1 2010'.

The library build time was '03:03:45'.

The library package version is '5.0.158.0'.

The library component version is '35.34.29.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 now 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).

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

This error is generated by TI's USCIF driver.

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."

As posted in the previous post by Rafael, there could be several factors that contribute to the JTAG emulator detecting some scan paths to be stuck in high. If you have access to an external emulator that you can connect to the kit, that might be a good test to try. Also please check the XDS100 page, specifically the section on Troubleshooting, which describes how to check that the VID/PID for the EEPROM is programmed properly: http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting_FAQ

Just started to work with the High Volatge Motor control and RFC Kit  Get the SAME results as the other user here..  And what I'm hearing is that the Kit may NOT be proper manufactured and I need to buy some more hardware from TI to possibily fix the problem.

ALSO where is the Board Congif  file located.. I have searched in the locations mentioned above and also a hard drive search without success..

FYI M Emulator config as per the TI doc

David,

Please check that the VID/PID for the XDS100 is programmed to the correct values - there are FAQs and details in this page on how to reprogram the EEPROM (if the values are not as expected):
http://processors.wiki.ti.com/index.php/XDS100#Q:_I_got_an_.22Error_connecting_to_the_target:_Error_0x80000240.2F-151_Fatal_Error_during:_Initialization.2C_OCS.22_when_trying_to_connect_to_the_target_in_Code_Composer_Studio_v4

This related forum post might also be helpful:
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/43494/301465.aspx#301465

Aarti

 I check tVID/PID 2 two days agao it was correct then ;-)

The link didn't correct the problem.. It appears to be a number of problems that are being hit, includeing updating CCv4

My Log file..

8867.dbgview_log.LOG

Fixed

Thanks Dave

So the CCS connection issue to the motor control kit is fixed? I'm curious to hear what fixed the issue. Was it reprogramming the VID/PID?

Hi, I also have a very similar problem with "High Voltage Motor Control and PFC Developer's Kit" (TMDSHVMTRPFCKIT) with external JTAG emulator

I'm using CCS v4.2.3.00004 on Win7 (64bit) also  CCS v3.3 with "High Voltage Motor Control and PFC Developer's Kit"  via USB cable on  (TI XDS100 Emulator) works good but  if I want to use external JTAG (XDS510 USB) emulator, it's not work. I double checked jumper and connection according to "HVMotorCtrl+PFCKit_HowToRunGuide.pdf" and "HVMotorCtrl+PFC_HWGuide.pdf".

The external JTAG (XDS510 USB) emulator is good work other dsp boards..

THE CONNECTION ERROR:

Error connecting to the target:

Error 0x80002280/-1250

Fatal Error during: Target Communication, OCS, Control, 

Device driver: Lost USB connection to emulator.

You should ABORT and restart to re-establish the USB link.

I/O Port = 510

Board Name: F28335 XDS510USB Emulator

Cpu Name: cpu_0

Abort: Close Code Composer Studio.

Retry: Try to connect to the target again.

Cancel: Remain disconnected from the target

Diagnostic: Run diagnostic utility.

I can summarize the problems interested in this High Voltage kit as follows:

1. External JTAG emulator (XDS510) does not work with this kit. We expect TI will solve this problem, because there van be many reasons for users to engage in using XDS510.

"I dont know whether XDS510 works with Low Voltage kit, i will try"

2. Motor parameters are almost completely fault. Besides, TI does not have any basis on this, even worse, Estun refuses to give any information to final customers. I tried it, but i could not succeed.

3. The softwares for both High voltage and Low voltage kits are in per unit format. So, you can not make any modifications over them.

4. I appreciate TI because of releasing such high quality and low cost kits. However, It is clear ther is the need for improving them, specially the problems interested in motor paremeters (not only 400W but also 50W) and XDS510 problems.

Dear Community,

I solved the problem some months ago. 

I've made ​​a mistake in interpreting the operation of the jumpers.

Re-reading the instructions I was able to correctly program the target. 

Unfortunately I do not remember what were the jumpers in question but I hope to give hope to those facing this error: recheck the jumpers ...even if you have already double checked!!

Davide

Hi, after so amny analysis, i am still getting same error:

Recently i have bought DRV C2 8412 kit, while connecting the h/w with XDS100 JTAG, i am facing so many problems.

1. unrecoverable error, 
solutions, to recover this, i changed CMS settings, again i faced one more error. ()


2. C28xx: Error connecting to the target: (Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.663.0) 


3. while running DBJTAG :
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.

Kindly help me pls