CCSv4.1 import ccsv3.3 import error - tcf excluded from build

Thanks. I'll do that.

Found a great article on RTSC and Eclipse

http://www.eclipse.org/proposals/rtsc/#How_RTSC_fits_into_the_Eclipse_E

Cheers

Hi Eddie,

The RTSCpedia is a great resource for all things RTSC. As John mentioned the project model in CCS4 has changed. A new type of project - RTSC configuration project - is used for consuming RTSC content like DSP/BIOS, codec engine - in CCS4.

For your use case I would recommend creating a  managed make executable and a RTSC configuration project. Add your C sources to the executable project and your 'tcf' and 'cfg' sources to the configuration project. The RTSC package path has to be setup properly in the RTSC configuration project. Also, the configuration should be enabled to consume 'tcf' files.

Given below are steps that I followed to build the MPEG4 decoder + G711 decoder  application shipped with the 64LC dvsdk v 1.00.00.20 :

The sources are available at <dvsdk_install_dir>/dvsdk_1_00_00_20/codec_combos/packages/ti/sdo/apps/mpeg4dec_g711dec

1. Create project -test- with RTSC support using the project wizard.
   
   • Refer to this flash demo on steps for creating a project with RTSC support using the wizard
   • Enable RTSC in the 'CCS Project Settings' page
   • Select 'Create a new RTSC Configuration project' in the 'Referenced RTSC Configuration' page
   • In the RTSC Configuration settings page of the wizard select 'xdais'. Add the following repositories to the package path by selecting 'Add' -> 'Select repository from file-system:' from the wizard page
   •  
     • <dvsdk_install_dir>\dvsdk_1_00_00_20\codec_engine_1_20\packages
     • <ccsv4_install_dir>\<bios_5.4x>\packages
     • <dvsdk_install_dir>\dvsdk_1_00_00_20\codec_1_10\packages
     • <dvsdk_install_dir>\dvsdk_1_00_00_20\framework_components_1_20\packages
     • <dvsdk_install_dir>\dvsdk_1_00_00_20\biosutils_1_00\packages
2. On completion the wizard will create 2 projects - 'test' and 'test_configuration' in the workspace
3. Add the files 'app.cfg' and 'app.tcf' to the project 'test_configuration'.  Since we are using old versions of some of the products add the following line to app.cfg -
   • environment['xdc.cfg.check.fatal'] = 'false';
4. Right click on test_configuration in C/C++ Project view and select C/C++ Build. Navigate to XDctools->Advanced Options: page. Select "Read infile.tcf in addition to infile.cfg(--tcf)
   
5. Add files 'app.c' and 'main.c' to the project 'test'. Build project. This should build the application.

Let me know if you face any issues in building your application.

I tried to replicate Amit's recipe above using a later CCSv4 and later DVSDK, and found I needed a few extra steps. Documenting them here, including an example project in the attachment.

The example is video_encdec from DVSDK, built for DM6437 EVM using:

• CCSv4 version 4.1.0.02003
• DVSDK 1.11.00.00 for DM6437
• XDCtools 3.16.02.32
• DSP/BIOS 5.41.02.14
• DM6437 BSP rev e

In addition to the steps above, I needed the following to build the RTSC configuration project (named "test_configuration" in Amit's recipe):

• not include BIOS6 on the RTSC package path, to avoid an error complaining that "xdc.runtime.Assert is present, but Program.system == null". If BIOS6 is on the RTSC package path then it may get selected ahead of BIOS5, and the configuration file in this example is written for BIOS5
• add the following DVSDK bundled components to the RTSC package path:
  • <dvsdk_install_dir>/edma_lld_1_05_00/packages
  • <dvsdk_install_dir>/pspdrivers_1_10_00/packages
  • <dvsdk_install_dir>/examples/common/evmDM6437
• download and install the DM6437 BSP from Spectrum Digital (http://c6000.spectrumdigital.com/evmdm6437/reve). This comes with the DM6437 EVM and if you have one of those, you probably already have this software.
• exclude "ti.rtdx" from RTSC package compatibility checking, because the BIOS5 in CCSv4 is newer than in this DVSDK. Step 3 in Amit's instructions above will do this for all packages, but I chose to use a finer-grained method that just excluded the ti.rtdx package, via the "-x" option in the "Advanced Options" panel for the XDCtools build tool (a.k.a. configuro) in CCSv4.

After this I was able to successfully build the RTSC configuration project.

The C application project (named "test" in Amit's recipe) also needed a few more steps:

• add the following source files to the app project. I added these as "linked resources" in CCSv4, but you could also copy them directly into the project:
  • <dvsdk_install_dir>/examples/common/evmDM6437/qdma_setup.h
  • <dvsdk_install_dir>/examples/common/evmDM6437/qdma_setup.c
  • <dvsdk_install_dir>/examples/common/evmDM6437/i2c_params.c
• add the following include and library search directories:
  • <bsl_install_dir>/include
  • <bsl_install_dir>/lib
• add the C preprocessor directives needed by the BSL header files:
  • CHIP_DM6437, _NTSC, and DM6437_SOC_BUILD
• add the BSL library to the linker options
  • evmdm6437bsl.lib

After this I was able to successfully build and link the application project. Not run it, though -- no board. Sorry!

The one other thing I did was to replace all the hard-coded directory paths in the CCSv4 project files with project-level macros, to make the projects a bit more portable. It's possible, though a bit laborious, to do this through the GUI, but you can also edit the .cdtbuild project files with a text editor if you're careful. It's not much different to CCS 3.3's .pjt file in that regard.

The result of all this is attached to this post. After saving the .zip file on your PC, you can use the File/Import.../Existing CCS/CCE Eclipse Project menu in CCSv4 to copy these projects into your own CCSv4 workspace. You will probably need to modify the macros to point to your own directories. Do this through the project Properties of both projects, in the C++ Build/Macros/Project sub-tab. The macros are:

• BSL_EVMDM6437_INSTALLDIR in the C application project, and
• BIOSDVSDK_INSTALL_DIR and BIOS_INSTALL_DIR in the RTSC configuration project

Hope this helps.

Jon