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.

V4l2 examples problem on DM8168 demoboard

Other Parts Discussed in Thread: TVP7002

Hello

we try to run the captures v4l2 demos of the ezsdk 5.04.00.11 (saLoopBack). We have installed the sdk, recompiled and started with the default setup and run omx examples. Than we cread a new rc5 directory in etc and deleted load-hd-firmware.sh and matrix-gui-e. We reboot the system and lanched the load-hd-v4l2-firmware.sh

root@dm816x-evm:/usr/share/ti/ti-media-controller-utils# ls
change_resolution.sh      dm816x_hdvpss.xem3        load-hd-v4l2-firmware.sh
dm816x_c6xdsp.xe674       dm816x_hdvpss_v4l2.xem3
dm816x_hdvicp.xem3        load-hd-firmware.sh

We see this error

root@dm816x-evm:/usr/share/ti/ti-media-controller-utils# ./load-hd-v4l2-firmware.sh start
Loading HDVICP2 Firmware
DM816X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
        PRCM for IVHD0 is in Progress, Please wait.....
                        BW Phy Addr : 0x48180600 Data : 0x00000002
                        AW Phy Addr : 0x48180600 Data : 0x00000002
                        Phy Addr : 0x48180c04 Data : 0x00000037
                        BW Phy Addr : 0x48180620 Data : 0x00070000
                        AW Phy Addr : 0x48180620 Data : 0x00070002
                        BW Phy Addr : 0x48180624 Data : 0x00030000
                        AW Phy Addr : 0x48180624 Data : 0x00010002
                        Phy Addr : 0x48180600 Data : 0x00000102
                        BW Phy Addr : 0x48180c10 Data : 0x00000007
                        AW Phy Addr : 0x48180c10 Data : 0x00000003
                        Phy Addr : 0x48180c14 Data : 0x00000004
                        BW Phy Addr : 0x58088000 Data : 0xeafffffe
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe
                        BW Phy Addr : 0x58098000 Data : 0xeafffffe
                        AW Phy Addr : 0x58098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180c10 Data : 0x00000003
                        AW Phy Addr : 0x48180c10 Data : 0x00000000
                        Phy Addr : 0x48180c14 Data : 0x00000007
        PRCM for IVHD0 is Done Successfully
        PRCM for IVHD1 is in Progress, Please wait.....
                        BW Phy Addr : 0x48180700 Data : 0x00000002
                        AW Phy Addr : 0x48180700 Data : 0x00000002
                        Phy Addr : 0x48180d04 Data : 0x00000037
                        BW Phy Addr : 0x48180720 Data : 0x00070000
                        AW Phy Addr : 0x48180720 Data : 0x00050002
                        BW Phy Addr : 0x48180724 Data : 0x00030000
                        AW Phy Addr : 0x48180724 Data : 0x00010002
                        Phy Addr : 0x48180700 Data : 0x00000102
                        BW Phy Addr : 0x48180d10 Data : 0x00000007
                        AW Phy Addr : 0x48180d10 Data : 0x00000003
                        Phy Addr : 0x48180d14 Data : 0x00000004
                        BW Phy Addr : 0x5a088000 Data : 0xeafffffe
                        AW Phy Addr : 0x5a088000 Data : 0xeafffffe
                        BW Phy Addr : 0x5a098000 Data : 0xeafffffe
                        AW Phy Addr : 0x5a098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180d10 Data : 0x00000003
                        AW Phy Addr : 0x48180d10 Data : 0x00000000
                        Phy Addr : 0x48180d14 Data : 0x00000007
        PRCM for IVHD1 is Done Successfully
        PRCM for IVHD2 is in Progress, Please wait.....
                        BW Phy Addr : 0x48180800 Data : 0x00000002
                        AW Phy Addr : 0x48180800 Data : 0x00000002
                        Phy Addr : 0x48180e04 Data : 0x00000037
                        BW Phy Addr : 0x48180820 Data : 0x00070000
                        AW Phy Addr : 0x48180820 Data : 0x00050002
                        BW Phy Addr : 0x48180824 Data : 0x00030000
                        AW Phy Addr : 0x48180824 Data : 0x00010002
                        Phy Addr : 0x48180800 Data : 0x00000102
                        BW Phy Addr : 0x48180e10 Data : 0x00000007
                        AW Phy Addr : 0x48180e10 Data : 0x00000003
                        Phy Addr : 0x48180e14 Data : 0x00000004
                        BW Phy Addr : 0x53088000 Data : 0xeafffffe
                        AW Phy Addr : 0x53088000 Data : 0xeafffffe
                        BW Phy Addr : 0x53098000 Data : 0xeafffffe
                        AW Phy Addr : 0x53098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180e10 Data : 0x00000003
                        AW Phy Addr : 0x48180e10 Data : 0x00000000
                        Phy Addr : 0x48180e14 Data : 0x00000007
        PRCM for IVHD2 is Done Successfully
PRCM Initialization completed
SysLink version : 2.10.03.20
SysLink module created on Date:May 25 2012 Time:01:21:50
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop>           to start/stop the firmware
===Optional arguments===
-mmap                  input memory map bin file name
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 1 start Successful
Loading HDVPSS (V4L2) Firmware
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop>           to start/stop the firmware
===Optional arguments===
-mmap                  input memory map bin file name
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 2 start Successful
tvp7002 2-005d: tvp7002 found @ 0x5d (OMAP I2C adapter)
tvp7002 2-005d: Rev. 00 detected.
tvp7002 2-005d: Unknown revision detected.
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 0
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 1
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 2
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 3
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 0
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 1
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 0
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 0
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 1
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 2
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 3
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 0
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 1
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 2
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 3
omap_i2c omap_i2c.2: controller timed out
tvp7002 2-005d: Write: retry ... 4
tvp7002 2-005d: TVP7002 write error -110
tvp7002: probe of 2-005d failed with error -110
ti81xxvin ti81xxvin: Error registering v4l2 subdevice
HDMI W1 rev 2.0

Thanks for the help.



  • I have the exactly same problem. Any help please?

  • They added parameters to the binary load.
    Modify the lines in the scrips as shown below  , note the addition of the -i2c parameter

          firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm816x_hdvicp.xem3 start -i2c 0
          echo "Loading HDVPSS (V4L2) Firmware "
          firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm816x_hdvpss_v4l2.xem3 start -i2c 0