Hi Weichun,

Just so I can understand the problem better, what is your end-goal?  Are you looking to run the ECU within the simulator to better understand the operation, or are you integrating it into an existing codebase and trying to compile?

Also, what VoLIB release are you using?  If you are using 1.0.0, and would like to run the ECU in the simulator, I would suggest downloading VoLIB patch release 1.0.1.  The patch release comes with CCS projects such that getting up and running is an order of magnitude easier.

Regards,

Charlie

Hi, Charlie,

thank you so much for helping out.

My ultimate goal is migrating my platform from C55 to C64x+. I am looking at using VoLib ecu to replace my old echo canceller. I might not have the luxary to run the full DSPBios/SysBios and the xdc tools. Therefore, my thought is to extract the ECU from the testbed, understand its operation, both from top (API) and bottom (such as how ECU is coupled with DSPBios, and in particular, how does it allocate the memory). Run the bare ECU within a simple main() through some test vectors, first on simulator, then on an eval board with cache on, get the MIPS. Then, I hope I can integrate the ECU into my platform.

I've downloaded VoLib 1.0.1, but could not follow the build instruction under its ECU integration section. It told me that I need config.bld which is not available.

You mentioned that VoLIB patch 1.0.1 comes with CCS project. You mean the new CCS 4.0 project or the traditional CCS3.x pjt project? Do you have any link/step by step guide to build and load the CCS project. -- I am completely new to CCS 4.x and the associated XDC tools.

Regards

Weichun

Charlie,

the following is the instruction I am following to build. The red marked portion shows the error message. Anything comes to your mind?

thanks again

Weichun

ECU Integration

Page Contents

• XDC Build Process
• Make Build Process
• Linking ECU with System
• Initialization Structures

XDC Build Process

Required Tools

The following tools are required to build the ECU component (links provided). Download and install all tools to a single local (C:) directory, for example c:\tools.

1. Code Generation (download)
   • C55xx: CG Tools version 4.1.0
   • C64xx: CG Tools version 6.0.15
2. XDC (download)
   • XDC Tools version 3.20.0.41
3. xDAIS (download)
   • xDAIS Developer's Kit version 5.21

Windows Configuration

Once all tools are properly installed, the environment will need to be configured to recognize the tool paths. A Windows batch file should be created to provide a consistent manner to achieve this. The example below can used (cut & paste) to create a setenv.bat batch file in the ...\ti\mas\swtools directory.

    @echo off
    rem # *************************************************************************
    rem # *** Version information (ONLY EDIT THIS SECTION)
    rem # *************************************************************************
    set LOCAL_TOOLSDIR=tools
    set XDCBASE=xdctools_3_20_00_41
    set C55CODEGENBASE=cgen_4_0_1
    set C64CODEGENBASE=cgen_6_0_15
    set XDAISBASE=xdais_5_21

    rem # *************************************************************************
    rem # *** Set up tools directory
    rem # *************************************************************************
    set LOCAL_TOOLSDIR_DOS=c:\%LOCAL_TOOLSDIR%

    rem # *************************************************************************
    rem # ** Set code generation tools path
    rem # *************************************************************************
    set C55CODEGENTOOL=%LOCAL_TOOLSDIR_DOS%\%C55CODEGENBASE%
    set C64CODEGENTOOL=%LOCAL_TOOLSDIR_DOS%\%C64CODEGENBASE%

    rem # *************************************************************************
    rem # ** Set the PATH
    rem # *************************************************************************
    set PATH=%SystemRoot%;%SystemRoot%\system32
    set PATH=%PATH%;%LOCAL_TOOLSDIR_DOS%\%XDCBASE%

    rem # *************************************************************************
    rem # ** Create environment variables for XDC
    rem # *************************************************************************
    set XDCCGROOT=%LOCAL_TOOLSDIR_DOS%
    set xdc=\%LOCAL_TOOLSDIR%\%XDCBASE%\xdc.exe $*

    rem # *************************************************************************
    rem # ** Set the XDC PATH
    rem # *************************************************************************
    set XDCPATH=%LOCAL_TOOLSDIR_DOS%\%XDCBASE%\packages
    set XDCPATH=%XDCPATH%;%LOCAL_TOOLSDIR_DOS%\%XDAISBASE%\packages

    rem # *************************************************************************
    rem # ** Identify the config.bld file
    rem # *************************************************************************
    xs -f setconfig.js
    call tempcfg
    del tempcfg.bat

    rem # End of file
   

