| Contents | Index |
| On this page… |
|---|
Configuring the D.signT DSK-91C111 to Use TCP/IP and UDP Requirements for the DM642 EVM |
Specific evaluation boards that don't have a build-in Ethernet ports accept the D.signT DSK-91C111 daughter card with the required Texas Instruments TMS320C6000 TCP/IP Stack. To use the D.signT DSK-91C111, change the position of solder point jumper JPINTPOL. Set the jumper to the "b" position from the default "a" position. Refer to your TI TCP/IP Stack User's Guide documentation for additional information about configuring the daughter card.
This section provides details about using both the DM642 EVM hardware target and the simulator.
Spectrum Digital has released three versions of the DM642 EVM board:
Version 1 — Original board with 600 MHz DM642, Philips SAA7115 video decoders. ASSY 506840 Rev. D on back of board, 50 MHz oscillator.
Version 2 — Original board revised to use 720 MHz DM642, Philips SAA7115 video decoders. ASSY 506840 Rev. D on back of board, 60 MHz oscillator.
Version 3 — Revised board with 720 MHz DM642, TI TVP5146/5150 video decoders and HD filters. ASSY 507340 Rev. B on back of board, 60 MHz oscillator.
To determine the board version, consult the documentation provided with your board, or refer to the ASSY number located on the bottom surface of the board.
After determining the board version, install the supported versions of the third-party software for that board version. See the System Requirements for the Embedded Coder software.
When you use the DM642EVM V1, V2, and V3 Target Preferences block, make sure that you enter the CPU clock speed that matches the CPU clock on your board. The figure below shows the accurate setting of 600 for Version 1 boards in CPU clock speed (MHz). For Version 2 and 3 boards, change the clock speed to 720.

If you have a DM642 EVM Version 2 or 3 board, make sure that you have the updated video drivers in your CCS IDE installation folder and that you select the accurate decoder type TVP5146 when you use DM642 EVM Video ADC blocks as shown in the following figure.

