I have a custom board from a vendor. The board has 20 TI c6678 chips on it and it has 10 of them each accessible through two JTAG pin connections on the board. I am using windows XP and the TI Code composer studio version is 5.2.1.00018. My emulator is a BH 560USBm and I have it connected correctly to the board and have it powered up (checks with troubleshooting guide on Blackhawk webpage). It has also enumerated correctly as I can run device manager on my PC and it shows the correct icons and information. I then managed to go to the ccsv5\cs_base\emulation\Blackhawk\Utility\BHProbe.2\ and run the BHprobe_USB560m dos batch file. Results are below and were successful. I also ran the \Blackhawk\Utility\BHDetect and the output is below – again results seem successful. I then opened up CCS studio and View-Target configuration and created a new connection and selected BH 560USBm. I then added 10 DSP c6678 chips each showing 8 cores. My ccxml file is enclosed. It is very similar to the ccxml file I obtained from the board manufacturer except they were using a 560v2 spectrum digital emulator. I then used the test connection on the CCS studio v5.2.1 View-Target Configuration window and the results are enclosed with errors. I did try to connect to the target but got an error which is to be expected. Can you please provide some insight into what could be wrong. I am unable to attach the ccxml file as e2e does not allow for it to be attached. I can provide it offline if need be.
Thanks, Aamir
Thanks, Aamir
Output of BHProbe_USB560m batch file run in DOS
16/05/2013-15:07:40.65
****************************************************************************************************
TEST 1 - RESET
****************************************************************************************************
**************************************************
BHProbe 5.01: Blackhawk USB560m JTAG Emulator
**************************************************
16/05/2013-15:07:40.68
bin\XDSProbe.exe -v -F BH560USBm.out -p0x0 -r -o log\BHprobe_USB560m.log
-----[Print the reset-command software log-file]-----------------------------
This utility has selected an XDS560 class product.
This utility will load the program 'BH560USBm.out'.
This utility will operate on port address '0'.
The controller does use a programmable FPGA.
The old VHDL code has a version number of '1544' (0x0608).
The new VHDL code has a version number of '1544' (0x0608).
The emulator program is named 'BH560USBm.out'.
The emulator program is version '35.24.0.3'.
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 '2' (0x0002).
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 '32768' (0x008000).
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 software is configured to use all Nano-TBC VHDL features.
The controller type is the Nano-TBC VHDL.
The connection type is a 560-class revision-B fixed-use old-PLL cable.
The controller will be software reset via its configure register.
The controller will use rising-edge timing on output pins.
The controller may use rising edge timing on input pins.
The controller has a logic ONE on its EMU[0] input pin.
The controller has a logic ONE on its EMU[1] input pin.
The scan-path link-delay has been set to exactly '3' (0x0003).
The support logic has not previously detected a power-loss.
Done.
****************************************************************************************************
TEST 2 - SCAN
****************************************************************************************************
**************************************************
BHProbe 5.01: Blackhawk USB560m JTAG Emulator
**************************************************
16/05/2013-15:07:41.75
bin\XDSProbe.exe -v -F BH560USBm.out -p0x0 -i -o log\BHprobe_USB560m.log
-----[Print the controller-open software log-file]---------------------------
This utility has selected an XDS560 class product.
This utility will load the program 'BH560USBm.out'.
This utility will operate on port address '0'.
The controller does use a programmable FPGA.
The emulator program is named 'BH560USBm.out'.
The emulator program is version '35.24.0.3'.
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 '2' (0x0002).
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 '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 60 bits.
The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 10 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.01: Blackhawk USB560m JTAG Emulator
**************************************************
16/05/2013-15:07:45.00
bin\XDSProbe.exe -v -f bin\bh-noscantest.cfg -F BH560USBm.out -p0x0 -i -o log\BHprobe_USB560m.log
-----[Print the controller-open software log-file]---------------------------
This utility has selected an XDS560 class product.
This utility will load the program 'BH560USBm.out'.
This utility will operate on port address '0'.
The controller does use a programmable FPGA.
The emulator program is named 'BH560USBm.out'.
The emulator program is version '35.24.0.3'.
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 '2' (0x0002).
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 '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 60 bits.
The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 10 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.01: Blackhawk USB560m JTAG Emulator
**************************************************
16/05/2013-15:07:46.96
bin\XDSProbe.exe -v -F BH560USBm.out -p0x0 -g -o log\BHprobe_USB560m.log
-----[Print the controller-open software log-file]---------------------------
This utility has selected an XDS560 class product.
This utility will load the program 'BH560USBm.out'.
This utility will operate on port address '0'.
The controller does use a programmable FPGA.
The emulator program is named 'BH560USBm.out'.
The emulator program is version '35.24.0.3'.
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 '2' (0x0002).
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 '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 60 bits.
The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 10 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.
Output of BH Detect
16:14:02: BHDetect - Version 1.0.0.11
16:14:02:
16:14:02: Scan started on Thursday, May 16, 2013 at 04:14:02 PM.
16:14:02:
16:14:02:
16:14:02: SYSTEM INFORMATION:
16:14:02: -------------------
16:14:02: Computer Name: BC-DSPDEBUG
16:14:02: User Name: dspuser
16:14:02: OsVersionInfo: Platform=2 (0=WIN32s, 1=WIN32_WINDOWS, 2=WIN32_NT)
16:14:02: Major.Minor=5.1; Build=2600 (if Platform=2: 5.0=W2K, 5.1=XP, 5.2=2003Server, 6.x=Vista or later)
16:14:02: (if Platform=1: 4.0=W95, 4.10=W98, 4.90=WMe)
16:14:02: CSD=[Service Pack 3], SP Major=3, SP Minor=0, Suite=256, Product=1
16:14:02: Processor Architecture=0 (INTEL=0 MIPS=1 ALPHA=2 PPC=3 SHX=4 ARM=5 IA64=6 ALPHA64=7 MSIL=8 AMD64=9 IA32onWIN64=10)
16:14:02: Wow64 Process: OS is Running 32-bit version.
16:14:02: -------------------
16:14:02:
16:14:02: SCANNING OPTIONS SELECTED:
16:14:02: --------------------------
16:14:02: + Scanning for CCS v3.3 and earlier.
16:14:02: + Scanning for CCS v4 or later.
16:14:02: --------------------------
16:14:03:
16:14:03: SCANNING CCS v3.3 and EARLIER:
16:14:03: ------------------------------
16:14:03:
16:14:03: Starting Quick Scan for CCStudio v3.3 and earlier Installations...
16:14:03:
16:14:03: %%ERROR: bhDetect_GetIniFile() opening ComponentManager registry key.
16:14:03: bhDetect_ListCCSInstallations: Error locating CCStudio Component Manager INI file.
16:14:03: bhDetect_ListCCSInstallations: No valid CCS v3.3 and earlier installations found.
16:14:03: ------------------------------
16:14:03:
16:14:04:
16:14:04: SCANNING CCS v4 or LATER:
16:14:04: --------------------------
16:14:04:
16:14:04: Starting Quick Scan for CCStudio v4 (or later) Installations...
16:14:04:
16:14:04: bhDetect_FindCCv4Installations: Program Files path: C:\Program Files\.
16:14:04: bhDetect_ListCCSv4Installations: No valid CCS v4 (or later) installations found.
16:14:04: --------------------------
16:14:04:
16:14:04:
16:14:04: Starting scan for installed Blackhawk Driver Files...
16:14:04:
16:14:04: Processing NON-SYS Files...
16:14:04: + Checking in System Folder: C:\WINDOWS\System32.
16:14:04: blackhwk.cpl, v01.01.00.00, 155440 bytes, Wed Feb 08 06:09:15 2012
16:14:04:
16:14:04: Processing SYS Files...
16:14:04: + Checking in System Folder: C:\WINDOWS\system32\drivers.
16:14:05: bh560eth.sys, v01.00.00.09, 97776 bytes, Wed Nov 17 14:05:14 2010
16:14:05: bh560usb.sys, v01.10.00.00, 318640 bytes, Wed Feb 08 06:09:14 2012
16:14:05:
16:14:05: Starting scan for Blackhawk Emulators...
16:14:05:
16:14:05: 1.) Blackhawk USB560M JTAG Emulator (S/N:HC7174)
16:14:05:
16:14:05: Completed scan for Blackhawk Emulators.
16:14:06:
16:14:06: Scan Completed Successfully on Thursday, May 16, 2013 at 04:14:06 PM.
16:14:06:
16:14:06: ******************************************************************************
16:14:06: BHDetect - Version 1.0.0.11 Errors: 1, Warnings: 0
16:14:06: ******************************************************************************
16:14:06: BHDetect has completed a scan of your system. The output generated in the
16:14:06: dialog box window is designed to help debug installation and setup problems.
16:14:06: Any messages that begin with "%ERROR" should be addressed and you can
16:14:06: contact Blackhawk support via email: support@blackhawk-dsp.com and include
16:14:06: the output from this utility for faster response.
16:14:06:
16:14:06: Thank you, The Blackhawk Support Team.
16:14:06: ***************************************************************************EOF.
Output of test connection from CCS studio v5.2.1 View->Target Configuration window
[Start]
Execute the command:
%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\DOCUME~1\dspuser\LOCALS~1\APPLIC~1\.TI\
3823558504\0\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 560/2xx-class product.
This utility will load the program 'bh560usbm.out'.
Interface uscif not exported by C:\ti\ccsv5.2.1\ccsv5\ccs_base\common\uscif\uscif.out
An error occurred while soft opening the controller.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.
The explanation is:
An attempt to access the named emulator via USCIF ECOM has failed.
[End]
