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.

Error while opening CCStudio

Other Parts Discussed in Thread: CCSTUDIO

Hi all,

I am using CCstudio 3.3v to test DSP (TMS320TCI6482) in one of our custom boards.

I do the following procedures.

Open Setup CCStudio v3.3 >> load ccs file >> Save and Quit to start CCStuio.

Before starting CCStudio it hangs by showing following errror.


Board Name: TMS
Cpu Name: ICEPICK_C_0
Abort:        Close Code Composer Studio.
Retry:        Try to initialize the emulator again.
Ignore:        Ignore the initialization error and start
        potentially without target debugging access.
Diagnostic:    Run diagnostic utility.

I use Blackhawk560Bp emulator to connect to target.

I tried by updating the drivers of blackhawk as well as CCS.

Attached logs of the BHDetect and BHProbe utilities.

I tried by Kindly request anybody could resolve this issue.

thanks & regards,

Pradeepa

 

 
************************************************** 
													
  BHProbe: Blackhawk USB560bp JTAG Emulator   
													
************************************************** 
Thu 04/28/2011-10:46:46.71										
													
													
bin\XDSProbe.exe -v -F BH560Ubp.out -p0x0 -r -o log\BHprobe_USB560bp.log 

-----[Select and reset the controller]---------------------------------------

This utility has selected an XDS560 class product.
This utility will load the program 'BH560Ubp.out'.
This utility will operate on port address '0x0'.

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.

The value is `-253' (0xffffff03).
The title is: `SC_ERR_ECOM_NO_USCIF'.

The explanation is:
The USCIF ECOM interface is missing or invalid.
		
Done.	
		
************************************************** 
													
  BHProbe: Blackhawk USB560bp JTAG Emulator   
													
************************************************** 
Thu 04/28/2011-10:46:48.13										
													
													
bin\XDSProbe.exe -v -F BH560Ubp.out -p0x0 -i -o log\BHprobe_USB560bp.log 

-----[Select the controller]-------------------------------------------------

This utility has selected an XDS560 class product.
This utility will load the program 'BH560Ubp.out'.
This utility will operate on port address '0x0'.

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.

The value is `-254' (0xffffff02).
The title is: `SC_ERR_ECOM_EMUNAME'.

The explanation is:
Cannot access the specified emulator.
The emulator program is missing or
the device number is invalid.
Connect failure
		
Done.	
		
************************************************** 
													
  BHProbe: Blackhawk USB560bp JTAG Emulator   
													
************************************************** 
Thu 04/28/2011-10:46:48.41										
													
													
bin\XDSProbe.exe -v -F BH560Ubp.out -p0x0 -g -o log\BHprobe_USB560bp.log 

-----[Select the controller]-------------------------------------------------

This utility has selected an XDS560 class product.
This utility will load the program 'BH560Ubp.out'.
This utility will operate on port address '0x0'.

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.

The value is `-254' (0xffffff02).
The title is: `SC_ERR_ECOM_EMUNAME'.

The explanation is:
Cannot access the specified emulator.
The emulator program is missing or
the device number is invalid.
Connect failure
		
Done.	
		
10:47:38: BHDetect - Version 1.0.0.7
10:47:38:  
10:47:38: Scan started on Thursday, April 28, 2011 at 10:47:38 AM.
10:47:38:  
10:47:38: FSHWPC2
10:47:38: admin
10:47:39:  
10:47:39: Starting scan for CCStudio Installations...
10:47:39:  
10:47:39: C:\Program Files\Common Files\Texas Instruments\ccs_compdb.ini
10:47:39:  
10:47:39: [CcsInstallation_1]
10:47:39:    INI File Path: C:\CCStudio_v3.3\
10:47:39:    Registry File Key: C:|CCStudio_v3.3|
10:47:39:    PoductName: Code Composer Studio v3.3
10:47:39:   *Version: 3.3.38.2
10:47:39:    Family: [not defined]
10:47:39:   *Collected Info: Code Composer Studio v3.3, 3.3.38.2, [C:\CCStudio_v3.3\]
10:47:39: 
10:47:39:       *  Collected Info and Version does not always correclty reflect
10:47:39:          applied CCStudio updates, patches, or service releases.  You
10:47:39:          may need to check Help->About from within the CCS application.
10:47:39:          You can also check below for the #SKU flag if this is CCS v3.3.
10:47:39: 
10:47:39:  
10:47:39:    Processing CCS Location: C:\CCStudio_v3.3\
10:47:39:  
10:47:39:       Determining TI USCIF Version installed...
10:47:39:          TI USCIF Version: 35.23.10.2
10:47:40:  
10:47:40:       Processing Key Files...
10:47:40:        + TI Key Files...
10:47:40:  
10:47:40:                       xdsfast3.dll, v35.23.10.02,     360448 bytes, Thu Aug 17 14:49:38 2006

