@veye_xumm Thanks!

@veye_xumm Thanks, just used a PCA9306 level shifter and it works perfectly.
I was also looking at ROC-RK3588S-PC but it's a closed linux source targeting mostly Android with weird file structure, partitioning and mounting approaches so it's a no go.

Thanks!

@veye_xumm So there's no pull-ups on camera's pcb side on I2C rails?
And hey, if you (your company) really intend to support Rockchip SBCs, it's something that I'm going through with all things asked.
BTW Just looked into Orange Pi 5's datasheet and it also uses 1.8V I2C bus for cams.

@veye_xumm That's why I measured SDA and SCL with multimeter.
Anyway it seems you're not going to help me here with I2C schematics of your cam or any other way.

@veye_xumm that's really strange but IMX219's I2C DOES work just fine with 1.8V I2C bus.
Orange Pi 4 LTS uses 1.8V I2C bus, I did the measuring and here's a pic:

I don't know where you got this screenshot from, here is a link to their schematics - link

So my question was: is I2C level shifter is of any good here? and may I have your cam schematics?

@desperex said in Please advise compatible mono camera:

@veye_xumm said in Please advise compatible mono camera:

mv seriescamera access to rockchip platform is what we are promoting. It is estimated that it will be completed within a month.
As for the upgrade tool, we will also provide the corresponding binary file.

And BTW I know it's too early but maybe there's already some progress=)
I'm just interested how do you see that task, is it also something to support stats & params of Rockchip ISPs?

Is there any news?

Hello, is it possible to use the camera on device with 1.8V I2C bus?
I've just made a test on Orange Pi 4 LTS with two cameras:

1. Raspberry Pi Camera v2.1 (IMX219), camera is detected OK and registered as a subdevice though it's designed to work on 3.3V I2C bus.
2. Your RAW-MIPI-SC132M is not detected. Is it the issue with camera's I2C logic level or I need to search somewhere else for the cause? In case it's I2C voltage issue will I2C level shifter solve this?

Any may I have camera's electric schematics to discuss it on relevant forum?

@veye_xumm
Another issue that I'm having with gstreamer that I run like this:

gst-launch-1.0 v4l2src device=/dev/video1 ! "video/x-raw, width=1024, height=768" ! queue ! autovideosink -e

is sometimes gives me 'squeezed frames moving up' effect (please see video). So that may happen right after the launch of gstreamer and I have to relaunch it. I haven't had that issue with the same setup but different camera (imx219), but my ISP driver is a little bit patched to support Y8 and Y10...
Do you know is it camera related or ISP related or maybe some gstreamer bug?

@veye_xumm, is there a particular reason why veye-raw drivers are missing these controls:

• V4L2_CID_ANALOGUE_GAIN_
• V4L2_CID_EXPOSURE_
• V4L2_CID_HBLANK_
• V4L2_CID_VBLANK_

EDIT: Figured out how to implement ANALOGUE_GAIN but the rest requires your help... EXPOSURE should be somehow converted from microseconds to image lines, the rest is just not in specs.
Why PIXEL_RATE in driver is set to constant 750000000?
Shouldn't it be like that?

#define MVCAM_LINK_FREQ 750000000
#define MVCAM_NUM_DATA_LANES 2

#define MVCAM_PIXEL_RATE_8BIT = (MVCAM_LINK_FREQ * 2 * MVCAM_NUM_DATA_LANES / 8)
#define MVCAM_PIXEL_RATE_10BIT = (MVCAM_LINK_FREQ * 2 *  MVCAM_NUM_DATA_LANES / 10)

Since RAW-MIPI-SC132M camera has no AE, I'm evaluating libcamera for this purpose. And it has some requirements:
https://git.linuxtv.org/libcamera.git/tree/Documentation/sensor_driver_requirements.rst#n25

Is there any document that shows how to deal with your raw camera sensor, like creating control loop etc.?

What's your best practices of using this sensor in opencv+libcamera scenarios?

@veye_xumm said in Please advise compatible mono camera:

mv seriescamera access to rockchip platform is what we are promoting. It is estimated that it will be completed within a month.
As for the upgrade tool, we will also provide the corresponding binary file.

And BTW I know it's too early but maybe there's already some progress=)
I'm just interested how do you see that task, is it also something to support stats & params of Rockchip ISPs?

@veye_xumm said in RAW-MIPI-SC132M on VisionFive 2:

We suggest you find a dts of mipi sensor that has been running successfully on Vision Five for reference, or seek help from the board manufacturer.

Current device tree for VF2 includes working example of imx219 sensor, which is used as a base for your own driver - https://github.com/starfive-tech/linux/blob/JH7110_VisionFive2_devel/arch/riscv/boot/dts/starfive/jh7110-visionfive-v2.dtsi
I just don't see big difference.

Pins J1-11 need to be pulled high.
http://wiki.veye.cc/index.php/RAW-MIPI-SC132M_Data_Sheet#Interface_.26_Pin_list

I don't think you can put the Raspberry Pi dts directly onto Vision Five. This dts corresponds to two parts of the driver. The part of the camera driver named veyemvcam, and the other part corresponds to the mipi reception and processing driver of the main chip (for your board it is the Vision Five main chip).

Thanks, I'd probably need to study specs & docs for the sensor and SBC more deeply.