• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 512 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DSPLIB Native Compilation on K2H Platform

Ankit Patel49
Prodigy 70 points

I have a K2H evaluation module and I'm trying to get some code running that tests the performance of the DSP libraries. I'm sure it is possible to compile code on the EVM, but I just have no idea where to start. I was hoping I could get some pointers. What I've done so far is build off the MCSDK HPC example code. But, I'm having issues with the includes for dsplib.h. What would I have to add to the makefile to get the includes to work?

EDIT: I should say that I know that native compilation is possible. I just don't know how to write a suitable make file. Using includes in my main file gives unsupported target errors. I've been trying to use the dsplib.ae66 file or dsplib.lib files and had no luck with those either.

  • 0
    TI__Mastermind 35645 points

    Hi,

    Thanks for your post.

    To my knowledge, DSP library native compilation on K2H is possible but you need to explore the source of DSP libaray and appropriately change the modifications on the make file to build the new static dsplibrary. But in my opinion, this is very complex to change the make file through appropriately setting the build source path and other dependancy packages of DSP libraries as well setting the paths in environment variable which would probably lead you to more conflicts to successfully build the DSP library source through make file process.

    I believe, you need to evaluate the performance of DSP library through benchmark test results. If my understanding is correct, you could check the latest DSPLIB 3.4.0.0 C66x test results and the cycle count formula are contained in the test report "DSPLib_c66x_TestReport.html" which is located on the DSPLIB download page as below:

    http://software-dl.ti.com/sdoemb/sdoemb_public_sw/dsplib/latest/index_FDS.html

    http://software-dl.ti.com/sdoemb/sdoemb_public_sw/dsplib/latest//exports/DSPLIB_C66x_TestReport.html

    Also. to know more on software routines included on DSP library, you could see the docs folder after you install the above DSP library package from the below path:

    ~\ti\KeystoneII_MCSDK_03_01\dsplib_c66x_3_2_0_1\docs\DSPLIB_Users_Manual.html

    You can check the DSP module API references from the below path after you install the DSP libarary package:

    ~\ti\KeystoneII_MCSDK_03_01\dsplib_c66x_3_2_0_1\docs\doxygen\html\dsplib_html\modules.html

    To know DSP library build process either through CCS build or GNU make build process, you could refer the below doc. path on the DSP lib. installation:

    ~:\ti\KeystoneII_MCSDK_03_01\dsplib_c66x_3_2_0_1\docs\doxygen\html\building.html

    Thanks & regards,

    Sivaraj K

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    -------------------------------------------------------------------------------------------------------

  • 0 in reply to Sivaraj Kuppuraj
    Prodigy 70 points

    Thank you for your answer Sivaraj. I understand that compiling the libraries will be very difficult, but I was referring to using the libraries in my own code and compiling it on the EVM. Would this require me to recompile the libraries (different from the library files that are built when installing MCSDK)? If so, I will explore other avenues for testing the EVM.

    There are a few examples in the MCSDK HPC package that use the libraries, but those programs and their makefiles are very complex. I'm new to this, so I was hoping for a more simple way to include the libraries. If there is no simple way, I understand that I will just have to learn how to write makefiles.

  • 0 in reply to Ankit Patel49
    TI__Mastermind 35645 points

    Hi,

    Thanks for your update.

    To know DSP library build process either through CCS build or GNU make build process, you could refer the below doc. path on the DSP lib. installation:

    ~:\ti\KeystoneII_MCSDK_03_01\dsplib_c66x_3_2_0_1\docs\doxygen\html\building.html

    Thanks & regards,

    Sivaraj K

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    -------------------------------------------------------------------------------------------------------