Site Index
   Support Home
   C2000 Products
   C5000 Products
   C6000 Products
   OMAP Products
   JTAG Emulators/
Emulation Drivers
   Legacy Support
   Ordering Info.

Spectrum Digital Troubleshooting Guide

This document contains troubleshooting information you can use if you think your target board or JTAG emulator is broken.

Debugging Your System

Table of Contents

1. Common Problems

2. Debugging a System with an External JTAG Emulator

3. Debugging a DSK with an Embedded JTAG Emulator

4. Debugging an eZDSP with an Embedded JTAG Emulator

5. Known Issues

6. Additional Information


Common Problems

1.1 Simple things to check
Small things that cause a surprising number of problems:

  • Make sure you follow the setup instructions that come with your target board. The exact order of operations is important. You can find many of our setup instructions here if you've lost them.
  • Verify that your JTAG connection is working using SDConfig (see below).
  • Make sure that all power cables and JTAG cables are securely connected.
  • If a historically reliable setup suddenly stops working, try running SDConfig while holding the JTAG cable or USB cable (both PC side and target side) in a few different positions. The PC side USB connectors and JTAG header can wear out with heavy use.
  • If you have several similar products, try one of the others to verify that the unit really is not working.
  • Check the Software Guide to see if you have all necessary components.
  • If you are having problems with audio input/output, make sure all cables are plugged in completely.
  • If you apply an incorrect voltage to your target board or emulator and now it does not work you'll have to RMA the unit.


Debugging Your System with an External JTAG Emulator

2.1 Parts of a Working System
The following is a list of components that must be working to debug with CCStudio and an external Spectrum Digital JTAG Emulator such as an XDS510 PP+ or XDS510USB. Follow this list in order to diagnose your problem. If you are connected using the embedded JTAG emulator on a DSK or eZdsp the procedure is slightly different, please skip to the appropriate section.

  • Target Board
  • External JTAG Emulator
  • Low Level Emulation Drivers
  • Code Composer Configuration
  • User Software

2.2 Target Board
Spectrum Digital target boards are fully tested before shipping so you should assume that new target boards are functional and that any connection problems are related to setup or software problems. The most common causes of real target board failures are application of improper voltages to the board or side effects of hardware engineers making modifications to the boards. Here are some other things to try if your working board suddenly has problems and there is no obvious electrical or physical damage:

  • If you have another similar target board, try it to see if the problem really is with the board or another piece of the tool chain.
  • Most Spectrum Digital target board's ship with bootable code in Flash. Since this code always runs at boot, some of the things users associate with a functioning board (LEDs blink, EMIF and clocks are set up) are actually dependent on the software and not the hardware. See the Software Guide for more information.
  • Related to the previous item, if you change any boot jumpers or switches the board startup behavior will change. Try putting the board in its original factory state before reporting a problem.

2.3 External JTAG Emulator
The factors that affect each type of emulation differs somewhat by their connection type, please follow appropriate instructions below:

2.3.1 External XDS510USB USB JTAG Emulator
These factors may affect the operation of your emulator:

  • Your JTAG emulator should always be attached to the board before power is applied. This insures that a proper ground is established on board startup.
  • Make sure that your cables and USB connectors are making good contacts. USB connectors can wear out after a large amount of plugging and un-plugging.
  • If you are getting an intermittent or unreliable connection, try using the JTAG cable (the part between the emulator and the target board) in a few different positions to see if it makes a difference. This will tell you if you need to have your cable replaced.

2.3 External XDS510PP+ Parallel Port Emulator
These factors may affect the operation of your emulator:

  • Your JTAG emulator should always be attached to the board before power is applied. This insures that a proper ground is established on board startup.
  • Make sure that the parallel port cable is firmly attached to both the emulator and your PC. Parallel port cables that are not firmly attached (screwed in) can slip out of place.
  • Switch boxes can degrade the parallel port signal. If you are having problems when connected to a parallel port switch box, try running directly attached to your PC.
  • The power supply connector is a standard 2.1mm co-axial connector that is used by many types of power supplies. Please make sure that you are using the +5V (center positive) adapter that shipped with your emulator.
  • If you are getting an intermittent or unreliable connection, try using the JTAG cable (the part between the emulator and the target board) in a few different positions to see if it makes a difference. This will tell you if you need to have your cable replaced.

