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.

TMDSCSK388: Capture VIP Handle FVID2_create error!

Part Number: TMDSCSK388
Other Parts Discussed in Thread: DM388

Hi

In IPNC_RDK 3.9.0

I'm trying to configure the capture path.

I see,In

/ipnc_mcfw/mcfw/src_bios6/links_m3vpss/capture/captureLink_drv.c

..................

 pInst->captureVipHandle = FVID2_create(FVID2_VPS_CAPT_VIP_DRV,
                                           pInst->instId,
                                           pVipCreateArgs,
                                           &pInst->createStatus, &pInst->cbPrm);

UTILS_assert(pInst->captureVipHandle != NULL);

..................

FVID2_create returns 0 and the boot process stops with error

How can this be corrected ?

What will be the possible causes of this error?

Thank you.

Regards

  • Hi Nithin,

    Something in the the create args or capture path is already allocated, so it fails.

    Rgds,

    Brijesh

  • Thank you Brijesh for the reply.
    Since I'm customizing the CSK camera application. I think this application is using the create args or capture path. How can i de-allocate them?

    Please guide
    Thank you
    Regards
  • Hi Nithin,

    In this case, please dont call Capture Link Create.

    Regards,
    Brijesh
  • Thank you Brijesh,

    Sorry for not making the statements correct, I'm trying to customize the present CSK application so as to disable full camera application and enable capture. I'm not creating any camera based links in usecase.

    I'm keeping CSK application for reference

    Print message was kept in FVID2_create function for both camera link enabled and capture link enabled.

    The observation is attached below;

    1665.observation.pdf

    when the capture links are enabled with no camera links, the VIP capture driver create is not happening. driver handle function returns 0, hence making the channel 0 and the process returns error. I'm not using any external decoder controlled by DM388. Ready 16bit YCbCr video data is provided at the VIP port

    What can be the problem here?

    Does the usecase alone control this process? or is there some other place we can configure?

    Thank you

    BR

  • hi
    My usecase was not complete. I made some additions. Now the capture drive create issue is solved.

    ........
    capturePrm.numBufsPerCh = 8;
    capturePrm.numEXtraBufs = 1;
    ............

    Thank you.