Ccs3.3 installation and configuration of dvsdk Environment Parameters

I recently used TI's tms320dm6437 processor. After installing ccs3.3, I installed dvsdk again. however, we found that the example under the pspdriver could not be compiled. After several days of research, we finally found some environment configuration details for you to share.

1. to install ccs3.3, we recommend that you install the default path "C:/ccstudio_v3.3". Follow the prompts during installation. You can cancel the installation of the "Ti emulator driver" option on some XP systems, if you do not cancel the installation, it will crash after the installation is complete. The reason is unknown.

2. after ccs3.3 is installed, install dvsdk again. We recommend that you install the mo path "C:/dvsdk_201711_00_00". The installation process will prompt you to install the latest DSP/bios. You can choose not to install it, if it is installed, bios_5_3x_xx, a sub-directory in the ccs3.3 directory, may be different from the DSP/BIOS version that comes with ccs3.3. X is the version number, which varies depending on the actual situation)

3. After the above two software are installed, you must set the system environment variables for compilation tool chain. The specific parameter settings are as follows (if it is installed on the default path)

Bios_install_dir C:/ccstudio_v3.3/bios_5_31_08

Biosdvsdk_install_dir C:/dvsdk_201711_00_00

Biosutils_install_dir C:/dvsdk_1_11_00_00/biosutils_000000_02

Bsl_evmdm6437_installdir C:/ccstudio_v3.3/boards/icetek-Dm6437-B _v2

Ce_install_dir C:/dvsdk_1_11_00_00/codec_engine_1_20_02

Dvsdk_install_dir C:/dvsdk_1_11_00_00

Ndk_install_dir C:/dvsdk_1_11_00_00/ndk_1_92_00_22_eval

Psp_include_soc_pathDm6437

Psp_install_dir C:/dvsdk_1_11_00_00/pspdrivers_1_10_00/Packages

Xdc_install_dir C:/dvsdk_201711_00_00/xdc_2_95_02

4. After the configuration is complete, all the examples in ccs3.3/bios_1_xx_xx can be compiled and run. However, examples in C:/dvsdk_201711_00_00/pspdrivers_000010_00 cannot be compiled. Directory C:/dvsdk_201711_00_00/pspdrivers_000010_00/packages/Ti/SDO/pspdrivers/system/Dm6437Examples in/bios/evmdm6437/UART describe how to configure and enable normal compilation of example.

5. use ccs3.3 to open the project file "utils". If an error occurs when you open the hosts file, right-click "dm6437_evm_uart_st_sample.tcf" and choose "DSP/BIOS config-> text edit. importfile ("Ti/SDO/pspdrivers/system/Dm6437/Bios/evmdm6437/UART/dm6437_uart0.tci ");

"

Replace

Utils. importfile ("dm6437_uart0.tci ");

Save.

In this way, the script file runs normally. However, some files cannot be found during compilation. This is because the path in the path file read by the xdc tool is not set

The setting method is as follows:

Open C:/dvsdk_1_11_00_00/pspdrivers_1_10_00/packages/Ti/SDO/pspdrivers/common/psp_xdcpaths_common.dat

The content is as follows:

-------------------------

// Do not move or delete this line [JavaScript xdcpaths]

// Note: Use/forward/slashes for all directories!

// Section for non-dvsdk users

// Section 1 starts

// Root directory for the PSP drivers Installation

// User shocould modify this variable to point it to the root directory

// Of PSP installation directory.

Psprootdir = "C:/dvsdk_201711_00_00 /";

// PSP version number

// If working from clearcase, this variable shocould be null as shown below:

// Pspversion = "";

Pspversion = "201710_00 ";

// PSP installation directory

// It is the directory where PSP is installed.

Pspinstalldir = "pspdrivers _" + pspversion;

// Edma3 installation directory

// It is the directory where edma3 LLD is installed.

Edma3installdir = "C:/dvsdk_201711_00_00/edma3_lld_000005_00 ";

Xdcpaths =

// Edma3 build directory

Edma3installdir + "/packages;" +

// PSP drivers build directory

Psprootdir + pspinstalldir + "/packages;" +

"";

// Section 1 ends

// Section for dvsdk users

// Section 2 starts

/**

* For making a release to the dvsdk, Section 1 abve needs to be commented and

* The code below needs to be un-commented. This is needed in order to include

* The dvsdk DAT file, so that the standalone Sample Apps can be built.

*/

/*

// Var xdcpathsfile;

// Function getwindowsenvironmentvar (envvarname)

//{

// Var temp = java. Io. file. createtempfile ("envvarechoer", ". Bat ");

// Temp. deleteonexit ();

// Var out = new java. Io. bufferedwriter (New java. Io. filewriter (temp ));

// Out. Write ("@ echo %" + envvarname + "% ");

// Out. Close ();

//

// Var runtime = java. Lang. runtime. getruntime ();

// Var proc = runtime.exe C (temp. getpath ());

// Var status = Proc. waitfor ();

//

// Var envvar = java. Io. bufferedreader (New

// Java. Io. inputstreamreader (Proc. getinputstream (). Readline ();

// If (envvar = "Echo is on ."){

// Envvar = "";

//}

// Return (envvar + ""). Replace ("//", "/", "G ");

//}

//

// Xdcpathsfile = This. xdcpathsfile;

//

// This. xdcpathsfile = getwindowsenvironmentvar ("biosdvsdk_install_dir ");

//

// Print ("xdcpaths-common.dat> using biosdvsdk_install_dir =" + this. xdcpathsfile );

//

// If (xdcpathsfile = ""){

// Throw "error: Windows environment variable biosdvsdk_install_dir is not set. Please run start-> Control Panel-> ..."

//}

//

// Load (xdcpathsfile + "/xdcpaths_evmdm648.dat ");

// Section 2 ends */

-------------------------

The above settings are based on the installation path on my computer, that is, the default installation path recommended by TI. If you do not use the default installation path, set the environment variables and modify the file according to the actual path.

Now, the environment is configured. Compilation can also pass normally.