TDA4VM: Running camera application multiple times on the same boot cycle

Jegathesan Shanmugam

Part Number: TDA4VM

Hi All,

We have created a camera application with reference of single_cam for our custom board. When we run a camera application for the first time the application exit gracefully. But, When we run the same application for the second time, it hangs at vxWaitGraph and dequeue is not happening(vxGraphParameterDequeueDoneRef). Is it expected behavior?

And, We could see there is no resource cleanup or Deint for IM_SENSOR_CMD_STREAM_OFF and IM_SENSOR_CMD_PWROFF. Where the camera handlers and other resources will be cleared when the application exit?

Regards,

Jegathesan S

over 5 years ago

0 Brijesh Jadav over 5 years ago

TI__Guru**** 491115 points

Hi,

But in this case, is your camera outputting data in the second iteration? this looks like camera is not outputting data. Can you please check it?

Rgds,

Brijesh

0 Jegathesan Shanmugam over 5 years ago in reply to Brijesh Jadav

Intellectual 270 points

Hi Brijesh,

Yes, I can check that. When we call the iss driver for second time it hitting below condition,

if(NULL != g_pSenHndl[chId]) {

printf("ISS_SENSOR - %s - Warning : channel ID %d already has a registered sensor handle \n", __func__, chId);

}

Means the handler register for previous cycle not cleared. And, We could see no implementation/Cleanup code for IM_SENSOR_CMD_STREAM_OFF and IM_SENSOR_CMD_PWROFF switch case statments.

Regards,

Jegathesan S

0 Brijesh Jadav over 5 years ago in reply to Jegathesan Shanmugam

TI__Guru**** 491115 points

Hi Jegathesan,

I see this handle is set to null in IssSensor_Stop API, which is called from STREAM_OFF. Can you please check if you are calling STREAM_OFF?

Rgds,

Brijesh

0 Jegathesan Shanmugam over 5 years ago in reply to Brijesh Jadav

Intellectual 270 points

Hello Brijesh,

IssSensor_Stop function call not being called. But, I tried calling IssSensor_Stop from IM_SENSOR_CMD_STREAM_OFF switch case and that hangs on that function.

FYI. Code snippet from Feb release.

case IM_SENSOR_CMD_STREAM_OFF:

appLogPrintf("ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_STREAM_OFF \n");

status = 0;

break;

case IM_SENSOR_CMD_PWROFF:

status = 0;

break;

case IM_SENSOR_CMD_CTL:

status = IssSensor_Control(NULL, 0, (void*)cmd_param, NULL);

break;

default:

appLogPrintf("ImageSensor_RemoteServiceHandler : Unsupported command : %d\n", cmd);

status = -1;

Regards,

Jegathesan S

0 Brijesh Jadav over 5 years ago in reply to Jegathesan Shanmugam

TI__Guru**** 491115 points

Hi Jegathesan,

ok, but i doubt this is reason for not able to restart. Can you please first check if capture is working fine?

Rgds,

Brijesh

0 Jegathesan Shanmugam over 5 years ago in reply to Brijesh Jadav

Intellectual 270 points

Hi Brijesh,

I checked all the status, and control registers of serializer, and deserializer for the first and second boot, and the values are the same. How can we check the capture at CSI2RX level or suggest to me how can we validate this?

Regards,

Jegathesan S

0 Brijesh Jadav over 5 years ago in reply to Jegathesan Shanmugam

TI__Guru**** 491115 points

Hi Jegathesan,

If you have CCS access, Can you try putting breakpoint on API captDrvCallback on MCU2_1. This is capture callback that driver gives to capture node when one capture frame is available..

Rgds,

Brijesh

Processors

Processors forum

TDA4VM: Running camera application multiple times on the same boot cycle