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.

How to support send error frame for YUV format?

I want to use the error frame function to report error frames when one of the multiple sensors does not come up with a new frame。I find this url:https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1136265/tda4vm-how-do-i-keep-graph-running-when-i-unplug-the-camera-for-one-or-more-channels/4216672?tisearch=e2e-sitesearch&keymatch=tivxCaptureRegisterErrorFrame#4216672

I try this solution in vx_app_multi_cam.out,I find captureObj.enable_error_detection param can not set 1。 Because my camera is YUV format frame, capture module only support raw format to enable error detection (see app_capture_module.c, function create_error_detection_frame()). How can i support enable error detection  for YUV format?

  • Hi Wang,

    Looking at the code, i dont see reason why this can't be supported. Can you please try providing error frame in yuv format and see if it works fine?

    Regards,

    Brijesh 

  • Hi, thanks for your reply.! I use "ti-processor-sdk-rtos-j721s2-evm-08_06_00_11" sdk, I find this code in function create_error_detection_frame() in <rtos sdk>/vision_apps/modules/src/app_capture_module.c:

    static vx_status create_error_detection_frame(vx_context context, CaptureObj *captureObj, SensorObj *sensorObj)
    {
    vx_status status = VX_SUCCESS;
    IssSensor_CreateParams *sensorParams = &sensorObj->sensorParams;

    /*Error detection is currently enabled only for RAW input*/
    if(0 != captureObj->capture_format)
    {
    captureObj->enable_error_detection = 0;
    }
    ......
    }

    But my capture_format is YUV, when I set enable_error_detection to 1, this code will change it to 0.

  • Hi xinrui wang,

    This is not supported in the capture module ie in the application. This needs to be changed in the application. As such capture node seems to be supporting this feature. Can you please try changing application code? 

    Regards,

    Brijesh