2.4 Low Level Emulation Drivers
Spectrum Digital provides a utility called SDConfig with our emulation drivers. SDConfig communicates directly with the JTAG emulator to test both the emulator and the software communication layers that talk to the emulator, even if Code Composer Studio is not installed. This utility lets you determine if your problem is on the emulator side or the Code Composer/Code Composer Setup side.

  1. Connect your emulator to your target board through the 14-pin JTAG header and make sure your target board is powered.
  2. Launch the SDConfig utility from its blue desktop icon. The top left panel is an I/O port address selector with each emulator using a different I/O address based on its connection type and the number of emulators installed. The I/O port address is typically 0x510 for a XDS510 USB emulator and 0x378 for a XDS510PP+ parallel port emulator.
  3. Select the I/O port address and use the Emulator --> Test option to check the connection all the way to the target. The emulator target scan chain length will be printed in the output window if successful.

2.5 Code Composer Configuration
If your emulator scans with SDConfig and Code Composer still reports that it cannot establish an emulation connection on startup you have three potential problems.

  1. Code Composer Setup is not configured properly (it must be configured to know what devices are on the scan chain before startup.
  2. You are not using the correct GEL files (some devices need special operations to occur during startup to come up properly.
  3. Your setup used to work but now it does not (did you install something new recently?)

Please check the emulator installation instructions in our Software Guide to resolve issues #1 and #2. For #3, try to put your system back in the state it was when it last worked.


Debugging Your DSK with an Embedded JTAG Emulator

3.1 Parts of a Working System
The following is a list of components that must be working to debug with CCStudio and a Spectrum Digital DSK. Follow this list in order to diagnose your problem.

  • Target DSK Board
  • Low Level Emulation Drivers
  • Code Composer Configuration
  • User Software

3.2 Target DSK Board
Spectrum Digital target DSK boards are fully tested before shipping so you should assume that new target boards are functional and that any connection problems are related to setup or software problems. The most common causes of real target board failures are application of improper voltages to the board or side effects of hardware engineers making modifications to the boards. Here are some other things to try if your working board suddenly has problems and there is no obvious electrical or physical damage:

  • If you have another similar target board, try it to see if the problem really is with the board or another piece of the tool chain.
  • Most Spectrum Digital target DSK board's ship with bootable code in Flash. Since this code always runs at boot, some of the things users associate with a functioning board (LEDs blink, EMIF and clocks are set up) are actually dependent on the software and not the hardware. See the Software Guide for more information.
  • Related to the previous item, if you change any boot jumpers or switches the board startup behavior will change. Try putting the board in its original factory state before reporting a problem.

3.3 Embedded JTAG Emulator
These factors may affect the operation of your emulator:

  • Make sure that your cables and USB connectors are making good contacts. USB connectors can wear out after a large amount of plugging and un-plugging.
  • If you are getting an intermittent or unreliable connection, try using the USB cable in a few different positions to see if it makes a difference. This will tell you if you need to have your cable replaced.

3.4 Code Composer Installation
If your emulator scans with SDConfig and Code Composer still reports that it cannot establish an emulation connection on startup you have three potential problems.

  1. Code Composer Setup is not configured properly (it must be configured to know what devices are on the scan chain before startup.
  2. You are not using the correct GEL files (some devices need special operations to occur during startup to come up properly.
  3. Your setup used to work but now it does not (did you install something new recently?)

Please check the emulator installation instructions in our Software Guide to resolve issues #1 and #2. For #3, try to put your system back in the state it was when it last worked.


Debugging Your eZdsp with an Embedded JTAG Emulator

4.1 Parts of a Working System
The following is a list of components that must be working to debug with CCStudio and an embedded JTAG Emulator. Follow this list in order to diagnose your problem.

  • Target Board
  • Low Level Emulation Drivers
  • Code Composer Configuration
  • User Software

4.2 Target eZdsp Board
Spectrum Digital target eZdsp boards are fully tested before shipping so you should assume that new target boards are functional and that any connection problems are related to setup or software problems. The most common causes of real target board failures are application of improper voltages to the board or side effects of hardware engineers making modifications to the boards. Here are some other things to try if your working board suddenly has problems and there is no obvious electrical or physical damage:

  • If you have another similar target board, try it to see if the problem really is with the board or another piece of the tool chain.
  • Most Spectrum Digital target board's ship with bootable code in Flash. Since this code always runs at boot, some of the things users associate with a functioning board (LEDs blink, EMIF and clocks are set up) are actually dependent on the software and not the hardware. See the Software Guide for more information.
  • Related to the previous item, if you change any boot jumpers or switches the board startup behavior will change. Try putting the board in its original factory state before reporting a problem.

4.3 Embedded JTAG Emulator
These factors may affect the operation of your emulator:

  • Make sure that your cables and USB connectors are making good contacts. USB connectors can wear out after a large amount of plugging and un-plugging.
  • If you are getting an intermittent or unreliable connection, try using the USB cable in a few different positions to see if it makes a difference. This will tell you if you need to have your cable replaced.

4.4 Code Composer Installation
If your emulator scans with SDConfig and Code Composer still reports that it cannot establish an emulation connection on startup you have three potential problems.

  1. Code Composer Setup is not configured properly (it must be configured to know what devices are on the scan chain before startup.
  2. You are not using the correct GEL files (some devices need special operations to occur during startup to come up properly.
  3. Your setup used to work but now it does not (did you install something new recently?)

Please check the emulator installation instructions in our Software Guide to resolve issues #1 and #2. For #3, try to put your system back in the state it was when it last worked.


Known Issues

5.1 Issues when using USB connection and Xilinx ISE tools
There is a known issue with systems running both Xilinx ISE tools version 5.1 and earlier. During the Xilinx tools installation the defaults install device drivers for the Xilinx Multilinx USB JTAG cable even if you are not using it (most customers use the parallel port version). The Xilinx device drivers will filter out commands to the on-board USB port on the Spectrum Digital DSKs and Windows will never recognize the board. This issue was officially resolved in release 5.2 of the Xilinx tools.

The workaround is to remove the Xilinx USB device drivers and reinstall the Xilinx tools without Multilinx USB drivers.

  1. Uninstall the Xilinx tools.
  2. Go to the windows/system32/drivers directory and remove mlnxfltr.sys and mltilnx.sys.
  3. Unplug your DSK.
  4. Go to your Windows device manager (from the Control Panel) and delete any USB hubs.
  5. Reboot your PC, Windows will restore support for the hubs.
  6. Plug both the USB and power cables back into the DSK. The Add New Hardware wizard should pop up and ask for the location of the drivers. Put the DSK software installation CD-ROM back in the CD-ROM driver and let Windows automatically search for the drivers.
  7. At this point the DSK should be recognized by Windows (you should be able to go to the device manager and see something like "SD Based USB Debug Tools".
  8. Re-install the Xilinx tools making sure NOT to install and Xilinx USB Multilinx drivers.

This issue is described on the Xilinx support site at:Xilinx Support

5.2 Problems migrating from CCS 2.2X to CCS 3.XX

  1. CCS 2.2X and before install in directory c:\ti, CCS 3.XX and after install in directory C:\CCStudio
  2. CCS 3.XX does not automatically connect to the target board, like CCS 2.2X. Instead you the user must manually connect by selecting the Debug->Connect option.
  3. With the new manual connection, CCS 3.XX requires the use of OnTargetConnect() in the GEL file. This function is called each time a manual connection is established. This function does not replace OnStartup(), but does removed any operations that is done in OnStartup().


Additional Information

6.1 On-line documentation
For more up to date documentation go to :

   http://support.spectrumdigital.com

©Copyright 2002-2014 Spectrum Digital, Inc. All Rights Reserved.