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.

Remove HDVICP2 in kernel



Hi,

We use C6A8168 CPU now.

We make boards with C6A8168.

Not DM8168.

I know that DM816x is pin compatible with C6A816x.

But I have a problem.

HDVICP2 is loading when U-boot file call kernel image.

DM816x hasn't errors because it has HDVICP2.

But C6A816x hasn't HDVICP2, so it has errors.

How can I solve this problem.

Please answer my question.

  • Provide a boot log and someone might be able to help you.

  • Hi Sangyun,

    The HDVICP2 firmware auto load at init (boot) time can be removed from the <file system>/etc/init.d/load-hd-firmware.sh file. You have to comment this line:

    # firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm816x_hdvicp.xem3 start

    Best Regards,

    Pavel

  • Thanks!

    I solved this problem.

    Thank you for your answer.

  • Hi Pavel,

    I removed the HDVICP2 firmware auto load form the load-hd-firmware.sh file, but it seemed the HDVPSS firmware cannot work stably after it, the grpx cannot output via VOUT0 (DVO2 compositor) sometime. How to deal with it?

    BTW. I'm using DM8168.

    Best Regards,

    Jed ZHU

  • Hi Jed,

    Sangyun removed the HDVICP2 firmware as he was on C6A8168 device, which does not have HDVICP2 hardware. As you are on DM816x (which has HDVICP2 hardware), what is the reason for you to remove the HDVICP2 firmware?

    Best Regards,

    Pavel

  • Hi Pavel,

    Sorry for late reply.

    Currently HDVICP2 is unnecessary for us and it takes about 3 seconds to load HDVICP2 firmware when startup, so we want to remove the HDVICP2 firmware loading to speedup the startup time.

    Best Regards,

    Jed ZHU

  • Hi Jed,

    This is not so easy. The HDVPSS-M3 binary by default does IPC_attach with HDVICP2-M3. So it mandates HDVICP2-M3 also to be loaded.

    You will have to modify HDVPSS-M3 to remove this & modify load-hd-firmware.sh in order not to load HDVICP2-M3.

    The other option is to look at the HDVPSS-M3 standalone firmware, present in HDVPSS driver component if you are not using any of the OMX components.

    More info here: http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/t/186702.aspx

    Best Regards,

    Pavel

  • Hi Pavel,

    Thanks.

    But how to modify the HDVPSS-M3 to remove IPC_attach with HDVICP2-M3 and not to load HDVICP2-M3?

    And where could I find out HDVPSS-M3 standalone firmware?

     

    Best Regards,

    Jed

  • Hi Jed,

    Are you using EZSDK or DVRRDK? AFAIK the M3 source code is available only in DVRRDK (to which I have no access, I am working only with EZSDK). If you need to switch to DVRRDK, you should contact your local FAE.

    BR,

    Pavel

  • Hi Pavel,

    I'm using EZSDK.

    Did TI release HDVPSS-M3 standalone firmware (dm816xbm_m3vpss.xem3 binary), or put it into next EZSDK release?

     

    Best Regards,

    Jed

  • Hi Jed,

    Yes, TI release HDVPSS-M3 firmware in EZSDK release, but only as a binary (black box), no source code in EZSDK. I think there will be new version of the HDVPSS-M3 firmware in the next EZSDK.

    BR,

    Pavel

  • Hi Pavel,

    I'm sorry but the HDVPSS-M3 standalone firmware I mentioned means it is HDVICP2-M3 independent, which hasn't IPC_attach with HDVICP2-M3.

    Would TI release such a HDVPSS-M3 firmware it in the next EZSDK?

     

    BR,

    Jed

  • Hi Pavel,

    Now I got DRRRDK. But does VPSS-M3 firmware source code is same for both DVRRDK and EZSDK? or DVRRDK and EZSDK use different VPSS-M3firmware?

    Thanks and Best Regards,

    Jed

  • Hi Jed,

    As I have access only to EZSDK (respectively support only EZSDK), I contacted the DVRRDK experts. Here is the feedback from them:

    VPSS-M3 firmware of DVRRDK and EZSDK are different. Even if you move to DVR RDK, modifications are required in VPSS side firmware to remove VID-M3 firmware.  Mainly we need to cut the IPC_attach with VID-M3.  But this can be done without much effort.
    BTW, our RDK is primarily targeted/ used for video surveillance & conference applications, so it would be better if you help me to know more about your application/product spec to guide you better before the migration.

    They also wants to know which version of the DVRRDK you are using, is it GA 03.00.01.xx ? Also want to know what is the customer application and who is the customer. If you do not want to expose this kind of information in a public forum, you can write me directly on p-botev@ti.com.

    Regards,
    Pavel
  • Hi Pavel,

    Sorry for late reply due to vacation.

    Now I'm studying DVRRDK_03.00.01.03, but we don't want to move to DVRRDK, we just want to modify VPSS-M3 of EZSDK to remove the IPC_attach with VICP-M3.

    As it is different in EZSDK and DVRRDK, could TI provide VPSS-M3 source code/build envionment of EZSDK? or release a VPSS-M3 firmware w/o IPC_attach with VICP-M3 in next version EZSDK?

    Thanks and Best Regards,

    Jed