@veye_xumm said in Please advise compatible mono camera:
Which functions of isp do you need, please?
Just AE,IS and crop, if there was a way to skip ISP, I'd do.
Other reqs would come up later, now I just can't start developing CV part.
@veye_xumm said in Please advise compatible mono camera:
Which functions of isp do you need, please?
Just AE,IS and crop, if there was a way to skip ISP, I'd do.
Other reqs would come up later, now I just can't start developing CV part.
@veye_xumm After deep analysis of rkisp driver I see two completely different implementations:
@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.
EDIT: There's also a warning "mvcam 4-003b: Consider updating driver mvcam to match on endpoints", not sure if it's harmful or not
https://github.com/torvalds/linux/blob/v6.1/drivers/media/v4l2-core/v4l2-async.c#L142
Ok will work on no.1 while waiting for any updates from you
Thanks!
@veye_xumm
Just finished setting up RAW-MIPI-SC132M camera on rock pi 4b using rpi mvcam ported driver.
Now I'm trying to create a working rkisp1 pipeline, which is not straightforward for me, so I've got some questions:
EDIT: So this setup is to use the sensor in OpenMV, if rkisp1 just can't work with mono cams, is there any other way to use this cam in my configuration?
Below is media topology for reference:
media-ctl -p -d "platform:rkisp1"
Media controller API version 5.15.90
Media device information
------------------------
driver rkisp1
model rkisp1
serial
bus info platform:rkisp1
hw revision 0xa
driver version 5.15.90
Device topology
- entity 1: rkisp1_isp (4 pads, 5 links)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev0
pad0: Sink
[fmt:SRGGB10_1X10/1080x1280 field:none
crop.bounds:(0,0)/1080x1280
crop:(0,0)/1024x768]
<- "mvcam 4-003b":0 [ENABLED]
pad1: Sink
[fmt:unknown/0x0 field:none]
<- "rkisp1_params":0 [ENABLED,IMMUTABLE]
pad2: Source
[fmt:YUYV8_2X8/1024x768 field:none
crop.bounds:(0,0)/1024x768
crop:(0,0)/1024x768]
-> "rkisp1_resizer_mainpath":0 [ENABLED]
-> "rkisp1_resizer_selfpath":0 []
pad3: Source
[fmt:unknown/0x0 field:none]
-> "rkisp1_stats":0 [ENABLED,IMMUTABLE]
- entity 6: rkisp1_resizer_mainpath (2 pads, 2 links)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev1
pad0: Sink
[fmt:YUYV8_2X8/1024x768 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range
crop.bounds:(0,0)/1024x768
crop:(0,0)/800x600]
<- "rkisp1_isp":2 [ENABLED]
pad1: Source
[fmt:YUYV8_2X8/1024x768 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
-> "rkisp1_mainpath":0 [ENABLED,IMMUTABLE]
- entity 9: rkisp1_resizer_selfpath (2 pads, 2 links)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev2
pad0: Sink
[fmt:YUYV8_2X8/800x600 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range
crop.bounds:(0,0)/800x600
crop:(0,0)/800x600]
<- "rkisp1_isp":2 []
pad1: Source
[fmt:YUYV8_2X8/800x600 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:lim-range]
-> "rkisp1_selfpath":0 [ENABLED,IMMUTABLE]
- entity 12: rkisp1_mainpath (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video5
pad0: Sink
<- "rkisp1_resizer_mainpath":1 [ENABLED,IMMUTABLE]
- entity 16: rkisp1_selfpath (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video6
pad0: Sink
<- "rkisp1_resizer_selfpath":1 [ENABLED,IMMUTABLE]
- entity 20: rkisp1_stats (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video7
pad0: Sink
<- "rkisp1_isp":3 [ENABLED,IMMUTABLE]
- entity 24: rkisp1_params (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video8
pad0: Source
-> "rkisp1_isp":1 [ENABLED,IMMUTABLE]
- entity 28: mvcam 4-003b (1 pad, 1 link)
type V4L2 subdev subtype Sensor flags 0
device node name /dev/v4l-subdev3
pad0: Source
[fmt:Y8_1X8/1080x1280 field:none colorspace:srgb
crop.bounds:(0,0)/1080x1280
crop:(0,0)/1080x1280]
-> "rkisp1_isp":0 [ENABLED]
@veye_xumm thanks for the input, will give it a try with SC132 on rock pi 4b+, sure there will be lot to do with dts.
Yes it's old, but still good in terms of cores/RAM/M.2 support, it only lacks extra CSI and 4 lanes/MIPI CSI-2 support.
It'd be really cool to see your roadmap with all stuff planned and I hope there will be Orange Pi 5 with SC130 adapter for my next project.
Hi there, I'm interested in SC130 and SC132 mono cameras, going to use them on Rock Pi 4B+ now and probably later on Orange Pi 5.
Concerning Rock Pi 4B+ (RK3399): I see there were some issues with similar board (http://wiki.veye.cc/index.php/VEYE_MIPI_327_for_Nano_Pi_4_ubuntu#Exsiting_bugs) and different camera, but I guess the tests were not done on mainline 5.10+ kernels (which has rkisp1 official support). Anyway I'll probably need an adapter.
Concerning Orange Pi 5: I see you support t-firefly ROC-RK3588S-PC, but Pi 5 uses different type of camera connector, so the adapter is definitely required.
So the question is are those two sensors compatible with two stated boards?