This message is commonly due to a change in the connection properties within CCStudio. Try the following steps to clear the condition:
1. disable and then re-enable your NIC card on the PC that you are using.
2. stop the service and then start it again on the bhethcfg.exe setup tab
There is a bug in the CCS v.3.3 SR2 update, which should only be limited to devices that have a C64x+ and/or ICE_PICK devices defined in CCSetup (i.e. C6455, TCI6482, DM6443/6, DM6437, etc.). If the board name shown in CCSetup under My System is 28+ characters long, CCStudio will crash on startup. The workaround is to shorten the board name once you import the board configuration. For example, change "Blackhawk USB560m - C6455 Emulator" (~35 chars) to "BH USB560m - C6455" (< 28 chars).
In order to gain access to the driver download areas, you must register with this site. The registration is a two step process. First, select the "Register Now" link on the login box. At the next screen choose the "Regular User" role. Complete the registration form that follows and be certain to use a valid email address. Our site will send an email to this address with a link that completes the registration process and gives you access to the driver files. At each login, be sure to select the "Regular User" role by selecting the drop down menu next to the caption "Role".
If you installed a CCS v3.1 update or patch (i.e. SP1) after installing the TI XDS560 USCIF v35.23.6.0 patch, you may need to re-apply the USCIF. There are CCS v3.1 updates that over-write CFG files which do not work with the newer USCIF update. Just re-run the EXE from the Blackhawk USB560-BP Driver CDROM.
LIKELY CAUSE: CCStudio v3.1 updates applied after the C672x update from TI overwrites a file with bad data for the C672x devices. This does not affect the Texas Instruments PCI emulators and does affect all Blackhawk XDS560-class emulators.
SOLUTION: Fix the C672x Configuration error in CCS files:
a.) Locate the file, xdsfamily.cfg, in \CCStudio_v3.1\cc\bin and edit
with wordpad or equivalent editor.
b.) Locate the "%tms320c672x" section and change the "fixedsize"
paramter from 0x1400 to 0x1b00.
c.) Save the file.
d.) Make sure CCSetup is configured correctly for the C672x devices
(8-bit bypass + C6720 CPU) and start CCS.
If this does not resolve the issue, please contact Blackhawk support at this link: http://www.blackhawk-dsp.com/SupportRequest.aspx
The ICEpick_C driver and CCS setup was modified by TI and writes BAD data into the registry for CCSetup. This is located under key, HKEY_LOCAL_MACHINE\SOFTWARE\GODSP. If you locate the CCS v3.2 setup keys under this entry, you will find that the DrvSetupEmuName for the ICEpick_C driver does not match the other Blackhawk CPU entries. Changing the value from "XDS560 0" to match the other ARM and C64x+ devices will cure the problem. Note: You must do this edit everytime you run setup until TI issues an update that fixes their problem. We cannot implement a workaround.
A installation choice of CUSTOM (not FULL or TYPICAL) of CCS (v3.0 or v3.1 and later), where you did not install some required components. If you omitted the installation of the XDS560 PCI drivers or its parent option in the custom setup, that is the problem because TI has included some non-PCI driver files needed for XDS560-class emulators.
You can clear up this condition by going to the Windows add/remove programs dialog box and modify the CCS installation to install the XDS560 PCI drivers. You will probably need the CCS CD-ROM and this will install the missing files needed by the XDS560 DVR files. You do not need to install the EVM portion of this custom install option.
The latest information from Intel shows that some of the motherboards with Intel Chipsets (915G) mistake USB peripherals as boot devices. This is an INTEL bug and the work around is to unplug the emulator (USB cable) and allow the PC to boot. Operation is OK once PC displays Windows login or dekstop. See http://www.intel.com/support/motherboards/server/scb2/sb/CS-001202.htm for more information on the subject.
This behaviour has been observed in some PC's. The issue is that the enumeration of the emulator in Windows is not consistent especially after reboot or Windows shutdown. With the USB cable not connected to the emulator, attach the 5 volt power supply, then wait 2 seconds, then connect the USB cable to the emulator. You should see the unit enumerate with Windows every time in Windows Device Manager and/or Blackhawk Control Panel.
- Our USB560 & LAN560 supports the same targets as TI supports in Code Composer Studio v2.1 and later and uses the TI provided XDS560 DVR files. These are listed below with the prefix (*).
Please note that you need CCS v2.1 or later to use an XDS560-class driver, which is a requirement imposed by TI.
- We can also support operation in XDS510-class mode. This is where we use the TI XDS510 DVR files supported in Code Composer 4.1x and Code Composer Studio 1.x and later. This is something unique to our device and extends capabilities to the C24xx and VC33 devices in Code Composer v4.1x. These devices are shown below with the prefix (#).
- We cannot support the MPSD devices C30-32 as well as the older C4x and C5x DSP's. These are prefixed below with (x).
So, in summary, we can support all devices below, one way or another, except those marked with (x).
(x)TMS320C30-32 (#)TMS320VC33 (x)TMS320C4x
(x)TMS320C5x (*#)TMS320F24x (*#)TMS320F240x
(*)TMS320C27x (*)TMS320F280x (*)TMS320C54x
(*)TMS320C55x (*)TMS320C6000 (*)TMS320C64x
(*)TMS320C67x (*)TMS470 ARM7 (*)TMS470 ARM9
(*)OMAP
If the Blackhawk Control Panel (Start--> Settings--> Control Panel-->) does not show an installed emulator, then there was a problem in the installation and Windows does not see the emulator. As such, CCS also cannot see the emulator and simply reports that there is no target.
If you plugged the emulator in before installing the software from the CD, then go to the Windows device manager and remove the unrecognized USB device, reboot, then follow the installation instructions in the Quick Start Guide for your emulator model.
Blackhawk Emulators are not compatible with NT and Windows 95 or older versions. The PCI emulator is compatible with Windows 2000, XP and Vista. Additional support for 64-bit Windows is also provided in the download section of this website.
The Blackhawk JTAG emulator support is as follows:
XDS510-class: USB 2.0 JTAG Emulator and PCI JTAG Emulator
XDS560-class: USB560 JTAG Emulator
The USB560 is capable of operating in XDS510-mode. This is specific to Blackhawk XDS560-class emulators. By being able to run in XDS510-mode we can support older versions of TI Code Composer and devices such as the VC33. It also means that it will support standard RTDX for C2000 devices where TI only has this support in its XDS510 class drivers.
TI has two different classes of emulators, which are referred to by XDS510 and XDS560 classes. New features, capabilities and performance were added to XDS560-class emulators. However, TI does not support all available devices with the XDS560 drivers. The drivers are only supported for Code Composer Studio v2.1 and later. So if you buy an XDS560-class emulator, there are some devices, software, and features that not included. Some of these are: support for VC33, Code Composer v4.1x, RTDX for C2000 devices.
Unique to Blackhawk, our XDS560-class emulators support XDS510 drivers by being able to communicate with them or XDS560 drivers. So, if you update to one of our XDS560-class emulators you will not miss support for the things listed above.
Blackhawk emulators all use the TI provided driver (DVR) files that ship with Code Composer and Code Composer Studio. For example, if you have a C5510 device, you would use the TIXDS55x.DVR file for XDS510-mode emulators and the TIXDS560c55x.DVR file for XDS560-mode emulators.
All of our emulators, including XDS560-class, support Code Composer 4.1x and the VC33 device. This is possible because our XDS560-class emulator is unique to any other XDS560 emulator, even TI.
Yes. And you need nothing more from us. Our emulators are compatible with the TI Code Composer Studio “FlashBurn” plug-in utility, so there is nothing to learn, update or install. We are also compatible with the FlashBurn utility to program external flash memory. Just follow the many examples that TI provides with CCS.
Our emulators are available from a worldwide network of resellers including Texas Instruments. Just visit www.blackhawk-dsp.com and click the “where to buy” link in the home page, send us an email, or give us a call.
Yes. We support the ARM core devices, known as TMS470 by TI, and all OMAP devices. The OMAP list of supported devices includes, but is not limited to, 5910, 1510, 161x, 171x, DM270, DM31x, DM7xx, etc.
We use the C5510 EVM, C5509 EVM, and C5510 DSK just fine in the lab for testing. The main problem we have had with the C5510 device has been that Rev 2.x has an 8-bit BYPASS in the scan chain, so when you setup CCS with the C55x DVR file, you have to also add in an 8-bit BYPASS.
The other most common mistake is that customers do not use the TI DVR file (the one that you use for the TI XDS510 ISA card). If they are trying to use the files that are installed for use with the EVM board's JTAG interface, it will not work. Those drivers are designed to only work with that board and that host interface.
The other most common mistake is that customers do not use the TI DVR file (the one that you use for the TI XDS510 ISA card). If they are trying to use the files that are installed for use with the EVM board's JTAG interface, it will not work. Those drivers are designed to only work with that board and that host interface.
The USB 2.0 and USB560 JTAG Emulators support ALL of the devices that TI supports in Code Composer Studio (C2000, C5000, C6000, ARM and OMAP).
The USB560 supports TI's XDS560 class emulation technology. Some of XDS560 features include HS RTDX and faster code download. Our USB 560 JTAG is 480MB/s. The XDS560-class of emulation technology offers updated features and performance over the older XDS510 solutions. The main thing you will get from XDS560-class emulators is a large performance increase for the C28x platform. And if you are going to be ready for future enhancements to the C2000 line in CCS (RTDX, AET, etc.), you'll be ready with our USB560. See the TI emulation pages at
Go to
http://dspvillage.ti.com/docs/catalog/devtools/details.jhtml?templateId=5121&path=templatedata/cm/tooldetail/data/emul_560features
for more info.
The Blackhawk USB 2.0 emulator supports the XDS510 class of 15KB/sec download.
Regrettably, NO. TI protects CCS from using emulation drivers other than the simulator DVR files. Even if you add the DVR's from the DSK versions, CCS will say that they are not supported.
The host interface for one. This allows our unit to be portable and used with a laptop or desktop. Our testing has produced the same results in performance as the TI PCI card (no loss in performance). Of course, on USB 1.1, which is only rated for 12Mbit/sec transfer rate (1.5MByte/sec), we have some limits on the 2MByte HS-RTDX channel. All other aspects meet XDS560 speeds and compatibility. Actually, we go one further. Our unit can run in XDS510 mode, using the TI XDS510 DVR files, so you can use the unit with CC v4.1x (VC33, C20x, C24x) and CCS v1.2. Click here for more info.
It is compatible. We use the TI supplied DVR files for our USB 2.0 (XDS510-class) and USB560 (XDS560-class) JTAG emulators. When TI releases new or updated drivers, our unit is designed to work with them and you will not need to wait for driver updates from us. We support Code Composer v4.1x, CCS v1.2, and CCS v2.0 and later. We do not support MPSD or C4x devices. The VC33 is supported.
Our USB 2.0 emulator is currently being tested with the CCS release of RTDX for the C28x device family. If TI provides an XDS560 DVR file, the USB560 will be faster than the USB 2.0. It depends on how big your application is, how much you are depending on new features, and future needs, to which unit will be best for you and save development time vs. cost.
Yes, both of our USB-based emulators (XDS510 and XDS560-class) support these devices, but you need the CCS v2.2 Update for the C64x Rev 1.1 devices from TI.
The new version of silicon for the 5510 requires that an 8-bit bypass be configured in Code Composer. When you go to Code Composer setup, just add the bypass in the "Processor Configuration" tab of the Board Properties dialog box.
You should use the TIXDS6000.DVR file for both C6x0x and C6x1x devices. Just specify the proper CPU type in CCS setup. Also, there are no problems with you continuing to use the TIXDS6x1x.DVR for the C6711.
Most problems with DSP portion of OMAP is that ARM core does not release DSP from reset, which is done in GEL file on CCS startup or menu command. If there is a CCS Import Setup for the TI XDS560 PCI Card and your hardware (DM270), import the configuration and change the board name in the board properties tab from "XDS560 0" to "USB560 0" and save setup. Blackhawk USB560 emulator sues the SAME setup as the TI XDS560 PCI emulator! Just change the emulator name in setup.
Both units operate with the DM642, however, users will be much better off using the USB560 (XDS560-class) Emulator, because of its speed and support of the advanced emulation features contained in the DM642 (AET, HS-RTDX, etc.). These are not supported by XDS510-class emulators.
For the OMAP platform, it has been noticed that the ARM core of the device boots and causes contention with CCS and the emulator. This has been experienced with the TI XDS560 PCI card and our USB560. Both emulators act similarly. The following workarounds are what TI has recommended:
1.) When you get the ABORT, RETRY, IGNORE error dialog, reset the target and hit retry. As it was explained to us recently, this is typical and may require multiple retries, but should be stable once CCS gets control of the ARM core.
2.) The ARM can or defaults its boot process from flash. The idea here is to program the flash with code to put it into an infinite loop allowing CCS to halt each core and start up.
First the USB560 is a TI XDS560-class emulator and our USB 2.0 is an XDS510-class emulator.
The "560" is the latest emulation technology introduced by TI in May 2002. XDS560-class emulators contain an on-board processor which does 75% or more of the JTAG processing. On XDS510-class emulators, this is done on the PC (Intel Processor) and all of the JTAG commands (thousands) had to cross the PC to Emulator interface (ISA, PCI, USB, Parallel Port, etc.). This old way did not take advantage of the USB interface. We can utilize the bandwidth of the USB in our USB560 design, thus it performs very well on USB 1.1 and 2.0.
The USB 2.0 emulator will give you a 5-7 times improvement running with USB 2.0 controller. This should have been included with the unit (choice of PCI or CARDBUS) from our reseller if you only had USB 1.1 on your desktop or laptop. I am not sure what you target processor is, but it should load in under 30 seconds with a high speed USB 2.0 controller.
The USB560 adds more features (Advanced Event Triggering, HS-RTDX, etc.), and speed to make you more productive. It all comes from comparing needs, features, speed, portability and cost to determine which is the right buy.
There is a Flash Plug-in available for Code Composer at this link: http://focus.ti.com/docs/tool/toolfolder.jhtml?PartNumber=C2000FLASHTOOLS Use this link to download the file: http://dspvillage.ti.com/download/c2000flashprogsw_v112.zip The plug-in will provide support for our USB emulator. There is also a tool for the serial port if your target has a serial port.
The dialog box you refer to is displayed when there is a problem with the Windows USB driver communicating to the firmware running inside the emulator pod. You should not see this dialog, however it can happen if CC_APP.exe has problems and remains in memory. Usually a reboot will clear this from happening.
Yes, that is how our remote access works. The only thing required for the remote "server" machine is installing the USB 2.0 JTAG Emulator drivers for Windows (Plug and Play) and then run a background service. You do not need CCS installed on this machine, but it has to be connected to the LAN. On your "client" machine, you need CCS installed. Then, using our normal CCS DLL, you can access the "server" machine by adding a setting into our CFG file.
The remote emulation software is a software utility add-on for our emulators that will allow them to support remote connections over Ethernet. You do not need to buy a special Ethernet adapter because it uses the computer where it is already installed and that computer does not even need Code Composer Studio installed, which saves you a license. Of course the computer needs an Ethernet connection to your LAN, but then many users are able to connect to the emulator from other machines in different offices or buildings. Please keep in mind that the same emulator cannot be access concurrently.
Glad to see that you are able to use the remote connection. Unfortunately, multiple users access the emulator at the same time. CCS cannot dynamically maintain the state of the emulator, processor and scan chain. It can be shared by many people, but only one person can connect at a time.
YES. The DM642 uses the C64x DVR driver that is supplied by TI in CCS. You should be able to add the board labeled "C64xx XDS510 Emulator", add a CPU and then manually configure the rest of setup for our emulator using the right CFG file and I/O port as listed in our documentation.
Our Blackhawk USB560 JTAG Emulator supports OMAP CCS v2.2 and DM270 and is currently being used by developers on this platform. The USB560 emulator ships with CDROM that contains all the necessary Windows device drivers. Also, the USB560 uses the TI supplied XDS560-class DVR files for your target. These are the files that ship with CCS or you download via the update advisor. So, you are always up to date.
Yes, TI recently released the FlashBurn utility for C2000 CCS. We have not tried it here in the lab, but it is configured the same way as C5000 and C6000, which we use regularly with all our emulators, including the USB 2.0 unit.
We use the C5510 EVM, C5509 EVM, and C5510 DSK just fine in the lab for testing. The main problem we have had with the C55x device has been that Rev 2.x has an 8 bit BYPASSin the scan chain, so when you setup CCS with the C55x DVR file, you have to also add in an 8-bit BYPASS. The other most common mistake is that customers do not use the TI DVR file (the one that you use for the TI XDS510 ISA card). If they are trying to use the files that are installed for use with the EVM board's JTAG interface, it will not work. Those drivers are designed to only work with that board and that host interface. The USB 2.0 and USB560 JTAG Emulators support all of the devices that TI supports in Code Composer Studio (C2000, C5000, C6000, ARM and OMAP).
It is possible to hardware modify the emulator to reduce TCK frequency. The choices are 3, 6, 12 & 24MHz. However, there is a charge associated with this modification.
Our TALON OS is POSIX-compliant for TI TMS320 DSPs. We stress POSIX, because that is what UNIX and Linux are based on, however, we are real-time. There is no reason that our OS would not support the CORBA Facilities and Services, but that engine does not exist. You have the same POSIX system calls available to you across each TMS320 platform, so moving from one to the other is easy. Also, you have all the POSIX documentation that has been written at your finger tips.
