• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 704 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Connect Target vs. Connect Device

Nicholas Parker
Intellectual 320 points
Other Parts Discussed in Thread: CCSTUDIO

 

Hello,

I have been having connection problems with my BlackHawk USB2000 controller (Code Composer 3.3) and a digtially controlled (2808) power supply I am working on, for some time now.  Sometimes things can be 'fixed' by unplugging and re-plugging USB, even several times ocassionally. Frequently my PC resets when forcing the CCStudio Parallel Dbug Window to close, because it is "hanging".  But things have really come to a head now,  I have a collection of 4 USB2000's on my desk and have tried several target boards also with no success in connecting.  Specifically I get the following error :-

Error connecting to the target:
Error 0x80000200/-1047
Fatal Error during: OCS,
PTI_ERR_EMU_CLOSE Error Occured at 0x00000000

I/O Port = 0

Board Name: Blackhawk USB2000 - C28x Controller
Cpu Name: TMS320C2800_0

I have Googled this and found many hits - many people having the same problems as me, but nothing very helpful.

I have noticed in the "CCStudio Parallel Debug Manager" window that depending on whether I right click the "Blackhawk USB2000 - F2808 Controller"  or  "TMS320C2800_0" I get "Connect Target" and "Connect Device" respecitvely.      What is the difference?    In my case there are RED crosses through both option's icons (to the left hand side of the label).

Is there a diagnostic utility I can use to determine the problem with the JTAG interface? 

I have run the Blackhawk utility "BHCheck33.exe" which recommends no actions, as everything (CCStudio and Driver versions) is apparently OK.

Is there a simple process I can follow to verify the JTAG interface with my oscilloscope to find out why I cannot connect to my target (or device?)  A preliminary check of several lines (TRST, TDI/O etc) seemed to show no activity on the JTAG lines when trying to connect, but in windows, under device manager I can see device is "working correctly"

Nick.

 

 

  • TI__Guru**** 465171 points

    Hello Nick,

    First of all, sorry for the delayed response.

    Nicholas Parker said:
    I have been having connection problems with my BlackHawk USB2000 controller (Code Composer 3.3)

    Can you confirm you have the latest blackhawk drivers for CCSv3.3 and are using the latest CCSv3.3 service release? If not, could you upgrade to them and try again?

    Nicholas Parker said:

    Is there a diagnostic utility I can use to determine the problem with the JTAG interface? 

    I have run the Blackhawk utility "BHCheck33.exe" which recommends no actions, as everything (CCStudio and Driver versions) is apparently OK.

    Have you tried BHProbe?

    http://www.blackhawk-dsp.com/support/Software.aspx#BHProbe

    ki

     

     

     

  • in reply to Ki
    Prodigy 40 points

    I have the same error. Link below for the error log file.

     

    Fullscreen 4466.BHprobe_USB2000.log Download 
    2014/10/16 �g�|- 9:31:20.05 
BHDeviceList:  Device Find Started...
BHDeviceList:  Searching for Attached PnP Devices
		 1.) Blackhawk USB2000 Controller (S/N:MD3589)
BHDeviceList:  Found [1] device(s) attached to the system.
BHDeviceList:  Completed Search for Attached PnP Devices
BHDeviceList:  Searching for Installed PnP Devices
		 1.) Blackhawk USB2000 Controller (S/N:MD3589)
BHDeviceList:  Found [1] device(s) installed on this system.
BHDeviceList:  Completed Search for Installed PnP Devices
BHDeviceList:  Device Find Completed.
**************************************************************************************************** 
TEST 1 - RESET 
**************************************************************************************************** 
************************************************** 
  BHProbe 5.03: Blackhawk USB2000 JTAG Emulator   
************************************************** 
2014/10/16 �g�|- 9:31:20.25										
													
													
bin\XDSProbe.exe -v -F bhemutbcl.dll -p0x0 -r -o log\BHprobe_USB2000.log 

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbcl.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

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

This error is generated by TI's USCIF driver.

The value is '-182' (0xffffff4a).
The title is 'SC_ERR_CTL_CBL_BREAK_NEAR'.

The explanation is:
The controller has detected a cable break that is near-to itself.
The user must connect the cable/pod to the controller.
		
Done.	
		
**************************************************************************************************** 
TEST 2 - SCAN  
**************************************************************************************************** 
************************************************** 
  BHProbe 5.03: Blackhawk USB2000 JTAG Emulator   
************************************************** 
2014/10/16 �g�|- 9:31:21.62										
													
													
bin\XDSProbe.exe -v -F bhemutbcl.dll -p0x0 -i -o log\BHprobe_USB2000.log 

-----[Print the controller-open software log-file]---------------------------

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbcl.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

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

This error is generated by TI's USCIF driver.

The value is '-182' (0xffffff4a).
The title is 'SC_ERR_CTL_CBL_BREAK_NEAR'.

The explanation is:
The controller has detected a cable break that is near-to itself.
The user must connect the cable/pod to the controller.
		
Done.	
		
**************************************************************************************************** 
TEST 3 - SCAN2 
**************************************************************************************************** 
************************************************** 
  BHProbe 5.03: Blackhawk USB2000 JTAG Emulator   
************************************************** 
2014/10/16 �g�|- 9:31:21.89										
													
													
bin\XDSProbe.exe -v -f bin\bh-noscantest.cfg -F bhemutbcl.dll -p0x0 -i -o log\BHprobe_USB2000.log 

-----[Print the controller-open software log-file]---------------------------

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbcl.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

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

This error is generated by TI's USCIF driver.

The value is '-182' (0xffffff4a).
The title is 'SC_ERR_CTL_CBL_BREAK_NEAR'.

The explanation is:
The controller has detected a cable break that is near-to itself.
The user must connect the cable/pod to the controller.
		
Done.	
		
**************************************************************************************************** 
TEST 4 - DATA 
**************************************************************************************************** 
************************************************** 
  BHProbe 5.03: Blackhawk USB2000 JTAG Emulator   
************************************************** 
2014/10/16 �g�|- 9:31:22.12										
													
													
bin\XDSProbe.exe -v -F bhemutbcl.dll -p0x0 -g -o log\BHprobe_USB2000.log 

-----[Print the controller-open software log-file]---------------------------

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbcl.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

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

This error is generated by TI's USCIF driver.

The value is '-182' (0xffffff4a).
The title is 'SC_ERR_CTL_CBL_BREAK_NEAR'.

The explanation is:
The controller has detected a cable break that is near-to itself.
The user must connect the cable/pod to the controller.
		
Done.

     Please help to solve it, thank you.