The Avnet S3ADSP DaVinci evaluation platform is designed for joint software and hardware design. It brings the Texas Instruments TMS320DM6437 DSP and Xilinx Sparta-3A FPGA together. This chapter provides an overview of the board, and instructions for installing, configuring, and using the Avnet S3ADSP DM6437.
Download and install the current Avnet Board Support Package for Simulink (Avnet BSL), available from the Avnet Web site, www.avnet.com. Doing so creates environment variables that the Embedded Coder software uses to locate files in the Avnet BSP.
Make a note of the installation folder for the Avnet BSL.
The Embedded Coder software uses environment variables to locate files in the Avnet BSP.
The MathWorks utility, setTgtEnv.m, automatically maps the following environment variables (where <Avnet BSL> is the Avnet BSL installation folder):
PSP_EVMDM6437_INSTALLDIR: must be mapped to "<Avnet BSL>\psp"
CSLR_DM6437_INSTALLDIR: must be mapped to "<Avnet BSL>\ psp\pspdrivers\soc\dm6437\dsp\inc"
NDK_INSTALL_DIR: must be mapped to "<Avnet BSL>\ndk"
Run setTgtEnv by entering the following command at the MATLAB command prompt: setTgtEnv('avnet_s3adsp_dm6437')
If you installed the Avnet BSL prior to installing the MathWorks BSL, the utility detects the AVNET_S3ADSP_DM6437_INSTALLDIR environment variable created by the Avnet BSL installer. It will automatically set the environment variables above based on the path stored in the AVNET_S3ADSP_DM6437_INSTALLDIR environment variable. On a successful run, you should see the following messages printed on the MATLAB command window:
Setting environment variable "PSP_EVMDM6437_INSTALLDIR" to C:\avnet_s3adsp_dm6437_1_06\psp"
Setting environment variable "CSLR_DM6437_INSTALLDIR" to C:\avnet_s3adsp_dm6437_1_06\psp\pspdrivers\soc\dm6437\dsp\inc"
Setting environment variable "NDK_INSTALL_DIR" to C:\avnet_s3adsp_dm6437_1_06\ndk"
If automatic mapping fails for any reason, the script will prompt you to browse for the "avnet_s3adsp_dm6437_version.txt" file stored in the top-level Avnet BSL installation folder. If so, browse for the file and click the Open button. This will set the required environment variables.
If you have a Spectrum Digital DM6437EVM board together with an Avnet S3ADSP DM6437 board, setting environment for the Avnet board as explained in section 2.3 will override DM6437EVM environment setup. To revert back to DM6437EVM environment after using Avnet board, execute the following at the MATLAB command prompt: setTgtEnv('dm6437evm')
Follow the instructions printed on the MATLAB command window to complete environment configuration. To go back and forth between DM6437EVM environment and Avnet S3ADSP DM6437 environment, use the setTgtEnv script with the right platform name specified as the argument.
Open the Avnet S3ADSP Board Support Library by entering the following command at the MATLAB command prompt: avnet_s3adsp_dm6437 This opens the Avnet Spartan–3A DSP DaVinci Evaluation Platform Board Support Library. You have completed installing and configuring the MathWorks and Avnet Board Support Libraries. You are ready to start using the Avnet S3ADSP DaVinci evaluation platform.
This section details some target operations that you should know about as you use Embedded Coder software.
The C6713DSK PLL is not automatically set to the right CPU Clock frequency when you try to target the board. When you power-up your DSK, it runs at a clock speed of 50 MHz. However, the C6713 is capable of running at 225 MHz.
If you generate code incorporating the DSP/BIOS real-time operating system, the PLL is automatically configured for you at run-time to use the right clock speed. If you are not using DSP/BIOS in your project, you must manually configure the PLL to the right clock rate before running your code.
Setting the PLL to Drive the CPU at 225 MHz. To set the C6713 DSK PLL to drive the CPU at 225 MHz, perform the following steps. Be sure you have defined your GEL file for your DSK in the Setup Utility for CCS IDE.
To make this happen whenever you open Code Composer Studio to use your C6713 DSK, edit the file \ti\IDE_Obj\gel\dsk6713.gel. Add the following command to the StartUp() function:
init_pll();
This tells the GEL file to initialize the PLL to operate at 225 MHz.
On the DM642 EVM, ADC-DAC Loopback Displays An RGB Image Incorrectly After Power-Up. When you set up the DM642 EVM to use loopback from the ADC to the DAC, the DAC block does not reproduce the captured image accurately immediately after you power up the board. Colors in the image are not shown accurately.
To get a clean image, reload the program to the target and run the program again. This also happens with the examples Texas Instruments ships with the DM642 EVM product.
If you are using the Simulink Stop block in your model, but you are not using DSP/BIOS features, your model might take longer to stop when it is running on the target than if you are using DSP/BIOS.
The condition the model uses to detect the stop processing flag is different when you do not use DSP/BIOS. The result is that the model may not detect and respond to the flag as promptly, taking longer to stop the running model on the target processor.
For a list of required third-party target packages, with version numbers, see the Embedded Coder System Requirements page at http://www.mathworks.com/products/target-package/requirements.html.
When you install any of the third-party target packages listed below, perform a default installation using the installation path provided for that package and perform any additional steps given.
This documentation uses placeholders for portions of the installation path that may vary by software version or environment. Please replace the placeholders with the path information for your software environment. For example, if the CCS IDE installation path is C:\CCStudio_v3.3, then enter C:\CCStudio_v3.3\boards\evmdm642 instead of <CCStudio_vn.n>\boards\evmdm642.
Placeholders:
<CCStudio_vn.n> — The installation path for Code Composer Studio
<n.n> — Version-specific path information
Note If you do not use the installation paths provided, update the Libraries and Include paths parameters in the Target Preferences and C6000 IP Config blocks of the Embedded Coder™ software with accurate paths. Otherwise, the software produces error messages when you attempt to generate code. |
Spectrum Digital EVMDM642 Board Support Package — <CCSvn.n>\boards\evmdm642
TI's Network Developer's Kit (NDK) — <CCSvn.n>\C6000\NDK
DM642EVM Version 1 & 2 Boards.
Spectrum Digital EVMDM642 Board Support Package — <CCSvn.n>\boards\evmdm642
Device Driver Developer's Kit (DDK) — <CCSvn.n>\ddk
TI's Network Developer's Kit (NDK) — <CCSvn.n>\C6000\NDK
Spectrum Digital DM6437EVM DVSDK RTM — Install anywhere. TI recommends using the root path of your main drive. For example, C:\dvsdk_<n.n>
Also, set the following environment variables, replacing DVSK with the DVSDK installation path (e.g., C:\dvsdk_<n.n>).
The first time you generate code, the Embedded Coder™ software prompts you to locate specific files in the DVDSK folders and creates environment variables mapped to the location of required folders. For example, the application creates an environment variable called CSLR_DM6437_INSTALLDIR for the path of the Register Layer Chip Support Library.
C6455DSK. Spectrum Digital DSK6455/EVM6455 Target Content Package — <CCSvn.n>\boards\dsk6455_v<n.n>
Network Developer's Kit NDK — <CCSvn.n>\C6000\NDK
C6727PADK. Lyrtech's PADK Software — Install anywhere.
TI's C672x Chip Support Libraries (CSL) — Extract all three C672x CSL components from sprc223.zip to <CCSvn.n>\boards\C6727PADK.
TI's System Patch Code, FastRts(V<n.n>)/DSPLIB (V<n.n>) — <CCSvn.n>\boards\C6727PADK\sprc203
After installation, the path structure for the C672x CSL libraries should resemble the following figure:

The PADK Software installer automatically sets the PADK_DIR environment variable with the accurate installation path.
The first time you generate code, the Embedded Coder™ software prompts you to locate the following files under <CCSvn.n>\boards\C6727PADK\ and sets the environment variables accordingly:
$(CSL_C672x_INSTALLDIR)\lib\csl_C6727.lib
$(CSL_C672x_INTC_INSTALLDIR)\lib\csl_C672x_intc.lib
$(SYSPATCH_C672x_INSTALLDIR)\applySystemPatch.obj
You have completed installation of the third-party softwares.
![]() | Configuring Timing Parameters for CAN Blocks | Working with Wind River VxWorks RTOS | ![]() |

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |