• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 383 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM62A3: Does ISP support multi-camera image tuning?

Gibbs Shih
Expert 5165 points
Part Number: AM62A3

Tool/software:

Hi, Dear Expert

This question is from customer.

Each camera has its own ISP tuning parameter, but AM62A only have one ISP inside,

Does our AM62A ISP support multi camera ISP parameter work at the same time?

or mult camera need to use the same ISP parameter?

Many Thanks

Gibbs

  • 0
    TI__Guru 58725 points

    Hello Gibbs,

    Yes, AM62A ISP supports multi-cameras that are not the same. For example, we have validated IMX390 + OV2312 running simultaneously.

    Regards,

    Jianzhong

  • 0 in reply to Jianzhong Xu
    TI__Expert 5165 points

    Hi, Jianzhong

    Thank you very much.

    Could you give me some related link or documents, because I need to explain to customer that how does it work

    Gibbs

  • +1 in reply to Gibbs Shih
    TI__Guru 58725 points

    Please refer to this app note: https://www.ti.com/lit/an/spradh2/spradh2.pdf. Check the Gstreamer pipelines in section 4.4 Streaming from Four Cameras. 

    Even though the 4 cameras are the same in these use cases, the ISP is configured with a binary file for each camera. 

    Below is a pipeline for running with IMX390 and OV2312:

    gst-launch-1.0 \
    v4l2src device=/dev/video-ov2312-rgb-cam0 ! video/x-bayer, width=1600, height=1300, format=bggi10 ! queue leaky=2 ! \
    tiovxisp sensor-name=SENSOR_OV2312_UB953_LI \
    dcc-isp-file=/opt/imaging/ov2312/linear/dcc_viss.bin \
    sink_0::dcc-2a-file=/opt/imaging/ov2312/linear/dcc_2a.bin sink_0::device=/dev/v4l-ov2312-subdev0 format-msb=9 \
    sink_0::pool-size=8 src::pool-size=8 ! \
    video/x-raw, format=NV12, width=1600, height=1300 ! queue ! mosaic.sink_0 \
    v4l2src device=/dev/video-imx390-cam0 io-mode=5 ! video/x-bayer, width=1936, height=1100, format=rggb12 ! queue leaky=2 ! \
    tiovxisp sensor-name=SENSOR_SONY_IMX390_UB953_D3 \
    dcc-isp-file=/opt/imaging/imx390/linear/dcc_viss.bin \
    sink_0::dcc-2a-file=/opt/imaging/imx390/linear/dcc_2a.bin sink_0::device=/dev/v4l-imx390-subdev0 format-msb=11 \
    sink_0::pool-size=8 src::pool-size=8 ! \
    video/x-raw, format=NV12, width=1936, height=1100 ! queue ! mosaic.sink_1 \
    tiovxmosaic name=mosaic \
    sink_0::startx="<0>" sink_0::starty="<0>" sink_0::widths="<640>" sink_0::heights="<480>" \
    sink_1::startx="<640>" sink_1::starty="<480>" sink_1::widths="<640>" sink_1::heights="<480>" ! \
    kmssink driver-name=tidss sync=false

    We will be adding this use case to the app note in a few weeks.

    Regards,

    Jianzhong