Why does the Blackhawk USB510 Emulator not work with CCSv5?

Hello Jason,

The USB510 is still supported by us, including for CCS v5, however it is no longer being manufactured.  This is the first issue we are hearing about CCS v5.1.1 and will look into it.  We regularly test with the F28035 target.

Andrew

Here's one further observation.

LD3 will blink (code running) when JTAG connector of Blackhawk USB2000 Controller is plugged in
LD3 will not blink (code not running) when JTAG connector of Blackhawk USB510 Emulator is plugged in

 

Hi, Andrew

I notice a seemingly newer version driver for USB510 on this page: http://www.blackhawk-dsp.com/support/Drivers.aspx . the v4.1.55.0, however, the release date (Aug 2006)seems older than the v3.3. Do you recommand to try out this v4.1.55.0 driver?

thanks,

Clio

Clio,

CCS v4 and later includes all the files and drivers you need as part of the TI distribution.  Updates are avilable via the CCS Eclipse Update Manage (within the application).

Our drivers download page is for CCS v3.3. and earlier.  Don't confuse the old C2xx/vc3x/c4x Code Composer v4 with the newer Code Composer STUDIO v4.

Andrew

Jason,

We tracked down what we believe is the issue and are pursuing the fix.  In the mean time, if we can find something to use as a workaround, I will post it.

The details....We beleive that USCIF v35.34.39.0 (underlying low-level emulation code if you are not familiar) introduced a change causing a problem with the sequence of establishing a good TCK rate.  This issue would affect any CCS version that is updated to USCIF 35.34.39.0 (we found no problem with USCIF v35.34.29.0 and earlier during our testing).  CCS updates that include this change must have been posted recently - we tested CCS v5 and v5.1 extensively before their release.

 

 - Andrew

Hello,

Anyone out there?

Anyone working on this?

It has been quite a while.

I guess I will have to write off Blackhawk on CCS5.

Harry

Hello,

It seems I met the same problem: I try to use “Blackhawk USB510 Emulator” on EVM5515 board under CCSV5.  However, I failed on the very first step – “Test Connection” with target board.   As a compare, we have no problem to use “Blackhawk USB510 Emulator” in our C5509A based board under CCSV3. 

Could any one from Texas Instruments or Blackhawk evaluate this issue and solution?

Jun Cao from Arbitron Inc.

Hello Jun Cao,

This was fixed (approximately) in April/May 2012,  with TI EMUPACK_5.0.693.0.  Sorry, This may have been indicated in another post.

As there is no error here I can only ask that you make sure you have updated your CCS v5 installation with a TI EMUPACK of this version or later.  You can verify by checking installed software.

If problems persist, please email our support directly with the error message.  We can help from there.

Thanks, Andrew

Hi Experts,

Can you please help in finding the issue : error logs are as below-->

Error connecting to the target:
Error 0x80002240/-118
Fatal Error during: Initialization, OCS, Control,
This error was generated by TI's USCIF driver.

SC_ERR_OCS_PORT <-118>
An invalid controller port value has been used.
Thus Unified-SCIF will not attempt to detect a controller
The standard XDS560 ports are 0x0, 0x1, 0x2 and 0x3.
The standard XDS100usb ports are 0x0, 0x1, 0x2 and 0x3.
The standard XDS100pp ports are 0x378, 0x278 and 0x3BC.
The standard XDS510 ports are 0x240, 0x280, 0x320 and 0x340.


I/O Port = 0

Board Name: Blackhawk USB510 - TCI6486-4 cpu Emulator
Cpu Name: ICEPICK_C_0

regards
mahesh mudela

Hello,

The error: SC_ERR_OCS_PORT <-118>, typically means that the emulator has not enumerated with Windows properly and CCS cannot find it.

You can check enumeration in the Windows Device Manager and Blackhawk Control Panel.  If you do not see enumeration, the typical cause is that Blackhawk Emulator support was not installed with CCS.

Regards,

Andrew

Hi,

Window can see the emulator , plz find the attached  scrrenshot.

regards

Hi,

In control panel, I can see emulator is getting identified by driver with ccs3.3,

Some more screen shot to help u further:

regards

anshul

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

 

 

 

 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

 

 

 

 

 

 

 

hi experts,

It looks me If I am running BHprobe AND ALL THE Diagnastic/integrity test goes fine for the BH-510USB jtag emulator.
Somehow when I am using the same with CCSV3.3, then jtag is unbale to communicate with dsp.

Plz suggest the best

thanks


see logs of probe test:
Thu 03/17/2016-11:42:32.48
BHDeviceList: Device Find Started...
BHDeviceList: Searching for Attached PnP Devices
1.) Blackhawk USB510-EBD JTAG Emulator (S/N:USB510-TI)
BHDeviceList: Found [1] device(s) attached to the system.
BHDeviceList: Completed Search for Attached PnP Devices
BHDeviceList: Searching for Installed PnP Devices
1.) Blackhawk USB510-EBD JTAG Emulator (S/N:USB510-TI)
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 USB510 JTAG Emulator
**************************************************
Thu 03/17/2016-11:42:32.68


