TI E2E Community
Code Composer Studio
Code Composer Forum
CCS4 and Windows 7 64-bit not working with Blackhawk USB 560bp emulator
I have CCS 4.1.3.00038 installed on a PC running 64-bit Windows 7. Every time I try to start the debugger I get a dialog box that says "Error initializing emulator". The Blackhawk emulator appears to be enumerating properly and shows up in Device Manager. The output of the BHDetect utility is included below. The same setup works fine on a Windows XP 32-bit machine. I cannot find anything on the e2e site that says CCS4 should not work with windows 7 64 bit. Is there something else I can look at to debug this problem?
07:23:03: BHDetect - Version 184.108.40.2067:23:03: 07:23:03: Scan started on Monday, October 11, 2010 at 07:23:03 AM.07:23:03: 07:23:03: MEYEMAC07:23:03: wsm07:23:03: 07:23:03: Starting Quick Scan for CCStudio Installations...07:23:03: 07:23:03: %%ERROR: bhDetect_GetIniFile() opening ComponentManager registry key.07:23:03: bhDetect_ListCCSInstallations: Error locating CCStudio Component Manager INI file.07:23:03: bhDetect_ListCCSInstallations: No valid CCS installations found.07:23:04: 07:23:04: Starting scan for installed Blackhawk Driver Files...07:23:04: 07:23:04: blackhwk.cpl, v01.01.00.00, 266280 bytes, Mon Mar 23 11:26:08 2009 07:23:04: 07:23:04: Processing SYS Files...07:23:04: bh510usb.sys, v01.14.00.00, 310568 bytes, Mon Mar 23 11:26:06 2009 07:23:04: bh560eth.sys, v01.00.00.09, 97704 bytes, Thu Jan 15 14:10:36 2009 07:23:04: bh560usb.sys, v01.09.00.00, 318248 bytes, Mon Mar 23 11:26:08 2009 07:23:04: bhpci.sys, v01.05.00.00, 481448 bytes, Mon Mar 23 11:26:08 2009 07:23:04: 07:23:04: Starting scan for Blackhawk Emulators...07:23:04: 07:23:04: 1.) Blackhawk USB560-BP JTAG Emulator (S/N:LF4521)07:23:04: 07:23:04: Completed scan for Blackhawk Emulators.07:23:05: 07:23:05: Scan Completed Successfully on Monday, October 11, 2010 at 07:23:05 AM.07:23:05: 07:23:05: ******************************************************************************07:23:05: BHDetect - Version 220.127.116.11 Errors: 1, Warnings: 007:23:05: ******************************************************************************07:23:05: BHDetect has completed a scan of your system. The output generated in the 07:23:05: dialog box window is designed to help debug installation and setup problems. 07:23:05: Any messages that begin with "%ERROR" should be addressed and you can 07:23:05: contact Blackhawk support via email: email@example.com and include07:23:05: the output from this utility for faster response.07:23:05: 07:23:05: Thank you, The Blackhawk Support Team.07:23:05: ***************************************************************************EOF.
CCS 4.1.3 should work with Windows 7, but it is recommended to install CCS outside the "Program Files" or "Program Files (x86)" directory as mentioned here:http://processors.wiki.ti.com/index.php/Running_CCStudio_v3.3_on_Windows_Vista#CCSv4
What device are you connecting to? Does connection to the same device with the same emulator work with from the Windows XP machine with the same version of CCS (4.1.3)?
If a post answers your question please mark it with the "Verify Answer" button
Search the wikis for common questions: CGT, BIOS, CCSv3, CCSv4Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
I have installed CCS4 in C:/TI. I'm trying to connect to a TMS320C6747. I am using the same CCS version, emulator, and board with Windows XP. The only curious thing in my 64-bit setup is that the Blackhawk detect utility says it can't find a valid install of CCS (see previous post), even though it's definitely installed.
The utility from BlackHawk is trying to detect a CCSv3.3 installation, thus the error (it found one in my PC as I have both 3.3 and 4 installed). Because of this I am not sure if the information provided is reliable with the updated device drivers for CCSv4 (in my Win7/64 this utility does not give me any information about the driver files!).
Even still, to help get additional details about this issue could you please use the tool <dbgjtag.exe> from your CCSv4 installation and publish the results? Its usage is described in the link below:
BTW, I use a BH560m (not bp) in my Win7/64 and OMAPL137 without trouble.
Hope this helps,
Thanks for the very prompt response. I appreciate it. One thing I neglected to mention is that the board i'm using has the DSP in a jtag chain with a couple of other devices. The DSP is not the first device in the chain. Have you had any experience on Windows 7 with boards with the processor in a jtag chain?
I'll get you the results as soon as I can.
No, I haven't used any other devices in daisy-chain with this specific DSP. However the CCSv4 target configuration file (.ccxml) will have to reflect that.
In your case you will have to create the JTAG configuration by adding each daisy-chained device in order - they would be either a DSP (for the C6747) or a bypass device with "x" number of bits (for each of the other ones). Please check the page below that contains additional details on how to create a custom configuration:
The target configuration file I have works fine with 32-bit Windows XP. I'm using the same config with Windows 7 64-bit, but can never get past the emulator initialization.
I ran dbgjtag as follows:
/TI/ccsv4/common/uscif/dbgjtag.exe -f 'C:\TI\ccsv4\DebugServer\bin\win32\BrdDat\ccBoard0.dat' -rv -S pathlength
It reported the following:
-----[An error has occurred and this utility has aborted]--------------------This error is generated by TI's USCIF driver.The value is '-131' (0xffffff7d).The title is 'SC_ERR_SYS_MEM_ALLOC'.The explanation is:The operating system has reported a memory error when allocating memory.
This is pretty odd. There are no errors that I can find in any of the windows event logs. I've got 8GB of memory in this machine. Any ideas?
Should I just try reinstalling ccsv4?
Just some ideas on few other things to check:
- Can you open the Blackhawk control panel (should be an icon on your desktop) and see if it detects your emulator correctly?
- Run the reset and probe diagnostic utilities that Blackhawk provides. There should be a BHreset_USB560bp.bat file and BHprobe_USB560bp.bat file in the directory <installdir>\emulation\Blackhawk\Utility\BHProbe.2
- Try updating your drivers if they are not already on the latest version. You can check for Blackhawk driver updates from within CCS Help->Software updates->Find and Install.
Sorry for the delay; we have found some issues with the emulators being used in Win7/64bits environments; can I send you a patch in a private message?
Hello Bill, (and Hello Rafael),
I've tried to duplicate the errors here on our Windows 7 x64 machines, but have not been able to do it. I am also not sure what is in the file: 'C:\TI\ccsv4\DebugServer\bin\win32\BrdDat\ccBoard0.dat' . Can you send me that file or contents?
As Rafael said, please run our BHProbe utility and email us the output file. I'd like to know if this works or fails.
You can also, from a command prompt, execute this command and send the output.
dbgjtag -d bh560ubp.out -rv -S pathlength
Just a couple other ideas: Are you running a virtual machine? Did you try to install drivers by compying files manually? Is the BHDetect output provided in an earlier response from the WIndows 7 64-bit machine?
We have an Atmel MCU (atxmega) in our jtag chain which controls power to the other parts in the chain. When the BHprobe untility tries to scan the chain (scan 2 with the "-i" option to the driver) it ends up resetting the MCU and removing power from the board. The Blackhawk folks have suggested we just not use the utility for our board. Either way CCS4 does not do this in Windows XP 32-bit when you start the debugger and connect to the target. It looks very much like Windows 7 64-bit does something different.
I'm not running a virtual machine, I've tried reinstalling things manually and otherwise multiple times. The BHreset utility works fine on all machines.
I just want to clarify things and what has been identified.
The JTAG scan chain on your board includes a non-TI device (Atmel MCU). This non-TI device is affected by the TI "xdsprobe" command used by our BHProbe utility when it probes the scan chain, except when it only does a "reset".
There is no problem having another device in the scan chain with the TI DSP, but unlike Xilinx or Altera devices, the Atmel part is being affected, so we just recomended that you not run xdsprobe with any options other than reset. I would expect this to be a problem with any CCS version and any Windows version (x86 or x64).
Now, if I understand the post, you can use CCS v4 and Windows XP 32-bit to connect to your board, but if you use the same version of CCS v4 with Windows 7 x64, you see this power down problem with the Atmel device when you try to connect. Correct?
Yes, that's the case.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.