building XDAIS algorithms

building XDAIS algorithms

[Carlos Davila]

Hello,

I have been adapting the base RF6 application that comes with the TI 
Linux Dsp Tools. The base application implements an FIR filter and a 
volume control. The executable code that implements the XDAIS FIR filter 
algorithm comes in library files located in the rf_3_11_dsp/lib 
directory and appears to have already been built, i.e. the executable 
XDAIS FIR algorithm code is not built when the dsp side RF6 application 
is built, rather, it appears to have been built with code composer 
studio using the project file in rf_3_11_dsp/src/fir_ti/. Is it possible 
to build the dsp-side XDAIS algorithm executables using only the Linux 
DSP Tools or the montavista tools, without CCS?

Thank you,
Carlos

RE: building XDAIS algorithms

[Hunter, Jon]

Hi Carlos, 

> I have been adapting the base RF6 application that comes with 
> the TI Linux Dsp Tools. The base application implements an 
> FIR filter and a volume control. The executable code that 
> implements the XDAIS FIR filter algorithm comes in library 
> files located in the rf_3_11_dsp/lib directory and appears to 
> have already been built, i.e. the executable XDAIS FIR 
> algorithm code is not built when the dsp side RF6 application 
> is built, rather, it appears to have been built with code 
> composer studio using the project file in 
> rf_3_11_dsp/src/fir_ti/. Is it possible to build the dsp-side 
> XDAIS algorithm executables using only the Linux DSP Tools or 
> the montavista tools, without CCS?
> 
> Thank you,
> Carlos
> 


This should be possible. However, you will need to create a Makefile for
the FIR filter project. The *.pjt file that CCS uses is a text file and
so you can view this with any text editor. In the *.pjt file you will
see a list of the source files included in the project, plus the
compiler and linker options used for building the project and creating
the *.out file. 

Regards,
Jon
 

Re: building XDAIS algorithms

[Carlos Davila]

Hunter, Jon wrote:

>> Is it possible to build the dsp-side 
>>XDAIS algorithm executables using only the Linux DSP Tools or 
>>the montavista tools, without CCS?
>>
>>Thank you,
>>Carlos
>>
>>    
>>
>
>
>This should be possible. However, you will need to create a Makefile for
>the FIR filter project. The *.pjt file that CCS uses is a text file and
>so you can view this with any text editor. In the *.pjt file you will
>see a list of the source files included in the project, plus the
>compiler and linker options used for building the project and creating
>the *.out file. 
>
>  
>
Thanks for your response Jon. The .pjt file also has settings for an 
"Archiver" and a "DspBiosBuilder". I assume the DspBiosBuilder is not 
needed since DspBios is already incorporated into RF6, but the archiver 
appears to be what generates the for_ti.l55l library file used by RF6. 
Can this also be done by gcc?

Carlos
 

RE: building XDAIS algorithms

[Hunter, Jon]

Hi Carlos

> Thanks for your response Jon. The .pjt file also has settings 
> for an "Archiver" and a "DspBiosBuilder". I assume the 
> DspBiosBuilder is not needed since DspBios is already 
> incorporated into RF6, but the archiver appears to be what 
> generates the for_ti.l55l library file used by RF6. 
> Can this also be done by gcc?


Yes I believe this can be done via gcc. The archiver is included with
the linux c55x dsp tools. The archiver is located in the
cgtools-c5500-v2.56/bin/ directory and it is the tool called ar55. 

After you have compiled the source files and generated the *.obj files
you can create a library by doing something like:

ar55 -r [libname] [obj file names]

Eg. ar55 -r fir_ti.l55l fir_ti.o55 fir_ti_filter.o55 fir_ti_ialg.o55
fir_ti_vt.o55

Regards,
Jon

Re: building XDAIS algorithms

[Carlos Davila]

Hunter, Jon wrote:

>Yes I believe this can be done via gcc. The archiver is included with
>the linux c55x dsp tools. The archiver is located in the
>cgtools-c5500-v2.56/bin/ directory and it is the tool called ar55. 
>
>
>  
>
Jon...that's a big help. The c55 compiler is also in that same directory 
and accepts the options found in the .pjt file.
Thanks,
Carlos