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.

  • TI Thinks Resolved

TDA2P-ACD: Capture and Display 6 Sensors simultaneously (two CSI2 Ports)

Part Number: TDA2P-ACD

Hello Experts,

I found the following thread and was wondering if the functionality to run more than 4 sensors at the same time has been added to the PSDK since then.

e2e.ti.com/.../703535

Currently I try to run and display six sensors (IMX390) simultaneously on the TDA2Px + Fusion Board. Four sensors are connected to CSI2-PHY1 and two to CSI2-PHY2. Unfortunately the PSDK crashes when it reaches the function IssM2mIspLink_drvAllocFrames(). So I just want to make sure if it is possible at all to run these six sensors at the same time.

Regards,

Tobias

  • In reply to Tobias Schulze:

    Hi Tobias,

    It is not problem in using 2 phys. But sure, you could start with this usecase.
    Capture module, CAL, has internal limitation. Because of which, we need to run addition channel through another driver.

    Rgds,
    Brijesh
  • In reply to Brijesh Jadav:

    Hey Brijesh,

    which module will then take part of the remaining channels?
    I also found the new define VPS_ISS_CALM2M_BUILD in the PSDK 3.5. Is that part of the new driver you wrote?

    Regards,
    Tobias
  • In reply to Tobias Schulze:

    Hi Tobias,

    Yes, this is the new driver which will be used for the conversion.

    Rgds,

    Brijesh

  • In reply to Brijesh Jadav:

    Hey Brijesh,

    could you please tell me which module will process the remaining two channels then? Another CAL or do we use the same CAL and time-share it?
    I also noticed that capture CAL is named 'CAL_B', is there an 'CAL_A'?

    Also, could you give me a small guideline on how to use the new driver? The location where I have to add changes to the code, maybe?

    Thank you!

    Tobias

  • In reply to Tobias Schulze:

    Hey Brijesh,

    I changed the driver create function in the ISP link to use VPS_M2M_ISS_INST_CAL_ISP to VPS_M2M_ISS_INST_CALM2M, so that ISP link uses the new drivers. Unfortunately I get an assertion while setting the pixel processing configs in CalSetPixProcCfg().

    (VPS_ISS_CAL_PIX_EXRCT_MIN != cfg->extract)

    Do I have to change some other parameters to make this work?

    Regards,
    Tobias
  • In reply to Tobias Schulze:

    Hi Tobias,

    You need to set pixel extract config to 12bit mipi (VPS_ISS_CAL_PIX_EXRCT_B12_MIPI) format.

    Rgds,

    Brijesh

  • In reply to Brijesh Jadav:

    Hi Brijesh,

    it was already set to VPS_ISS_CAL_PIX_EXRCT_B12_MIPI in IssCaptureLink_drvSetDrvCfg. The first time CalSetPixProcCfg is called, the extract value is correct and I dont get the assertion.
    But after the driver is created the problem is in vcoreCalm2mApplyConfig() in vpscore_calm2m.c. In the following line the pixel extract config is set to cfg.inPixExtract (also see attached image):

    calCfg.pixProcCfg[0].extract = cfg.inPixExtract;

    All other parameters from cfg are 0, so it seems this config isnt initialized. At least I couldn't find the init function. Do you know how to solve this?


    Thank you,
    Tobias

  • In reply to Tobias Schulze:

    Hi Tobias,

    ok, so this is not in iss capture configrations. It seems you are trying to use new m2m path, which internally uses cal.

    we need to similarly configure cal even in m2m path. You could look into the example application in ti_components\drivers\pdk_01_10_01_06\packages\ti\drv\vps\examples\iss\m2mIssCal\src\ to understand how to configure it.  This example converts 12bit mipi to 12bit linear.

    Rgds,

    Brijesh  

  • In reply to Brijesh Jadav:

    Hi Brijesh,

    alright, I will take a look at the example.
    Just to be sure: this new m2m path makes it possible to use more than 4 sensors simultaneously?

    Regards,
    Tobias
  • In reply to Tobias Schulze:

    Yes, it is in the way i explained earlier.

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.