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.

Rebuilding The hdvpss and hdvicp m3 executables from source in EZSDK 5.02

Expert 2220 points

Hello,

 

I have been provided the HDVPSS 1.0.1.28 source under NDA and can rebuild the examples. However, it would appear that none of the executables generated are the media controller executables provided in the target filesystem located at ~targetFS/usr/share/ti/ti-media-controller-utils. I would need to rebuild these executables because i have to modify them slightly because of an unsupported input. Is there a patch or a set of instructions that is available for me to use?

many thanks

  • Hello,

        EZSDK does not come with source code for media controller, you need to get additional source code add on installer for media controller. Please contact your sales/field application engineer to get the source code. This is available for the customers who have signed NDA with TI.

    regards,

    Venkat

  • I have the source code provided under NDA from TI. My question above is: when I build the m3 source files, the m3 executables generated are not the same as the media controller executables found in the SDK (the SDK expecutable is 15MB and the generated file is 10MB max) how are the m3 files included with the EZSDK generated from the sourc supplied under NDA? Thanks
  • That is right, SDK team adds its own M3 OMX SW in the top of M3 HDVPSS + different memory map. Please check with your local Sale or FAE to get the SDK NDA M3 source codes.

    Regards,

    yihe

  • I obtained an NDA and requested the EZSDK HDVPSS source from my FAE, but he was unable to get it: "TI DaVinci team has changed a lot, and they told me the drivers they provided is “as is”.", and told me to ask here.

    Is this EZSDK HDVPSS source available anywhere? If not, I have the DVR RDK package which has HDVPSS source, but it's configured differently. How can I  convert it to match the EZSDK configuration?