bin\XDSProbe.exe -F bhemutbc.dll -p0x0 -r -o log\BHprobe_USB510.log

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbc.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'bhemutbc.dll'.
The emulator adapter is titled 'Adapter for use with Blackhawk USB510/PCI510'.
The emulator adapter is version '35.24.0.3'.
The emulator adapter is using 'Block-Mode'.
The controller has a version number of '1' (0x0001).
The controller has an insertion length of '16' (0x0010).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '32768' (0x008000).

Done.

****************************************************************************************************
TEST 2 - SCAN
****************************************************************************************************
**************************************************
BHProbe 5.03: Blackhawk USB510 JTAG Emulator
**************************************************
Thu 03/17/2016-11:42:33.07


bin\XDSProbe.exe -v -F bhemutbc.dll -p0x0 -i -o log\BHprobe_USB510.log

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbc.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'bhemutbc.dll'.
The emulator adapter is titled 'Adapter for use with Blackhawk USB510/PCI510'.
The emulator adapter is version '35.24.0.3'.
The emulator adapter is using 'Block-Mode'.
The controller has a version number of '1' (0x0001).
The controller has an insertion length of '16' (0x0010).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '32768' (0x008000).

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

Done.

****************************************************************************************************
TEST 3 - SCAN2
****************************************************************************************************
**************************************************
BHProbe 5.03: Blackhawk USB510 JTAG Emulator
**************************************************
Thu 03/17/2016-11:42:35.51


bin\XDSProbe.exe -v -f bin\bh-noscantest.cfg -F bhemutbc.dll -p0x0 -i -o log\BHprobe_USB510.log

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbc.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'bhemutbc.dll'.
The emulator adapter is titled 'Adapter for use with Blackhawk USB510/PCI510'.
The emulator adapter is version '35.24.0.3'.
The emulator adapter is using 'Block-Mode'.
The controller has a version number of '1' (0x0001).
The controller has an insertion length of '16' (0x0010).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '32768' (0x008000).

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

Done.

****************************************************************************************************
TEST 4 - DATA
****************************************************************************************************
**************************************************
BHProbe 5.03: Blackhawk USB510 JTAG Emulator
**************************************************
Thu 03/17/2016-11:42:36.57


bin\XDSProbe.exe -v -F bhemutbc.dll -p0x0 -g -o log\BHprobe_USB510.log

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbc.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'bhemutbc.dll'.
The emulator adapter is titled 'Adapter for use with Blackhawk USB510/PCI510'.
The emulator adapter is version '35.24.0.3'.
The emulator adapter is using 'Block-Mode'.
The controller has a version number of '1' (0x0001).
The controller has an insertion length of '16' (0x0010).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '32768' (0x008000).

-----[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 Given Data scan-test on the JTAG IR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.
It uses the first 1 of the 10 different test-cases.

Do a test using 0x5533CCAA.
Scan tests: 1, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Given Data scan-test has succeeded.

-----[Perform the Given Data scan-test on the JTAG DR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.
It uses the first 1 of the 10 different test-cases.

Do a test using 0x5533CCAA.
Scan tests: 1, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Given Data scan-test has succeeded.

Done.

Thank you for the bhprobe output, which shows that the emulator is installed and working properly.  I could not see the screen shots, but that is OK, since the emulator is recognized by Windows.

At this point I would normally say that CCS v3.3 setup must be the problem, but the information provided in your initial post with the error, looks correct - proper emulator declared and I/O port.

I suggest you download an run our BHDetect utility and email the output file to Blackhawk support for analysis.  That will be easier than trying to read it inside this post unless you can attach the file for download.

Andrew

Regards,
Andrew

hi Andrew,

See the jtags logs after updating the driver

/////////////////////////////////////logs//////////////////////////////

Error connecting to the target:
Error 0x80002240/-233
Fatal Error during: Initialization, OCS, Control,
This error was generated by TI's USCIF driver.

SC_ERR_PATH_BROKEN <-233>
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.

I/O Port = 0

Board Name: Blackhawk USB510 - TCI6486-4 cpu Emulator
Cpu Name: ICEPICK_C_0

Abort: Close Code Composer Studio.
Retry: Try to connect to the target again.
Cancel: Remain disconnected from the target
Diagnostic: Run diagnostic utility.

//////////////////////////////////////////////////////

Does it mean there is hardware connectivity issue , cpu is not reached through this path???

please helps.

regards

mahesh

hi,

This is probe results:

probe result:

BHProbe: Blackhawk USB510 JTAG Emulator

**************************************************
21-03-2016-17:49:42.86

bin\XDSProbe.exe -F bhemutbc.dll -p0x0 -r -o log\mahesh_log.txt

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'bhemutbc.dll'.
This utility will operate on port address '0'.

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

This error is generated by TI's USCIF driver.

The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

Done.

regards
mahesh