Skip to main content
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 InterfaceAnalog SwitchCamera ConnectorB2B Connector
CSI0U45 (TMUX646ZECR)JCAM0JEXP4, Pins 111–120
CSI1U42 (TMUX646ZECR)JCAM1JEXP4, Pins 51–60
CSI2U44 (TMUX646ZECR)JCAM2JEXP4, Pins 40–49
CSI3U43 (TMUX646ZECR)JCAM3JEXP4, 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.
SwitchONOFF (default)
SW1-5CSI0 → GMSL mezzanineCSI0 → mainboard
SW1-6CSI1 → GMSL mezzanineCSI1 → mainboard
SW1-7CSI2 → GMSL mezzanineCSI2 → mainboard
SW1-8CSI3 → GMSL mezzanineCSI3 → 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

ResolutionAspect RatioIMX577OV9282
4000 × 30004:3YesNo
3840 × 216016:9YesNo
1920 × 108016:9YesNo
1280 × 72016:9YesYes
1024 × 7684:3YesYes
800 × 6004:3YesYes
640 × 4804:3YesYes
320 × 2404:3YesYes
  • 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

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.
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

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:
scp -r root@[ip-addr]:/opt/mux_avc. mp4 .

Video Encoding + Snapshot

1

Start the pipeline

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
2

Take a snapshot

From the interactive menu: (1) Ready → (3) Playing → (p) Plugin Mode → (11) camerasrc → (37) capture-image → (1) Snapshot → enter count
3

Stop and retrieve files

Press Enter → b (Back) → q (Quit).
scp -r root@[ip-addr]:/opt/<file name> .

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:
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

1

Check camera module connection and DIP switch settings

2

Restart cam-server

systemctl restart cam-server
# or
pkill cam-server
3

Run a single-stream test

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:
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:
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

journalctl -f > /opt/user_log.txt   # User space logs
dmesg -w > /opt/kernel_log.txt      # Kernel logs

Resources

TopicLink
Camera ArchitectureCamera Architecture
Camera Sensor Driver DevelopmentCamera Sensor Driver Development
Customize Camera Use Case and PipelineCustomize Camera Use Case and Pipeline
Customize Advanced Camera FeaturesCustomize Advanced Camera Features