> ## Documentation Index > Fetch the complete documentation index at: https://dragonwingdocs.qualcomm.com/llms.txt > Use this file to discover all available pages before exploring further. # Camera The IQ9-EVK supports camera sensor connectivity through four MIPI CSI interfaces, supporting both C-PHY and D-PHY modes. ## Hardware Architecture ### CSI Interface Mapping | CSI Interface | Analog Switch | Camera Connector | B2B Connector | | ------------- | ----------------- | ---------------- | ------------------- | | CSI0 | U45 (TMUX646ZECR) | JCAM0 | JEXP4, Pins 111–120 | | CSI1 | U42 (TMUX646ZECR) | JCAM1 | JEXP4, Pins 51–60 | | CSI2 | U44 (TMUX646ZECR) | JCAM2 | JEXP4, Pins 40–49 | | CSI3 | U43 (TMUX646ZECR) | JCAM3 | JEXP4, Pins 29–38 | ### DIP Switch Configuration The four CSI PHYs can be routed to either MIPI camera ports or GMSL camera ports (via mezzanine board) using DIP switches. | Switch | ON | OFF (default) | | ------ | --------------------- | ---------------- | | SW1-5 | CSI0 → GMSL mezzanine | CSI0 → mainboard | | SW1-6 | CSI1 → GMSL mezzanine | CSI1 → mainboard | | SW1-7 | CSI2 → GMSL mezzanine | CSI2 → mainboard | | SW1-8 | CSI3 → GMSL mezzanine | CSI3 → mainboard | ## Supported MIPI CSI Camera Sensors ### ov9282 Camera Sensor ### Arducam imx577 Camera Sensor **Arducam sensor requires an additional converter board(Arducam 22-pin to Qualcomm 30-pin CSI adapter)** **Arducam imx577 sensor + 22 pin flex cable + converter board** ### Arducam imx577 Camera Sensor connection to iq9075 ### ov9282 Camera Sensor connection to iq9075 ## Supported Resolutions | Resolution | Aspect Ratio | IMX577 | OV9282 | | ----------- | ------------ | ------ | ------ | | 4000 × 3000 | 4:3 | Yes | No | | 3840 × 2160 | 16:9 | Yes | No | | 1920 × 1080 | 16:9 | Yes | No | | 1280 × 720 | 16:9 | Yes | Yes | | 1024 × 768 | 4:3 | Yes | Yes | | 800 × 600 | 4:3 | Yes | Yes | | 640 × 480 | 4:3 | Yes | Yes | | 320 × 240 | 4:3 | Yes | Yes | * Advanced features such as SHDR, LDC, and EIS are not supported on IQ-9075. * There is no hardware JPEG encoder — snapshots use a software encoder running on the CPU. ## Camera Streaming ### Single Camera Stream ```bash theme={null} gst-launch-1.0 -e qtiqmmfsrc name=camsrc camera=0 ! 'video/x-raw,format=NV12,\ width=1280,height=720,framerate=30/1' ! fakesink ``` The above command starts the camera with 720p at 30 FPS configuration. The frame coming from the camera sensor is thrown away by fakesink. If the gst pipeline status is changed to “PLAYING” as shown below, this indicates that the camera is running. Since this command dumps camera frames to fakesink, nothing will be saved on the device. If the pipeline status changes to `PLAYING`, the camera is running. Press `Ctrl+C` to stop. ```bash theme={null} gbm_create_device(187): Info: backend name is: msm_drm Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... New clock: GstSystemClock ``` ### Video Encoding ```bash theme={null} gst-launch-1.0 -e qtiqmmfsrc name=camsrc camera=0 ! \ video/x-raw,format=NV12,width=1280,height=720,framerate=30/1,\ interlace-mode=progressive,colorimetry=bt601 ! v4l2h264enc \ capture-io-mode=4 output-io-mode=5 extra-controls="controls,video_bitrate=6000000,\ video_bitrate_mode=0;" ! h264parse ! mp4mux ! filesink location=/opt/mux_avc.mp4 ``` This command starts the camera with 720p at 30 FPS configuration and saves it as a video file after h264 video encoding. If the gst pipeline status is changed to “PLAYING”, this indicates the camera is running. To stop the camera, press CTRL+C. /opt/mux\_avc.mp4 is generated on the device. The recorded content can be pulled from the device by running the following scp command on the host PC: ```bash theme={null} scp -r root@[ip-addr]:/opt/mux_avc. mp4 . ``` ### Video Encoding + Snapshot ```bash theme={null} gst-pipeline-app -e qtiqmmfsrc name=camsrc camera=0 ! video/x-raw,format=NV12,width=1280,height=720,\ framerate=30/1,interlace-mode=progressive,colorimetry=bt601 ! queue ! v4l2h264enc capture-io-mode=4 \ output-io-mode=5 extra-controls="controls,video_bitrate_mode=0,video_bitrate=6000000;" ! queue ! \ h264parse ! mp4mux ! queue ! filesink location="/opt/mux_720_avc.mp4" camsrc.image_1 ! "image/jpeg,\ width=1280,height=720,framerate=30/1" ! multifilesink location=/opt/frame%d.jpg async=false sync=true \ enable-last-sample=false ``` From the interactive menu: **(1) Ready → (3) Playing → (p) Plugin Mode → (11) camerasrc → (37) capture-image → (1) Snapshot → enter count** Press Enter → `b` (Back) → `q` (Quit). ```bash theme={null} scp -r root@[ip-addr]:/opt/ . ``` ## Multi-Camera with Offline IFE The IQ-9075 has two IFEs for real-time bayer-to-YUV processing. A maximum of two cameras can operate concurrently with real-time IFE The **Offline IFE** feature allows a single IFE to process two cameras in offline mode, enabling concurrent streaming upto four cameras. Each Sensor is connected to one IFE-Lite hardware instance and data is dumped to DDR using the RDI port. A single IFE hardware is being used to read data from two IFE-Lites using bus fetch engine SFE Lite and processing data in Offline mode. With this approach, instead of directly feeding the camera frames to IFE, frames are routed from IFE\_LITE and dumped in DDR. Then they’re provided to IFE using the fetch engine SFE Lite for bayer-to-YUV processing. ### Verify Multi-Camera Operation Conenct Four OV9292 MIPI cameras connected to four MIPI CSI slots (0, 1, 2, and 3) Run a GST command with **multicamera-hint=true** for each camera to enable this feature. For example: ```bash theme={null} gst-launch-1.0 -e qtiqmmfsrc name=camsrc camera=0 multicamera-hint=true ! \ video/x-raw,format=NV12,width=1280,height=720,framerate=30/1,\ interlace-mode=progressive,colorimetry=bt601 ! v4l2h264enc \ capture-io-mode=4 output-io-mode=5 extra-controls="controls,video_bitrate=6000000,\ video_bitrate_mode=0;" ! h264parse ! mp4mux ! filesink location=/opt/mux_avc.mp4 ``` **Check for below print in user log to confirm offline ife feature is enabled** ``` CamX: [CORE_CFG]3509 3556 [CORE ] camxpipeline.h:4222 SetPipelineStatus() RealTimeFeatureZSLPreviewRawOfflineIFE_0_cam_0 status is now PipelineStatus::STREAM_ON ``` ## Troubleshooting ```bash theme={null} systemctl restart cam-server # or pkill cam-server ``` ```bash theme={null} gst-launch-1.0 -e qtiqmmfsrc name=camsrc camera=0 ! 'video/x-raw,format=NV12,\ width=1280,height=720,framerate=30/1' ! fakesink ``` Collect logs and search for `probe success`: ```bash theme={null} journalctl -f > /opt/user_log.txt ``` **Expected probe success log:** ``` CAM_INFO: CAM-SENSOR: Probe success, slot:0, slave_addr: 0x34, sensor_id:0x577 ``` If no probe success appears, check the flex cable connection or camera module. Enable CSI debug logs and collect dmesg: ```bash theme={null} echo 3 > /sys/kernel/debug/camera/ife/ife_csid_debug dmesg -w > /opt/kernel_log.txt ``` Start the camera and check for SOF/EOF IRQ messages in the log. **Expected logs:** ``` CAM_INFO: CAM-ISP: cam_ife_csid_irq: 5288 CSID:1 IPP SOF received CAM_INFO: CAM-ISP: cam_ife_csid_irq: 5300 CSID:1 IPP EOF received CAM_INFO: CAM-ISP: cam_ife_csid_irq: 5288 CSID:1 IPP SOF received CAM_INFO: CAM-ISP: cam_ife_csid_irq: 5300 CSID:1 IPP EOF received ``` ### Collect Debug Logs ```bash theme={null} journalctl -f > /opt/user_log.txt # User space logs dmesg -w > /opt/kernel_log.txt # Kernel logs ``` ## Resources | Topic | Link | | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Camera Architecture | [Camera Architecture](https://docs.qualcomm.com/doc/80-70023-17A/topic/camera-architecture.html) | | Camera Sensor Driver Development | [Camera Sensor Driver Development](https://docs.qualcomm.com/doc/80-70023-17A/topic/camera-sensor-driver-development.html) | | Customize Camera Use Case and Pipeline | [Customize Camera Use Case and Pipeline](https://docs.qualcomm.com/doc/80-70023-17A/topic/customize-camera-use-case-and-pipelines.html) | | Customize Advanced Camera Features | [Customize Advanced Camera Features](https://docs.qualcomm.com/doc/80-70023-17A/topic/customize-advanced-camera-features.html) |