HELP! Using BIOS 5.33.05 with DSP Link and CCS v4

Judson,

Here is how you can set up a CCS4 project to build the DSP side for a DSPLink OMAPL138 application:

• First build dsplink libraries using the makefiles provided.

• Look here for setting up an empty BIOS CCS4 project: http://rtsc.eclipse.org/docs-tip/Demo_of_DSP/BIOS_5.x_Project_Creation_in_CCSv4

             For me, I found the "Empty DSP/BIOS v5.xx Project" under "BIOS Examples", and not under "Empty Projects" as shown in the link.

• Once you have created the project, you can add the source files to your project.

• You will need to add a bunch of include paths and defines to your project for it to build.  An easy way to do this is to use the text files IPS_defines.txt and IPS_includes.txt that got  generated when DspLink was built.  You can find these two files in:

                 dsplink_linux_1_65_00_03\dsplink\dsp\export\BIN\DspBios\OMAPL138\OMAPL138GEM_0\DEBUG

           In your CCS4 project properties, add these two files under Tool Settings -> C6000 Compiler -> Command Files

• If your .tcf file includes other files in different locations, you will need to add those directories to Tool Settings -> TConf Script Compiler -> General Options

• Add the dsplink libraries to the library search path (Tool Settings -> C6000 Linker -> File Search Path).

Then your project should build.  I tried this with the DspLink message example, and I have attached an archive file with my project.  I had to modify one of the .tci files to get it to build, and I had to also add TSK_MODE to the defined symbols.

Best regards,

    Janet

6471.message_ccs4_pjt.rar

Judson,

Thanks for your additional comments.  Regarding the DSP/BIOS version, in CCS 4, I was able to select the BIOS version of the project by:

    Project -> Properties -> CCS Build

There I found a drop down list of the BIOS versions I had installed.  I was also add a version installed on the network by clicking on "More" and navigating to it.  This may have been an issue with older versions of CCS 4.  I am using CCS 4.2.4.00034.

As for the .tcf file, you don't actually have to merge them.  If you don't merge them, you will need to add the path to the included .tci files to the Configuration import path.  To do this, go to

    Project -> Properties -> C/C++ Build -> TConf Script Compiler -> General Options

and add the directory to "Configuration import path".  For example, I added:

    I:\jeh\dsplink_linux_1_65_00_03\dsplink\dsp\inc\DspBios\5.XX\OMAPL138GEM

I also made a copy of dsplink-omapl138gem-base.tci, calling it dsplink-omapl138gem-base-ccs.tci, and replaced the line:

    prog.module("GBL").PROCID          = parseInt (arguments [0]) ;

with

    prog.module("GBL").PROCID          = 0 ;

I then included dsplink-omapl138gem-base-ccs.tci, in message.tcf.

Also, I wanted to repeat the process, using another example, to more clearly document my steps.  So I tried this with the dsplink mp_list sample.  Here are the steps that I did:

• Create a new CCS 4 project. (File -> New -> CCS Project).

            This time, for some reason, the Empty BIOS project was not available as a template, so I chose

                DSP/BIOS v5.xx Examples -> evmOMAPL138 Examples -> hello example

• Add the mp_list files to the project:  Select "Project -> Add files" and browse to the dsplink/dsp/src/samples/mp_list. Select the .c, .h, and .tci files in this directory.  Similarly, add mp_list.tcf (located in dsplink/dsp/src/samples/mp_list/DspBios/5.XX/OMAPL138GEM) to the project.

• Remove hello.c and hello.tcf from the project.

• Copy dsplink/dsp/export/BIN/DspBios/OMAPL138/OMAPL138GEM_0/DEBUG/IPS_defines.txt and IPS_includes.txt to your project directory.  Since I had built dsplink libraries on Linux, I had to replace the share names in IPS_includes.txt with the appropriate drive letters for my Windows machine.  I probably could have used MESSAGE_defines.txt and MESSAGE_includes.txt, but for this example, IPS worked.

• Add the IPS_defines.txt and IPS_includes.txt to the C6000 Compiler command files:

                 Project -> Properties -> C/C++ Build -> Tool Settings -> C6000 Compiler -> Command Files

• Add the project directory to the include search path (Project -> Properties -> C/C++ Build -> Tool Settings -> C6000 Compiler -> Include Options). (This is necessary because sample source code .c files includes files header files in the same directory with <> instead or "").

• Make a copy of dsplink-omapl138gem-base.tci, and replace the line in your copy:

            prog.module("GBL").PROCID          = parseInt (arguments [0]) ;

             with

           prog.module("GBL").PROCID          = 0 ;

• Edit mp_list.tcf to include your copy of dsplink-omapl138gem-base.tci

• Add the path to your copy of dsplink-omapl138gem-base.tci to the Configuration import path under:

                 Project -> Properties -> C/C++ Build -> TConf Script Compiler -> General Options

• Add the dsplink libraries to the project:

                 Project -> Properties -> C/C++ Build -> C6000 Linker -> File Search Path

            I added I:\jeh\dsplink_linux_1_65_00_03\dsplink\dsp\export\BIN\DspBios\OMAPL138\OMAPL138GEM_0\DEBUG to the library search path,

            and the following libraries:

dsplink.lib

dsplinkmpcs.lib

dsplinkmplist.lib

dsplinkpool.lib

dsplinkmsg.lib

dsplinknotify.lib

After doing the above steps, my project built without errors.  I am attaching an archive of this workspace also.

4073.ccs4_mp_list.rar

Best regards,

    Janet