TDA4VM: Camera: Keep dropping frames

dongwang

Part Number: TDA4VM
Other Parts Discussed in Thread: DS90UB953-Q1,

Hi Ti

We want to use a camera on TDA4 EVM. The sdk version is 850. The serializer is DS90UB953-Q1.

The following table describes camera parameters

Sensor	AR0220AT
Resolution	1828×948
Output Format	RAW 12bit

After completing the register configuration, we encountered the problem shown in the following figure when we run "run_app_multi_cam.sh". Only The Frame Drop Count is increase.

In order to find the problem, we have made the following attempts:

1.We read registers of ub960,include LINE_COUNT_1 Register (Address 0x73),LINE_COUNT_0 Register (Address 0x74),LINE_LEN_1 Register (Address 0x75),LINE_LEN_0 Register (Address 0x76),and their values are 0x03, 0xb4, 0x0a, 0xb6.

2.The value of CSI-Clock is CSIRX_LANE_BAND_SPEED_1350_TO_1500_MBPS. And we throught read TDA4VM's DPHY_RX_VBUS2APB_PCS_TX_DIG_TBIT0 Register,the data rate matches set value.

The printing information when the program is running is shown in the following figure

In the funcion of app_run_graph_for_one_frame_pipeline, vxGraphParameterDequeueDoneRef is blocked. We want to know how to solve this problem.

over 2 years ago

+1 Brijesh Jadav over 2 years ago

TI__Guru**** 477005 points

Hi,

The frame Drop Count essentially means that capture is working fine, but some other component in the pipeline is stuck and because of that, the entire graph is getting stuck. Are you using VISS in the pipeline? Have you changed anything in the VISS settings for your sensor? Can you please read register at the offset 0x0F008000 and share the value?

Regards,

Brijesh

0 dongwang over 2 years ago in reply to Brijesh Jadav

Prodigy 10 points

HI,

We used VISS in the pipeline.The VISS settings is copied from the ar0233 VISS configuration.We haven't changed the VISS settings.The value of the register at the offset 0x0F008000 is 0x00000001.

The function settings of appIssGetDCCSizeVISS as the follows:

int32_t appIssGetDCCSizeVISS(char * sensor_name, uint32_t wdr_mode)
{
    int32_t size = -1;
    switch(wdr_mode)
    {
        case 0:
            /*Linear mode*/
            #ifdef VPAC3L
            if(0 == strcmp(sensor_name, SENSOR_OV2312_UB953_LI))
                size = DCC_VISS_OV2312_DCC_CFG_NUM_ELEM;
            else
            #endif
            if(0 == strcmp(sensor_name, SENSOR_SONY_IMX390_UB953_D3))
                size = DCC_VISS_IMX390_DCC_CFG_NUM_ELEM;
            else if (0 == strcmp(sensor_name, SENSOR_ONSEMI_AR0233_UB953_MARS))
                size = DCC_VISS_AR0233_DCC_CFG_NUM_ELEM;
            else if (0 == strcmp(sensor_name, SENSOR_ONSEMI_AR0820_UB953_LI))
                size = DCC_VISS_AR0820_DCC_CFG_NUM_ELEM;
            else if (0 == strcmp(sensor_name, UB9XX_RAW_TESTPAT))
                size = DCC_VISS_UB9XX_RAW_TEST_PATTERN_DCC_CFG_NUM_ELEM;
            else if (0 == strcmp(sensor_name, SENSOR_ONSEMI_AR0220_UB953_MARS))
                size = DCC_VISS_AR0233_DCC_CFG_NUM_ELEM;
            else
                size = -1;
            break;
        case 1:
            /*WDR mode*/
            if(0 == strcmp(sensor_name, SENSOR_SONY_IMX390_UB953_D3))
                size = DCC_VISS_IMX390_WDR_DCC_CFG_NUM_ELEM;
            else if (0 == strcmp(sensor_name, SENSOR_ONSEMI_AR0233_UB953_MARS))
                size = DCC_VISS_AR0233_WDR_DCC_CFG_NUM_ELEM;
            else if (0 == strcmp(sensor_name, SENSOR_ONSEMI_AR0820_UB953_LI))
                size = DCC_VISS_AR0820_WDR_DCC_CFG_NUM_ELEM;
            else if (0 == strcmp(sensor_name, SENSOR_ONSEMI_AR0220_UB953_MARS))
                size = DCC_VISS_AR0233_WDR_DCC_CFG_NUM_ELEM;
            else
                size = -1;
            break;
        default:
            /*Unsupported mode*/
            size = -1;
    }
    return size;
}

0 dongwang over 2 years ago in reply to Brijesh Jadav

Prodigy 10 points

Hi，

We haven't solved the issue yet.The resolved option was clicked by mistake.

0 Brijesh Jadav over 2 years ago in reply to dongwang

TI__Guru**** 477005 points

Hi,

Sure, i have opened this thread. Lets continue out discussion here.

From the register value, it is clear that VISS is getting stuck and because of which, Capture is dropping all frames.. What's the resolution of the newly added sensor? Is it matching with the resolution of the AR0233? Since you are using DCC file of this sensor, so resolution should match with this sensor. If not, please the DCC file for the new sensor resolution.

Regards,

Brijesh

0 dongwang over 2 years ago in reply to Brijesh Jadav

Prodigy 10 points

Thank you for your reply! We solved this problem by regenerating the DCC file for the new sensor resolution.

Processors

Processors forum

TDA4VM: Camera: Keep dropping frames