CCS4 and Windows 7 64-bit not working with Blackhawk USB 560bp emulator

Bill,

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)?

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.

Thank you,

--Bill

Bill,

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:

http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems#CCS_v4

BTW, I use a BH560m (not bp) in my Win7/64 and OMAPL137 without trouble.

Hope this helps,

Rafael

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.

Thanks again,

--b

Bill,

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:

http://processors.wiki.ti.com/index.php/Target_Configuration_-_Custom_Configurations

Hope this helps,

Rafael

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.

Thanks again,

--b

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?

Thanks again,

--b

Should I just try reinstalling ccsv4?

Bill,

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.

Bill,

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?

Regards,

Rafael 

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.

- 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

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?

Thanks, Andrew

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. 

--b

Bill,

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?

Andrew

Yes, that's the case.