Skip to main content

OMSBDAAN

Overview

OMSBDAAN camera module is equipped with OmniVision CMOS image sensor OX05B1S and Maxim GMSL serializer MAX9295A. It has an automotive-grade sensor with a well tuned Image Signal Processor (ISP) that produces exceptional image quality, It is also equipped with an M12 automotive grade lens that supports visible light and 940nm infrared light recognition.

OMSBDAAN

Getting Started

Specification

ParameterValue
SensorOmniVision 5MP OX05B1S RGB-IR
ISPOAX4000
Image Size1/2.53 inch CMOS
Output PixelsAA mode: 2592H *1944V / AB mode: 2592H *1800V
Frame rateAA mode: 2592H *1944V@30fps / AB mode: 2592H *1800V@60fps
Pixel Size2.2um*2.2um
HDR Support/
Output dataYUV422-8bit
SerializerMAXIM MAX9295A
IR FilterVisible+940nm band pass
Camera InterfaceGMSL2
Power SupplyPOC: 9~16V , LED: 9 ~16V DC
CurrentPOC: Less than 350mA@12VDC , LED: Less than 400mA@12VDC
ConnectorAmphenol Fakra(Z Code)+Molex
Operating temp.-40 to +85°C
DimensionsW: 28.8mm, L:44.2mm, H:20mm
WeightLess than 50g

Dimensions

OMSBDAAN

Hardware Overview

Block Diagram

OMSBDAAN

I2C Address Information

ComponentParameterValue
SerializerModelMax9295A
I2C Address0x80 (8bit address)
GMSL RateGMSL2 (6G bps)
ISPModelOAX4000
I2C Address0x48 (8bit address)
ResetControlled by Max9295A MFP0
SensorModelOX05B1S
I2C Address0x6C (8bit address)
Frame SyncControlled by Max9295A MFP7
ERRORControlled by Max9295A MFP3

LED Connector Pin Definition

OMSBDAAN_LED_Connect

Pin DefinitionOperating Voltage RangeSteady State CurrentInterface Type
PINDescriptionMax(V)Min(V)(mA)
1VCC+169<400mA@12VMolex
(5600200220)
2GND000

Lens Options

ModelHFOVVFOVF.NoEFLMax Optical DistortionWater-proofLens Mount
OMSBDAAN130°98°@1944V2.02.18mm-39.2%@HFOVIP5XM12

Parts List

Standard Configuration
  • OMSBDAAN
  • Power Supply Cable

Camera Working Mode

1. AA Mode

OMSBDAAN_WorkMode_AA
Parameter itemParameter Description
Resolution2592 x 1944
Frame Rate30fps
Output dataUYVY/YUYV
MIPI4lane, 800Mbps/lane

When the scene brightness is greater than the brightness threshold, the RGB image is output at a frame rate of 30fps.

When the scene is less than the brightness threshold, the output IR image will be automatically switched with a frame rate of 30fps.

The brightness threshold is set through register configuration.

2. AB Mode

OMSBDAAN_WorkMode_AB
Parameter itemParameter Description
Resolution2592 x 1800
Frame RateRGB: 30fps; IR: 30fps
Output dataUYVY/YUYV
MIPI4lane, 1296Mbps/lane

Frame A outputs RGB images, VC channel is 0, frame rate is 30fps; B frame outputs IR image, VC channel is 1, frame rate is 30fps.

Important Notice

The camera can only output in either AA or AB mode. Please specify your required mode to the sales staff when purchasing the camera.

Employing Camera

1. Adaptation to NVIDIA® Jetson™ platform

OMSBDAAN_ConnectNvidia

OMSBDAAN Camera Connect to Nvidia Jetson AGX Orin

Step 1: Installation Steps

Quick Setup
  1. Connect the OMSBDAAN camera to the SG8A-ORIN-GMSL2 board using the coaxial cable
  2. Mount the SG8A-ORIN-GMSL2 board onto the Jetson AGX Orin module
  3. OMSBDAAN camera Connect the power supply
  4. SG8A-ORIN-GMSL2 board Connect the power supply
  5. Power on the system

Step 2: Software Preparation

SDK Download

-Select the appropriate driver package based on your camera type and JetPack version:

-Copy the full link address to DownGit to download

NO.JetPack VersionCamera modeNVIDIA Jetson DevicesAdapter BoardDownload Link
1JP5.1.2AA modeJetson AGX Orin Developer KitSG8A-ORIN-GMSL2-FDownload
2JP5.1.2AB modeJetson AGX Orin Developer KitSG8A-ORIN-GMSL2-FDownload
JetPack Versions

