This FAQ applies to DSK development kits manufactured by Spectrum Digital. At the current time, this includes the:
DSK6713 Specific Issues
1.1 Problems when using Xilinx 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.
- Uninstall the Xilinx tools.
- Go to the windows/system32/drivers directory and remove mlnxfltr.sys and mltilnx.sys.
- Unplug your DSK.
- Go to your Windows device manager (from the Control Panel) and delete any USB hubs.
- Reboot your PC, Windows will restore support for the hubs.
- 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.
- 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".
- 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
1.2 Diagnostic utility won't run if installed in a path with spaces
Versions of the diagnostic utility prior to 1.10 have a bug that prevent the utility from properly locating the embedded emulator driver files if the DSK version of Code Composer was installed in a directory with spaces in its pathname. For example, if Code Composer is installed in:
the diagnostic utility will pop up an error in a dialog box that reads (the error message will be slightly different based on which DSK you are using):
Can't load driver Files\ti\drivers\5510DSKDiag.exe
You can either re-install the software in a different location without spaces in the path (like c:\ti) or just copy the ti\drivers directory to a new path without spaces and run the diagnostic utility manually from there.
1.3 Which external emulator/Code Composer versions can be used together?
DSKs come bundled with a special version of Code Composer that only works with the on-board JTAG emulator. Some rules of thumb are:
- The full version of Code Composer can make use of either the on-board JTAG emulator or an external emulator. The DSK version of Code Composer will only work with the on-board JTAG emulator.
- You cannot use the on-board emulator to debug a non-DSK target.
- An external JTAG emulator will only work with the full version of Code Composer.
If you are designing your own hardware you will need the full version of Code Composer as well as an external JTAG emulator. Spectrum Digital offers its XDS510 USB JTAG Emulator as a direct replacement for DSK users looking to upgrade to an external emulator, other emulators are available from Texas Instruments and other vendors.
1.4 How do I use a DSK with the Reference Frameworks or DDK?
The original DSK releases do not correspond directly with Code Composer versions such as 2.20 or 2.21. TI software releases such as the Reference Frameworks or DDK are generally targeted with users of the full version of Code Composer in mind and therefore ship with code that matches BIOS versions that ship with the full versions.
Both the Reference Frameworks and can be re-built on DSK versions of Composer using a script provided at the base of the RF or DDK install trees. This script will rebuild all of the BIOS configuration (.cdb) files in the examples using the version of Code Composer you are using. Instructions on how to run the scripts are provided in the RF and DDK release notes. For example, the RF release notes from dspvillage.ti.com can be found here:
2.1 Daughtercard Access
The convention when using TI daughtercards is to have the daughtercard pull down the DC_DETECT pin (pin 75 on the peripheral expansion connector). On the 5510 DSK, pulling this pin low will enable the power supply and data buffers to the daughtercard connectors.
The X_RESET pin (pin 59 on the peripheral expansion connector) is used as a daughtercard reset. When power is applied to the DSK the X_RESET will be held low until the power supplies are stable then driven high by the CPLD. For most daughtercards this provides the desired reset behavior. However, you can reset the daughtercard again in software by toggling the DC_RESET bit in the CPLD register. See the 6713 DSK help file for more information about the CPLD registers.
2.2 Can the DSP access the USB port directly?
The USB port is only connected to the on-board USB JTAG emulator on the DSK. Other than the JTAG signals needed for emulation, there are no communications signals from the USB emulation section to the DSP. There is no way for the DSP to communicate through the USB interface other than through the JTAG emulator.
2.3 Optional Power Connector(J6) part number correction.
The part number for teh Optional Power Connector(J6) in the DSK Technical Reference has been updated. The incorrect part number printed in the reference previously is Molex #15-24-4041. The correct part number is:
Tyco Electronics #174552-1
DSK6713 Specific Issues
3.1 How do I use the full 512Kb of Flash?
The Flash on the 6713 DSK is arranged as a 256Kb x 16 device, but the software and board are configured to use CE1 (the chip enable space the Flash is in) in 8-bit mode to match other C6x DSKs. The net effect is that people using the DSK software as-is will only see 256Kb of Flash.
To use the full 512Kb, follow these steps:
- This is a fairly complex process so make sure you're familiar with the existing FlashBurn process at 8-bit Flash widths before you change anything. Look in the DSK help file for more info on this.
- Create a new GEL file that sets CE1 up for 16-bit mode instead of 8-bit.
- Create a new copy of the FlashBurn algorithm in c:\ti\bin\utilities\flashburn\c6000\dsk6713 to write to all 16-bits of Flash instead of only the lower 8 bits. To make your life easier, you may want to make sure that all of your code sections are aligned to 16-bit boundaries so you don't have to handle the special case of odd length sections in the FlashBurn algorithm.
- If you're using the BSL, modify the BSL to work with CE1 in 16-bit mode. The affected portions are all in dsk6713.c. You should modify the EMIF setup to configure CE1 as 16-bits, and the CPLD register address offsets in DSK6713_rget() and DSK6713_rset() have to be multiplied by two because the registers will appear to be 16-bits apart rather than 8.
- Recompile your application and build a new hex file using hex6x options for 16-bit wide memory rather than 8-bit
- Put your application in Flash using FlashBurn and your 16-bit wide version of the FlashBurn programmming algorithm.
- Power your board off and set the boot mode config switches (SW3) for 16-bit mode instead of 8-bit mode.