NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide

From Texas Instruments Wiki
Jump to: navigation, search

TIBanner.png


Desktop Linux SDK


Version 1.0.0.4 Alpha Release

Guide to rebuild DSP images

Last updated: 12/14/2012


Introduction[edit]


(Note: This page has the instructions for the latest Desktop linux sdk 01.00.00 (version 01.00.00.04)release. If you are using a release older than 01.00.00.04. Please check specific instructions in the archived section below :Archived Pages )

The Desktop Linux SDK includes the DSP images to run the demo applications and the demos can work out of the box, The package also include the required sources to rebuild the DSP image. If required, the source code can be modified and dsp images can be rebuilt using the procedures on this page.

Required Compile Tools[edit]

To rebuild the DSP images, the following packages are needed.

  1. CCS 5.1 or higher
  2. TI MCSDK for TMS320C66x Processors V.2.0.3.15 or higher Refer to website: http://focus.ti.com/docs/toolsw/folders/print/bioslinuxmcsdk.html


The Desktop Linux SDK dsp builds use the platform part of MCSDK 2.0 [MCSDK Getting Started Guide, MCSDK User's Guide] to achieve platform abstraction.

Re-building of the image first requires patching the platform library which is part of the MCSDK package, for the Advantech platform.

Platform library patch and re-build instruction[edit]

[Note: This step is not required for the EVM Single C6678 card]
If you are using the Advantech Quad C6678 or Octal C6678 platform, the platform library in the MCSDK has to be patched to create library corresponding to the Advantech Card.

Steps to patch and build the platform library for are as follows (The instructions are for pdk_c6678_1_0_0_21. Similar procedure to be followed for other pdk releases, with the change in directory names)

1. Patch the platform files for DSPC8681 and DSCPC8682 in the PDK:
Copy the directory “desktop-linux-sdk\sdk\platform_patch\dspc8681” and paste to “<pdk_install_directory>/pdk_C6678_1_0_0_21/packages/ti/platform/
Copy the directory “desktop-linux-sdk\sdk\platform_patch\dspc8682” and paste to “<pdk_install_directory>/pdk_C6678_1_0_0_21/packages/ti/platform/
Copy the csl patch from “desktop-linux-sdk\sdk\platform_patch\csl_patch\packages” and paste to “<pdk_install_directory>/pdk_C6678_1_0_0_21/packages
2. Import the CCS project from "<pdk_install_directory>pdk_C6678_1_0_0_21\packages\ti\platform\dspc8681\platform_lib" directory or
"<pdk_install_directory>pdk_C6678_1_0_0_21\packages\ti\platform\dspc8681\platform_lib" according to what library is needed.
(In CCSv5, Project->Import Existing CCS/CCE Eclipse Projects)
Screenshot_Platform_build_import.png
3. Select "Lite" as active configuration (in CCSv5, Project->Properties)
DLSDK_Screenshot_LiteActiveset_dspc8681.png
Choose "Lite" Click Set Active button. Click OK Set Configuration to Lite
DLSDK Screenshot LiteActiveset.png
4. Clean the platform_lib_evmc6678l project and re-build the project. After build is completed the ti.platform.<dspc8681|dspc8682>.lite.lib will be generated under the directory: "pdk_C6678_1_0_0_21\packages\ti\platform\<dspc8681|dspc8682>\platform_lib\lib\debug"
5. Repeat step 3 and step 4, select "Debug" as active configuration and re-build the project: ti.platform.<dspc8681|dspc8682>.ae66 will be generated under the same directory

Demo DSP test image build instruction[edit]

The DSP image used by the “filetestdemo” can be built by using the DSP projects under the directory: desktop-linux-sdk/filetestdemo/c66x/demo_loopback.

1. Go to directory: “\desktop-linux-sdk\demos\filetestdemo\c66x\demo_loopback/build” and open macros.ini.

2. Edit macros.ini to update the PDK_C6678_INSTALL directory to where the PDK package under MCSDK is installed in the system. And DESKTOP_LINUX_SDK_DIR to where the desktop Linux SDK is installed.

(For example :

- Windows:

TI_PDK_C6678_INSTALL_DIR=”c:\Program Files\Texas Instruments\pdk_C6678_1_0_0_21”
DESKTOP_LINUX_SDK_DIR=”c:\desktop-linux-sdk”

- Linux:

TI_PDK_C6678_INSTALL_DIR =/home/username/ti/pdk_C6678_1_0_0_21
DESKTOP_LINUX_SDK_DIR=/home/username/ti/desktop-linux-sdk_01_00_00_04

)

3. Import the demo_loopback CCS project from “desktop-linux-sdk\demos\filetestdemo\c66x\demo_loopback\build” directory. ( In CCSv5, Project -> Import Existing CCS/CCE Eclipse Projects)
and click finish
DLSDK Screenshot Import demo project.png

4. Clean the demo_loopback project ( Using Project -> Clean ) and build the project ( Project -> Build Project). After build is completed the build files: demo_loopback.out and demo_loopback.map will be generated under the following directory: desktop-linux-sdk\demos\filetestdemo\c66x\demo_loopback\build\Debug

DSP init image build instruction[edit]

The init DSP image is used as a boot image to initialize the DDR and Ethernet switch. The DSP build can be built from the project directory: “desktop-linux-sdk_<versionno>\sdk\dsp_projects\dsp_init\build”.

1. Go to directory: “desktop-linux-sdk_<versionno>\sdk\dsp_projects\dsp_init\build”. and open macros.ini.

2. Edit macros.ini to update the TI_PDK_C6678_INSTALL directory to where the PDK package under MCSDK is installed in the system. And DESKTOP_LINUX_SDK_DIR to where the Desktop Linux SDK is installed.

(For example :

- Windows:

TI_PDK_C6678_INSTALL_DIR=c:\Program Files\Texas Instruments\pdk_C6678_1_0_0_21
DESKTOP_LINUX_SDK_DIR=c:\desktop-linux-sdk_01_00_00_01

- Linux:

TI_PDK_C6678_INSTALL_DIR =/opt/ti/pdk_C6678_1_0_0_21
DESKTOP_LINUX_SDK_DIR=/opt/ti/desktop-linux-sdk_01_00_00_01

)

3. Import the demo_loopback CCS project from “desktop-linux-sdk_<versionno>\sdk\dsp_projects\dsp_init\build” directory. ( In CCSv5, Project -> Import Existing CCS/CCE Eclipse Projects)
DLSDK_Screenshot_ImportInitProject.png

4. Choose the platform to be used for the compilation. ( In CCSv5: Click Project -> Properties. On the window that opens Select 'Build' and click on 'Variables' tab. By default the platform is evmc6678. If building for a different platform (DSPC8681 or DSPC8682). Edit the following two variables: PLATFORM_NAME & PLATFORM_DIR_NAME to <dspc8681|dspc8682>
DLSDK_Screenshot_demo_platformselection.png DLSDK_Screenshot_PLATFORM_DIR_NAME_DSPC8681.png DLSDK_Screenshot_PLATFORM_NAME_DSPC8681.png DLSDK_Screenshot_demo_platform_set.png

5. Clean the project using (Project -> Clean) and build the project using (Project -> Build Project). After build is completed the build files: init.out and init.map will be generated under the directory: “desktop-linux-sdk_<versionno>\sdk\dsp_projects\dsp_init\build\Release”

Copy the built images into the appropriate folder dspc8681, dspc8681, evm6678 or evm6678 in the demos/dsp_images folder.

Archived Pages[edit]

Related Links[edit]

Technical Support and Product Updates[edit]

For technical discussions and issues, please visit

NoteNote: When asking for help in the forum you should tag your posts in the Subject with “DESKTOP-LINUX-SDK” and the part number (e.g. “C6678”)

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article Desktop-linux-sdk 01.00.00.04 DSP Rebuild Guide here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity