Camera bring-up with imx95

[Rathore-pioneer]

Hi All,

I am using the imx95 SVS setup

imx95[SOC] + MX95MBDES01[MAX96724] ===> {mx95mbcam[0x03C10+MAX96717F]+mx95mbcam[0x03C10+MAX96717F]+mx95mbcam[0x03C10+MAX96717F]+custom_cam[0x03H10+MAX96717]}

So basically, the entire setup is the same as SVS, but just changed the cam3 with a custom camera module [0x03H10+MAX96717].

I am making driver modifications but am facing an issue with the GMSL link lock.
My custom camera module runs with this configuration:
I2C Address: 0x84;Xtal Configuration
Coax-Pixel Mode,6Gbps

I can only see cam0-3:
root@imx95-19x19-lpddr5-evk:~# i2cdetect -l
i2c-1 i2c 44350000.i2c I2C adapter
i2c-2 i2c 42530000.i2c I2C adapter
i2c-3 i2c 42540000.i2c I2C adapter
i2c-4 i2c 426b0000.i2c I2C adapter
i2c-5 i2c 426c0000.i2c I2C adapter
i2c-6 i2c 426d0000.i2c I2C adapter
i2c-8 i2c i2c-2-mux (chan_id 0) I2C adapter
i2c-9 i2c i2c-2-mux (chan_id 1) I2C adapter
i2c-10 i2c i2c-2-mux (chan_id 2) I2C adapter

Please suggest a solution.

[db16122]

clear the camera without dust in the front; modify the background light and make the image more clean; modify the brightness and contrastness and check the result; modify the cable connect and make the joint robust

btw, the MAX96717F and MAX96717 may have some parameter difference with serdes configuration

[Rathore-pioneer]

I got this fixed by running a correct SerDes config.
Now, the camera is up, but getting too white video data.
How can I do Image tunning?
Attached a video for reference.

[Rathore-pioneer]

I got the image as output. How do I do image tuning:
Attached the image and data which I have used.

[yipingwang]

First check: Is ISP actually being used?

Run:

libcamera-hello --list-cameras

or

media-ctl -p

and verify the stream is going through:

Sensor

-> ISI

-> ISP

-> libcamera

If you're bypassing the ISP and displaying RAW data directly, image quality will look very poor. The i.MX95 camera subsystem is designed to use the ISP for RAW Bayer sensors.

Common cause #1: Wrong Bayer pattern

You replaced the SVS sensor:

OX03C10

with:

OX03H10

One of the first things to verify is:

BGGR

RGGB

GRBG

GBRG

If the Bayer order configured in the driver differs from the sensor output format, the image often appears:

• extremely bright
• wrong colors
• pink/magenta tint
• green tint

Check the sensor mode table and DT endpoint configuration.

Common cause #2: Exposure too high

Try forcing exposure manually.

For example:

v4l2-ctl -d /dev/v4l-subdevX --all

``

Check:

exposure

analog gain

digital gain

If exposure is fixed at a large value, the image will become completely white.

Common cause #3: AE/AWB not working

The i.MX95 ISP uses calibration/tuning information and IPA algorithms for:

• AE (Auto Exposure)
• AWB (Auto White Balance)
• Color correction
• Denoise
• Gamma

The camera porting guide states that a sensor-specific configuration and calibration database must be created for a new sensor.

If you simply copied the OX03C10 driver and changed the sensor ID, the ISP may still be loading OX03C10 tuning parameters, which are incorrect for OX03H10.

Common cause #4: Wrong DTP / calibration database

For i.MX95, tuning parameters are stored in sensor-specific database files:

database_<sensor>_<mode>_<resolution>_<bitdepth>.bin

The porting guide states that a dedicated calibration file must be created for a new sensor and installed through the IPA configuration.

Without proper calibration:

• exposure can be unstable
• white balance can be wrong
• colors can be inaccurate
• image may appear washed out

[Rathore-pioneer]

How to generate tuning bin files?

[yipingwang · Accepted solution]

For i.MX95 ISP, the tuning .bin (DTP database) files are not generated automatically from the BSP. According to the internal i.MX95 Camera Porting Guide and ISP training material:

• Sensor-specific tuning files are generated using the MMS Tuning Tool.
• The output is a tuning database file named like:

database_<sensor>_<mode>_<resolution>_<bitdepth>.bin

Example:

database_os08a20_SDR_3840-2160_12bpp.bin

These files are installed under:

/usr/share/libcamera/ipa/nxp/neo/uguzzi/

and are referenced by the IPA configuration

[Rathore-pioneer]

Yes, that's correct

[db16122]

so the orginal setup has 4 camera modules with MAX96724，right now you change one of the module cam3 with custom camera module MAX96717 and you can not find it. The module is chan_id 3，right？