• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 463 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

No API References for CCS, could anyone send me API Guide? Thanks a lot !!!!!!

Kang Yang
Prodigy 100 points

Hello, everyone! I recently study the implementation for very large FFT of  signals  in Multicore DSP and read the program that was distributed by the Texas Instruments. In the program, I ran into some problems of understanding the basic APIs that was used for the algorithms, for example, 

void transpose_2Cols_rowsX8_cplxMatrix_sa ( float *pIn, float *pOut, Uint32 rows );

 void DSPF_sp_radix4_fftSPxSP( Uint32 n, float *pIn, float *pTwiddle, float *pOut, Uint32 log4NMinus1 );   

void transpose_2Rows_8XCols_cplxMatrix_sa ( float *pIn, float *pOut, Uint32 cols );

........

There are many such that APIs that I don't know what the arguments in it stand for, and the result of it means. Could anyone show me how to look up these APIs, or maybe there is API guide of the DSP for CCv5? Please tell me where to find the references guide of these APIs?  Thank you very much!!!!

  • 0
    TI__Guru**** 450031 points

    Hello,

    I'm not too familiar with those APIs... they are probably from some CSP library for your device. You may want to check the forum for your device for more advice.

    Note that there are many different software packages and libraries out there that you can use with your application when building with CCS. BSPs (Board Support Packages), CSPs (Chip Support Packages), target software packages (BIOS, NDK, StarterWare, etc), and so on. All of these come from various groups in TI and not from the CCS team. There is no comprehensive list of APIs in one place for all of these. You will need find out where the packages you are using come from and ping the respective groups (most of these packages ship the API doc with them)

    Thanks

    ki