10:47:40:                       xdsprobe.exe, v35.23.10.02,      90112 bytes, Thu Aug 17 14:49:40 2006

10:47:40:                    XDS560_ecom.dll, v02.06.01.00,     102400 bytes, Thu Aug 17 14:36:42 2006

10:47:40:  
10:47:40:        + BLACKHAWK Key Files...
10:47:40:  
10:47:40:  
10:47:40: %ERROR: GetFileVersion: Could not locate file (Error: 0x2)
10:47:40:            File: C:\CCStudio_v3.3\cc\bin\bhemu.dll.
10:47:40:       This is normal if Blackhawk XDS510 Emulation Drivers are not installed.
10:47:40:       (i.e. You are using only a Blackhawk XDS560 emulator.)
10:47:40:                       BHTProbe.exe, v01.00.00.00,     307200 bytes, Mon Dec 11 13:18:48 2006

10:47:40:  
10:47:40:       Processing XDS560 OUT Files...
10:47:40:                       bh560eth.out, v35.23.10.04,    1256964 bytes, Tue Jan 16 13:22:38 2007

10:47:40:                       bh560pci.out, v35.23.10.04,    1276474 bytes, Tue Jan 16 13:20:28 2007

10:47:40:                       bh560ubp.out, v35.23.10.04,    1257250 bytes, Tue Jan 16 13:22:40 2007

10:47:40:                       bh560usb.out, v35.23.10.04,    1256247 bytes, Tue Jan 16 13:22:32 2007

10:47:40:                      bh560usbm.out, v35.23.10.04,    1256964 bytes, Tue Jan 16 13:22:38 2007

10:47:40:                         xds560.out, v35.23.10.02,    1076616 bytes, Thu Aug 17 14:49:48 2006

10:47:40:  
10:47:40:       Processing TI DVR Files...
10:47:40:                       tixds24x.dvr, v03.01.00.01,     163840 bytes, Wed Jan 05 14:34:52 2005

10:47:40:                       tixds27x.dvr, v02.50.00.01,      98304 bytes, Fri Dec 03 15:53:34 2004

10:47:40:                       tixds28x.dvr, v01.00.00.01,     131072 bytes, Fri Dec 03 15:53:38 2004

10:47:40:                  tixds510arm11.dvr, v02.20.33.00,     188416 bytes, Fri Aug 18 09:30:40 2006

10:47:40:                   tixds510arm7.dvr, v33.02.00.04,     204800 bytes, Tue Nov 07 11:58:20 2006

10:47:40:                   tixds510arm9.dvr, v33.01.08.04,     208896 bytes, Tue Nov 07 12:08:26 2006

10:47:40:                tixds510cortexA.dvr, v10.00.00.16,     139264 bytes, Wed Jun 28 08:57:36 2006

10:47:40:              tixds510icepick_b.dvr, v03.03.01.01,     114688 bytes, Wed Oct 25 17:15:20 2006

10:47:40:              tixds510icepick_c.dvr, v03.30.00.01,     122880 bytes, Mon Aug 28 13:05:58 2006

10:47:40:                       tixds54x.dvr, v04.06.05.00,     311296 bytes, Wed Dec 15 10:41:50 2004

10:47:40:                       tixds55x.dvr, v03.30.02.00,     163840 bytes, Wed Nov 15 16:45:02 2006

10:47:40:                  tixds560arm11.dvr, v02.20.33.00,     360448 bytes, Fri Aug 18 09:30:38 2006

10:47:40:                   tixds560arm7.dvr, v33.02.00.04,     507904 bytes, Tue Nov 07 12:10:16 2006

10:47:40:                   tixds560arm9.dvr, v33.01.08.04,     503808 bytes, Tue Nov 07 12:12:58 2006

10:47:40:                   tixds560c24x.dvr, v03.01.00.01,     503808 bytes, Wed Jan 05 14:35:00 2005

10:47:40:                   tixds560c27x.dvr, v02.01.00.01,     253952 bytes, Fri Dec 03 15:53:42 2004

10:47:40:                   tixds560c28x.dvr, v02.01.00.01,     266240 bytes, Fri Dec 03 15:53:46 2004

10:47:40:                   tixds560c54x.dvr, v04.06.05.00,     458752 bytes, Wed Dec 15 10:47:14 2004

10:47:40:                   tixds560c55x.dvr, v03.30.02.00,     430080 bytes, Wed Nov 15 16:45:06 2006