Linux Configuration

TBD

Compilation

To build the ECU package, ensure (again) that all packages provided with the build have been extracted to a common working directory (as described in ECU Integration). Change to the swtools directory and configure the build environment by executing the setenv.bat batch file. To build the ECU using the XDC tools, change to the ECU directory and proceed.

response of the setenv.bat (in my case, setupVoiceLib.bat)

C:\debug\volib_C64P_1_0_0_1\packages\ti\mas\swtools>copy h:\tools\bin\setupVoiceLib.bat .
        1 file(s) copied.
 Error: config.bld not found in swtools directory
 WYWY: we do not exit for now
xs -f setconfig.js is done
call tempcfg is done

C:\debug\volib_C64P_1_0_0_1\packages\ti\mas\swtools>

With the environment configured, XDC may be eployed to build the ECU and its dependent packages. The four XDC commands below are all that is needed to clean and build any of the ECU packages. The first two commands provide a means to clean and build the ECU package (alone). Nothing further is needed unless the source for a dependent packages has changed.

If the source for any of the dependent packages has changed, commands (3) and (4) below provide a mechanism to clean and build both the ECU and all dependent packages.

Hi Weichun,

Yes, the projects provided with VoLIB 1.0.1 are for CCS version 4 and above.  Getting up and running with CCS version 4 can be a little vexing due to the new Eclipse environment, though I believe loading and building a project should be relatively easy.

Try the following and let me know how it goes:

1. Open CCS v4
2. Select the "C/C++ Perspective" button (upper right hand corner)
3. Under the "Project" menu, select "Import Existing CCS/CCE Eclpise Project"
4. Set the search directory to <VOLIB_ROOT>/packages/ti/mas/ecu/test (where <VOLIB_ROOT> is the installation directory)
   
5. You should see projects in the  "Discovered Projects" pane
6. Select one and proceed...

You should be able to rebuild the project without issue.

Regards,

Charlie

Hi Weichun,

Just curious -- do you have a config.bld file in your swtools directory?  The installation should provide this.

Regards,

Charlie

Hi, Charlie,

I followed your instruction, but under my directory, CCS4.0 can not find any projects. The following is the content of my ecu/test directory--I could not find anything like .project or .ccsproject. Do you think I missed anything during the installation? But the installation seemed to be simple and straightforward.

Is there any prerequiresit before I install voiceLib?

thanks

Weichun

C:\debug\volib_C64P_1_0_0_1\packages\ti\mas\ecu\test>dir
 Volume in drive C has no label.
 Volume Serial Number is B4BA-66CF

 Directory of C:\debug\volib_C64P_1_0_0_1\packages\ti\mas\ecu\test

07/12/2011  12:01 PM    <DIR>          .
07/12/2011  12:01 PM    <DIR>          ..
07/12/2011  12:01 PM    <DIR>          docs
07/12/2011  12:01 PM    <DIR>          lnkr
10/08/2008  09:01 AM               717 Makedocs.mk
09/30/2010  03:00 PM             2,945 makefile
07/12/2011  12:01 PM    <DIR>          package
08/03/2010  07:03 PM            10,826 package.bld
09/24/2010  12:00 PM             2,514 package.xdc
07/12/2011  12:01 PM    <DIR>          src
10/08/2008  09:02 AM               674 test.cfg
07/12/2011  12:01 PM    <DIR>          testvec
               5 File(s)         17,676 bytes
               7 Dir(s)  57,896,701,952 bytes free