NVIDIA JetPack (Jetpack 5.1.2 or Jetpack 6.0 ) is the official software development kit (SDK) for the Jetson series of development boards. It includes the operating system, drivers, CUDA, cuDNN, TensorRT, and other development tools and libraries. Each JetPack version typically corresponds to a specific Jetson Linux version (formerly known as L4T - Linux for Tegra).

  • 36.4.3: L4T R36.4.3 (Jetpack 6.2)
  • 36.4: L4T R36.4 (Jetpack 6.1)
  • 36.3: L4T R36.3 (Jetpack 6.0)
  • 35.4.1: L4T R35.4.1 (Jetpack 5.1.2)

For more information, visit NVIDIA's official Jetson Download Center.

2. Camera Integration with Customer's Self-developed Platform

For customers with their own deserializer who want to adapt our camera (serializer) to their platform, detailed technical coordination is required.

SG8A-ORIN-GMSL2-complete

The diagram illustrates the communication architecture between a camera and controller system. It shows how data flows from the Sensor/ISP through the Serializer on the Camera side, across to the Deserializer and SOC on the Controller side. The system utilizes Fsync signals for synchronization and MFP7 interfaces for control. This architecture is essential for proper integration of SENSING cameras with customer-developed platforms.

SENSING will provide:

  • Serializer and Deserializer Configuration

  • Link Status Troubleshooting Guide

    • Link training parameters
    • Error detection settings
tip

Please refer to the software flow and demo code below to develop your driver code.

Software Development

  1. Driver Development:
/* Example code for MAX9296 I2C initialization */
#define MAX9296_I2C_ADDR 0x90 // 8-bit address

int max9296_init() {
// Initialize I2C bus
i2c_init();

// disable MIPI output
i2c_write(MAX9296_I2C_ADDR, 0x0313, 0x00);
delay_ms(100);
// Configure link settings for GMSL2 (6Gbps)
i2c_write(MAX9296_I2C_ADDR, 0x0001, 0x02);

// Configure linkA and linkB settings for GMSL2 selection (default value)
i2c_write(MAX9296_I2C_ADDR, 0x0006, 0xC0);

// Configure MIPI rate 1200Mbps
i2c_write(MAX9296_I2C_ADDR, 0x0320, 0x2C);

// enable MIPI output
i2c_write(MAX9296_I2C_ADDR, 0x0313, 0x02);

return 0;
}
  1. Camera Configuration:
/* Example code for OMSBDAAN  initialization */

#define MAX9295_I2C_ADDR 0x80 // 8-bit address

int camera_init() {
// Initialize deserializer first
max9296_init();

// Reset ISP through MAX9295A
i2c_write(0x80, 0x02BE, 0x10); // MFP0 high
//
i2c_write(0x80, 0x0057, 0x12);
i2c_write(0x80, 0x005B, 0x11);
// Configure datatype YUV422 8bit
i2c_write(0x80, 0x0318, 0x5E);

// camera trigger MFP7 low to high
i2c_write(0x80, 0x02D3, 0x00); // MFP7 low
delay_ms(300);
i2c_write(0x80, 0x02D3, 0x10); // MFP7 high

return 0;
}

Integration Steps

  1. BSP Integration:

    • Modify the device tree to include the CSI interface configuration
    • Add camera driver to kernel build configuration
    • Configure media controller pipeline for the camera
  2. Application Development:

/* Example code for capturing camera frames */
#include "camera_api.h"

int main() {
// Open camera device
int fd = open("/dev/video0", O_RDWR);
if (fd < 0) {
perror("Failed to open camera device");
return -1;
}

// Configure video capture format
struct v4l2_format fmt = {0};
fmt.type = V4L2_BUF_TYPE_VIDEO_CAPTURE;
fmt.fmt.pix.width = 2592;
fmt.fmt.pix.height = 1944;
fmt.fmt.pix.pixelformat = V4L2_PIX_FMT_YUYV;

if (ioctl(fd, VIDIOC_S_FMT, &fmt) < 0) {
perror("Failed to set format");
close(fd);
return -1;
}

// Request and map buffers
// ... (buffer setup code) ...

// Start streaming
// ... (streaming code) ...

// Capture and process frames
// ... (frame processing code) ...

// Cleanup
close(fd);
return 0;
}

Step 2: Data Processing

After receiving the module data through the MIPI CSI interface:

  • Data Reception
    • MIPI CSI-2 protocol implementation
    • Data rate configuration
    • Clock synchronization
  • Image Processing
    • Raw/YUV data parsing
    • Image format conversion
    • Display configuration

Technical Support

  • Documentation

    • Detailed register descriptions
  • Engineering Support

    • Technical consultation
    • Debug assistance
    • Performance optimization
tip

SENSING Technology provides technical support for integration with most platforms. For detailed documentation, sample code, and technical assistance, please contact our support team.