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.

VLIB on DM8168

Hello,

I have downloaded the new VLIB from the following link;

http://software-dl.ti.com/libs/vlib/latest/index_FDS.html

I want to use the VLIB together with TI DM8168 EZSDK in Linux. For this purpose I have added the necessary include files such as vlib.h, c6x.h. But, now I got many errors including "integer constant is too large for "unsigned long" type.

Can you please describe the steps for building the VLIB in Linux with GNU make? I checked the documentation, but the "building" link is broken in the html document. What should I do to use VLIB on DM8168? Do I need to use dsp-devkit instead of linux-devkit? Please provide the building steps and a simple image processing example if possible.

Thanks&Best Regards,

Fikret 

  • Fikret,

    I have moved this post over to the device forum in hopes that it will get a faster response there.

  • Hi,

    you should be able to link linux build vlib library as it is in any DSP linux image. 

    we need more details about problem faced by you, like where where compilation error is coming, like you can send code snippet etc.

    Regards

    Deepak Poddar

  • Hi Deepak,

    Actually, I am in the first step. I want to learn how compile and link the DSP library to the ARM code. As I said, the building link is broken inside the documentation of VLIB. Do I need to use SYS/BIOS, or Codec Engine? Can you please provide an example or related documents?

    It would be very good if there is an example that takes an image or video file as input, makes some video processing with VLIB and outputs the processed image or video frame. This would be really helpful.

    Thanks&Best Regards,

    Fikret

  • The building link is in fact broken.  Since VLIB is delivered as a low level library (not source), you would need to link this in your DSP image that you are using.  The integration page is what you need to refer to at the following location:

    file:///C:/ti/vlib_c66x_3_0_0_7/docs/doxygen/html/integrate.html

    I am not familiar with the framework you are using to call from ARM.  You would need to first link VLIB in your DSP image, and add VLIB function calls on the DSP side.  VLIB does not depend on XDC, codec engine, or SYS/BIOS.  It's only dependency is the DSP compiler (7.4.2 is what was used to compile the library).   It is a low level library that requires an integrator to call it from a higher level framework, perhaps using codec engine, which then will take care of things like memory buffer allocation, inter-processor communication, and cache maintenance.  None of these things are done from within VLIB.


    Jesse

  • The other file you can directly look at is:

    file:///C:/ti/vlib_c66x_3_0_0_7/docs/doxygen/html/ccs_compile_knl.html

    This shows how to build the CCS project files that let you test the individual kernels.

    Jesse

  • Hi,

    Just highlighting basic facts. VLIB is released for DSP, and its executable will run on DSP present in the SOC. TO make use of this VLIB, you have to pass frame information to from A9/A8 to dsp, and there it will be processed there on DSP with VLIB functions imlementation, and then result information will require to pass to A8/A9.

    Regards

    Deepak Poddar