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.

TDA4AL-Q1: how to implement the AEWB without openvx

Part Number: TDA4AL-Q1

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1258122/tda4al-q1-there-exist-openvx-graph-application-both-on-mcu2_0-and-a72-linux-lots-of-errors-on-a72-would-come-up-when-tidlnode-is-creating-or-ldc-node-is-verifying/4772626#4772626

Based on the discussion in the e2e forum above, i have some further questions to ask for help.

1) Does the capture driver can implement the AEWB function?

2) If the answer to the above point is no,  In order to get yuv image, how to implement the ISP function(AEWB) without using openvx framework?

  • Hi Bruce,

    We might require a framework that would take care of buffer transfers. Could you confirm if you have something similar to OpenVX already in place?

    Regards,

    Nikhil

  • "Could you confirm if you have something similar to OpenVX already in place?"

    No, we can't construct a second host in openvx framework, as we have construct a openvx applicaion with A72 host.

    So we only need ae awb function on MCU2_0

    Is it feasible to directly to call the function as follows:

    static vx_status VX_CALLBACK tivxAewbProcess(
    tivx_target_kernel_instance kernel,
    tivx_obj_desc_t *obj_desc[],
    uint16_t num_params, void *priv_arg)

    Of course, the function should be refactored with removing openvx framework code

  • Hi Bruce,

    Yes, but the feasibility of this approach is something that I cannot comment as this is currently not tested and supported in the SDK and this might require removal of the dependency of AEWB with OpenVX framework.

    This is something that you would have to test and confirm at your end.

    Regards,

    Nikhil