10:47:40:                   tixds560c64x.dvr, v01.44.00.00,     385158 bytes, Fri Oct 22 06:57:14 2004

10:47:40:                tixds560c64x_11.dvr, v02.33.00.00,     577536 bytes, Thu Oct 26 14:31:18 2006

10:47:40:              tixds560c64x_plus.dvr, v02.00.05.00,     462848 bytes, Tue Dec 05 10:47:56 2006

10:47:40:                    tixds560c6x.dvr, v05.03.00.00,     528384 bytes, Thu Oct 26 15:22:16 2006

10:47:40:                tixds560cortexA.dvr, v10.00.00.14,     364544 bytes, Mon Jun 26 17:59:08 2006

10:47:40:                    tixds560drp.dvr, v03.10.08.00,     212992 bytes, Thu Nov 24 18:42:36 2005

10:47:40:              tixds560icepick_b.dvr, v03.03.01.01,     233472 bytes, Wed Oct 25 17:15:24 2006

10:47:40:              tixds560icepick_c.dvr, v03.30.00.01,     237568 bytes, Mon Aug 28 13:05:58 2006

10:47:40:                      tixds6000.dvr, v05.03.00.00,     307200 bytes, Thu Oct 26 15:22:18 2006

10:47:40:                      tixds6400.dvr, v01.44.00.00,     139264 bytes, Fri Oct 22 06:57:20 2004

10:47:40:                   tixds6400_11.dvr, v02.33.00.00,     151552 bytes, Thu Oct 26 14:29:26 2006

10:47:40:                 tixds6400_plus.dvr, v02.00.05.00,     188416 bytes, Tue Dec 05 10:47:56 2006

10:47:40:                      tixds_drp.dvr, v03.10.08.00,     118784 bytes, Thu Nov 24 18:42:34 2005

10:47:40:  
10:47:40:       Processing Blackhawk XDS510 DVR Files...
10:47:40:  
10:47:40: %WARNING: no Blackhawk DVR files found.
10:47:41:       This is normal if Blackhawk XDS510 Emulation Drivers are not installed.
10:47:41:       (i.e. You are using only a Blackhawk XDS560 emulator.)
10:47:41: 
10:47:41:   #Sku              =ALL-3.3.38.2-FULL,ALL-3.3-SA
10:47:41: 
10:47:41:       #  SKU contains information on any applied Service Releases that
10:47:41:          is not always reflected in the version output below.
10:47:41: 
10:47:42:  
10:47:42: Starting scan for installed Blackhawk Driver Files...
10:47:42:  
10:47:42:                       blackhwk.cpl, v01.00.00.09,     266792 bytes, Fri Jun 13 22:44:50 2008

10:47:42:  
10:47:42:       Processing SYS Files...
10:47:42:                       bh560usb.sys, v01.07.00.00,     319400 bytes, Thu Aug 09 14:19:32 2007

10:47:42:  
10:47:42: Starting scan for Blackhawk Emulators...
10:47:42:  
10:47:42: Blackhawk USB560M JTAG Emulator (S/N:HD8669)
10:47:42: Blackhawk USB560-BP JTAG Emulator (S/N:LD3735)
10:47:42: Blackhawk USB560-BP JTAG Emulator (S/N:LD3906)
10:47:42:  
10:47:42: Completed scan for Blackhawk Emulators.
10:47:43: Scan Completed Successfully.
10:47:43:  
10:47:43: **************************************************
10:47:43: BHDetect - Version 1.0.0.7
10:47:43:  
10:47:43: Errors: 1,  Warnings: 1
10:47:43: **************************************************
10:47:43: BHDetect has completed a scan of your system.
10:47:43:  
10:47:43: The output generated in the dialog box window
10:47:43: is designed to help debug installation and setup
10:47:43: problems.
10:47:43:  
10:47:43: Any messages that begin with "%ERROR" should
10:47:43: be addressed and you can contact Blackhawk support
10:47:43: via email: support@blackhawk-dsp.com and include
10:47:43: the output from this utility for faster response.
10:47:43:  
10:47:43: Thank you,
10:47:43: The Blackhawk Support Team.
10:47:43: **************************************************
10:47:43: .


 

  • The errors listed in the output of BHProbe seem to indicate missing or invalid USCIF emulation files.

    You may want to try reinstalling the Blackhawk drivers and see if that helps. If that doesn't help, it might be worth uninstalling and reinstalling CCS, followed by the BH drivers to make sure you have a clean installation.

    If this is the only version of CCS you have installed on this machine, this FAQ should be helpful in making sure you completely remove CCS from the machine ( by deleting the appropriate registry entries) so you have a clean machine on which you can perform the reinstallation.