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.

VPSS_FVID2: M3 firmware version 0x1000145 is newer,driver may not work properly.

I'm getting this error with the new 5_05_02_00 EZSDK. Is this typical? I'm using the new filesystem that TI provides in this SDK, e.g., the new xem3 files...here's what they look like

ubuntu@ubuntu-VirtualBox:~/targetfs/usr/share/ti/ti-media-controller-utils$ ll *x*
-rw-rw-r-- 1 ubuntu ubuntu 19075600 2013-04-11 15:06 dm816x_c6xdsp.xe674
-rw-r--r-- 1 ubuntu ubuntu 16706714 2013-04-11 15:06 dm816x_hdvicp.xem3
-rw-r--r-- 1 ubuntu ubuntu 20614230 2013-04-11 15:06 dm816x_hdvpss_v4l2.xem3
-rw-r--r-- 1 ubuntu ubuntu 20614230 2013-04-11 15:06 dm816x_hdvpss.xem3

same sizes as the ones in the SDK

  • Hi Rich,

    I have tested the new EZSDK 5.05.02.00 and the hdvpss firmware works fine with the vpss driver, there is no version misalignment. Could you please provide me a full log?

    BR

    Pavel

  • Pavel,

    Maybe this is a dumb question, but how do I provide a full log? You looking for stdout when I load the driver, dmesg, build log?

  • Hi Rich,

    I made more detailed look on my own console output, and I confirm there is a version misalignment between the vpss.ko module and the VPSS M3 firmware dm816x_hdvpss.xem3. It looks like that VPSS M3 firmware version is 0x01000145 while the VPSS FVID2 is defined to work with 0x01000137, see file
    ti-ezsdk_dm816x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01/drivers/video/ti81xx/vpss/fvid2.c

    /*define the information used by the proxy running in M3*/
    #define VPS_FVID2_RESERVED_NOTIFY    0x09
    #define VPS_FVID2_M3_INIT_VALUE      (0xAAAAAAAA)
    #define VPS_FVID2_PS_LINEID          0
    #define CURRENT_VPS_FIRMWARE_VERSION        (0x01000137)

    There are two patches available in the arago linux tree, first change the version to 0x01000139, second from 0x01000139 to 0x01000144 :

    http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=eb19c1d0b1fcace6e76a0e4bf78f2e3987f27275

    http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=2afe23da7ee5c0e061bf0c4df55e7ec189ddf380

    But we still have not update to 0x01000145. I think this warning can be ignored, as the vpss.ko is finally loaded successfully and is working fine. I will report this to the PSP team and come back to you if any further action is required regarding this issue.

    Thanks for reporting this.

    BR

    Pavel

  • Hi Rich,

    I made a consultation within TI, and the best option if there is a problem due to version mismatch is to use older version of HDVPSS to match the versions. If there is no problem, the best option is to use current version of HDVPSS.

    Best regards,

    Pavel