The port utility SdConfig.exe will help you setup your PC printer port and test out the connection between your emulator and target system.
Features:
- Test for the presence of a printer port and the current mode.
- Setup your sdopts.cfg emulator configuration file.
- Minimizes user setup errors of sdopts.cfg.
- Verify the connection between the host PC and emulator using the sdopts.cfg emulator configuration.
- Verify the connection between the emulator and target system using the sdopts.cfg emulator configuration.
- Provides and emulator reset.
Fully Supported Products:
- XDS510PP JTAG (Printer port)
- XDS510PP_PLUS (Printer port)
- SPI515 (Printer port)
- SPI510/XDS510 (ISA port)
- SPI525 (PCI port)
- All eZdsp
- XDS510USB
Limited Support Products:
- XDS510PP MPSD (Printer port, C3x)
- SPI530 (Printer port, C3x)
- SPI520 (Printer port, C27x )
You can use the configuration utility so setup most of the sdopts.cfg options. However you cannot test our PC to emulator or emulator to target connections. These products are shipped with utilities that can be used for testing the connections.
Installation:
The SdConfig utility is
included with the Spectrum Digital emulation driver istallation.
If you have not already run the emulation driver installation, please do so
before proceeding. The driver installation is included in your emulator product
kit or may be downloaded from the Spectrum Digital Support site at: "Emulation Drivers".
The configuration utility will install in a path that looks like c:\<Install Directory>\specdig\SDConfig. The default install directory is the same directory as the Code Composer or Code Composer Studio install Directory.
The installation will install(or replace) the sdopts.cfg file located in the Windows system directory. If there is currently a working Spectrum Digital Emulator configuration on this computer, you may wish to save this file just incase you do not remember current configuration. The new sdopts.cfg file is required to get all the emulators and eZdsp products included into the file with default settings.
The SdConfig.exe utility is targeted
towards users of TI/GoDSP Code Composer 4.x, Code
Composer Studio 1.x, 2.x, 3.x, and higher. If you are NOT running one of these debug tools
then you need to make sure that your Windows OS COMCTL files are up to date. In
general if you are running Win98, Win98 SE, WinNT with service pack 5, Win
2000, or if you are using Internet Explorer version 5.x or higher you should
have the proper OS updates installed. If you need an update then visit the
Microsoft web site athttp://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp.
If you are not running with the proper COMCTL files
then the SdConfig.exe utility may generate a protection fault
when some windows or controls are selected.
Latest Updates:
Latest updates of Emulation Drivers and the SDConfig configuration utility or other Spectrum Digital productsmay be found on our support website at: http://support.spectrumdigital.com
Step through the following screens to setup your sdopts.cfg file and test out your emulator connection.
When you start SdConfig.exe you will get the following startup screen.
Check Printer Ports Available:
If your emulator/eZdsp is connected via the PC printer port then you need to determine what ports are available. Under the Configuration menu item select Ports Available and Printer, USB. This will scan your printer ports and check for the current configuration. This test needs to be performed with the emulator disconnected from the PC. The results will be displayed in the "Output Window" at the bottom of the SDConfig Window.
Check USB Connection Available:
Using the information from the previous step you should have found at least one available printer port. If not then you will need to configure your PC BIOS to enable at least one printer port. Using the EmuPortAddr from the previous step select the emulator icon with the matching port address. This will give you two sets of options, Emu emulator configuration options and Data Log for data logging options. Select the Emu icon. This will bring up the available emulator options. These options are product sensitive and only allow "valid" options to be selected. For details on each option use the online help.
Select the name of the hardware product that you are attached to. Once you pick the product the other options will change to reflect only the valid options for the product.
Setting the Emulator Port Mode
Select an emulator port mode from the list available. The modes are emulator and port address dependent. Note that newer printer port emulator/eZdsp product do not support the old SPP4 mode of operation.
- Emulator port speed: The acceptable values are emulator dependent and in most cases the defaults will work.
- Include SD opto-isolator pod. Check this box if you have the SPI610 pod included in the scan chain.
- Disable certain emulation polling: Check this box if you want the highest emulator performance. Uncheck this box if you see erratic behavior under Code Composer.
- Perform C27x style Wait-In-Reset: Check this box if you are connected to a C27xx device and wish to use it’s Wait-In-Reset capability. This box should be unchecked for all processors that do not support Wait-In-Reset emulation feature.
Save the new options settings:
Save your file settings using the File->Save or floppy disk icon. If you forget to save your options then you will be prompted to do so before running verification or exiting the program.
The emulator must be connected to the computer and powered. Highlight the port address where the emulator is connected from the list of ports in the left window of the SDConfig. Click Configuration->Verify.
If an emulator or SD product is detected then product information will be displayed in the output window. Otherwise error information will be displayed. This test will verify that your PC is communicating with the emulator. The default printer port mode is used as it has the best chance of working for parallel port tools. When you test the emulator/target connection the port mode that you have specified in the configuration setup will be used.
Test Emulator\Target Connection:
Once you have verified that the PC to emulator connection you are now ready to verify the emulator to target connection. Make sure that you have power connected to your emulator and target system. Then select the <EMU check icon > or Emulator->Test.
This test performs basic JTAG scans to determine the length of the JTAG IR path and how many devices are in the scan chain. This test does not verify that each target device is functional. There could still be target-related issues that will not allow you to start up Code Composer. Following is a list of JTAG IR lengths for various TI devices:
|
Device |
JTAG IR Length |
|
TMS320C2XX |
8(F20x, F24x, F240xA) |
|
TMS320C28XX |
38 |
|
TMS320C5X |
8 |
|
TMS320C54X |
8 |
|
TMS320C4X |
8 |
|
TMS320VC3X |
8 |
|
TMS320C6X0X |
8(C6201,C6701) |
|
TMS320C6X1X |
46(C6211,C6711) |
|
TMS320C55XX |
38 |
|
TMS320C27XX |
38 |
|
TMS470R1X(ARM) |
4 |
|
TMS470R2X(ARM9) |
4 |
|
TMS320C64XX |
38 |
Following this test the emulator is reset and the JTAG TRSTn pin is driven low to reset the device emulation logic. You can also reset the emulator without running the scan test by selecting the <Big R icon> or Emulator->Reset.
Once you have verified the PC, emulator, and Target connection you can perform advanced scan chain diagnostics. These diagnostics can aid in finding scan chain problems related to integrity, signal quality and other failures that would prevent CCS or other debug products from starting and running reliably. To run diagnostics, select Emulator->Diagnostics. The following screen shows the diagnostic defaults.
· Scan Verify: Uses an incrementing scan pattern. This pattern will have varying numbers of ones and zeroes.
· Scan Pattern: User selectable pattern. Best selection for probing the JTAG TDI/TDO signals.
· Stop Error Count: Determines the number of failures that can accumulate before the test stops. If set to zero then all errors are ignored. Set to zero when probing with scope.
·
Test
The diagnostic test flow is designed such that emulator and or scan errors are cleared at the beginning of each pass of the test. This is required to provide a repetitive looping mode. Each pass of the test will scan approximately 10000 bits of TDI/TDO data. If the Stop Error Count is set to 1 then diagnostic messages will be displayed indicating the first bit that failed and number of bits state changes.
What To Expect
- TRSTn: Should be high during the test. Should pulse low between tests to toggle between test and emulation mode.
- TMS: This signals is generally low but will pulse high at the beginning and end of each scan. Scan data is sent in either 8 or 16 bit blocks for most emulators. So you will see a burst of scan data then silence and the pattern will repeat.
- TDO: Emulator TDO, DSP TDI. You will see your scan pattern aligned with TMS.
- TDI: Emulator TDI, DSP TDO. You should see your scan pattern delayed by the length of the JTAG IR. All test scans are to the JTAG IR. At the end of a scan burst the DSP will tri-state the TDO pin. So you may see this pin slowly rise to a high level.
- TCK/TCKRET: Free running JTAG clock. Frequency is generally 10MHz when supplied by the emulator.
- EMU0/1: These signals are generally outputs from the DSP and do not change state.
Tips
- Over 90% of scan related failures are a result of TCK/TCKRET signal. Always check this signal first. In many cases you may find that simply putting a scope probe on the TCK or TCKRET signal will make the diagnostics pass. This is clear indicator that TCK/TCKRET signals needs to be cleaned up or filtered. Testing has shown that on newer devices, DSP TCK is more noise sensitive then previous generations. Devices that fall into this class would be C64x, C55xx, OMAP, and custom ASIC devices. The predominant cause is related to type of input buffer being used on these devices and other signal coupling both on the board and in the DSP or package. In the majority of cases an AC terminator or small capacitor (12pf-33pf) at the DSP TCK pin will clear up the problem. In other cases you may need to buffer the TCK/TCKRET signals and terminate to resolve the problem.
- The highest probability of emulator failure is the 14-pin JTAG connector. This is especially true in production test and programming environments where JTAG cable may be inserted and removes hundreds of times a day. If your 14-pin JTAG connector looks worn then run the diagnostics and twist/bend the JTAG cable near the connector. The TMS and TRSTn signals are generally the first signals to fail as the JTAG cable is generally “peeled” off the target versus being removed in a straight upward fashion.
- If you are using a variable voltage emulator then first reset the emulator and probe the signals. Be sure that the PD pin on the JTAG connector is at the proper voltage level. Also, review the TCK/TCKRET for proper levels. In many emulators the TMS and TRSTn pins will be high following an emulator reset check these pins also.
- Most emulator design guidelines are out of date with respect to newer DSP devices and TCK/TCKRET noise. Routing a 4-6 inch TCK/TCKRET signals is not suggested for newer designs. Instead this distance should be limited to no more then 2 inches and the provision for an AC terminator should be include as a safety precaution. Also check with your emulator supplier to see if they have JTAG header adapters that include some form of buffering and termination.
- Check with your silicon vendor as there may be known JTAG exceptions and special recommendations for the device you are using.