This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Using DSPLIB on local or remote side of OMAP3530

Other Parts Discussed in Thread: OMAP3530

Hello,

 

I have the following setup:

Linux Build environment (no CCS)

OMAP3530

Using the latest DVSDK 3_01

Test Codec is based on the IUNIVERSAL FIR Filter Example

 

I'd like to leverage the DSPLIB and the C Intrinsics to build codec references for the ARM, and gradually migrate the reference to the DSP side.   Thus, I want to be able to build the same code (leveraging DSPLIB) with a local or remote target. 

 

1.  Any advice on the best way to approach this would be most appreciated.

 

2.  I looked at this http://processors.wiki.ti.com/index.php/Run_Intrinsics_Code_Anywhere, and read the presentation.  I've tried linking in a single DSPLIB function, and included the two intrinsic header files.  Everything is fine until the last link stage, when the compiler complains about the _nassert #define that is in C6xSimulatorTypes.h.  I'm using -DSIMULATION, but it's not picking up the #defines when I build the app. The remote side builds fine.

 

3.  Should I try creating each DSPLIB as it's own codec?The compiler also didn't like the relative addressing in dsplib64plus.h

 

4.  Is there a workaround for the left hand addressing of the _amem8d intrinsic?

 

Thanks for any insight,

 

Jim