• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 302 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.

[OMAP3530] Codec Engine : Errors while building .x64P on DSP server using only .l64P (Codec Package excludes source files)

M BHARATH
Intellectual 270 points
Other Parts Discussed in Thread: OMAP3530

Hi,

          I am using OMAP3530 board. I trying to integrate my own codec into so that i can create .l64P and .x64P. I am having my souce files and heder files for my codec.

1) What is the procedure to generate the .l64P and .x64P?

2) Can i use the .l64P generated in CCS for building .x64P in server side. (I have made the DSP code XDM complaint.) How to do it? I am building the servers by keeping my .l64P file in codecs. Is this the right way? What i noticed while checking viddec_copy example is " I am building .l64P using viddec_copy.c  and i am then  i am  building servers, it is working fine.  In my case if i have only the .l64P of viddec_copy what should i do. i tried to remove the c file from codecs and take only .l64P, xdc, xs files and build servers i am getting errors. The packages which were built while building codecs are needed or not? if i build the codecs with c files so that i get the packages and then i remove th c files(viddec_copy) it is working.    I want to know how can i do it if have a DSP library from CCS without any packages???

3) Is this the case that i have to take all my DSP side c files and header files to codecs folder and build with XDC tools so that i get my .l64P and packages. (Dont say me this is the right way...)

4) After these libraries are built, does the Application (which resides on ARM) require the packages with DSP source files?? If the package includes DSP header files, to my knowledge, it should work fine.No source files to be included. Please confirm.

Please help me sort out these.....

Thanks and Regards,

Bharath.M

  • 0
    TI__Genius 17205 points

    This article describes the responsibilities and tools available when playing the different 'roles' in a Codec Engine based system:

    http://tiexpressdsp.com/index.php?title=Codec_Engine_Roles

    To handle your direct questions, you'll be playing the "Algorithm Creator" and "Server Integrator".

    In your case, since you already have a .l64P library, you can probably use the Codec Packaging Wizard (link on the article above) to take your .l64P and turn it into a Codec Package.  From there, you switch to a Server Integrator and can use the Codec Server Wizard (link also in the article) to integrate your codec package into a Server.

    Finally, once you have your Server, you can configure your ARM-side app (Engine Integrator) and use the CE/VISA APIs in your application (Application Author) - those last 2 roles are also described at the article above.

    Chris