@mparem
Since I don't have the tablet board here, the following is just a suggested approach based on my guess. You can try commenting out the following two lines or modifying them as shown below:

clocks = <&ext_cam_ov5647_clk>; clock-names = "xvclk";

@newstec Cheers!

@goooofy 好的。

Your current image is Jetpack 5.1.2 with L4T version r35.4.1. The mvcam driver included in it is relatively old, so the mv_probe.sh script cannot work properly. — For more details, you can refer to the comments at the top of the mv_probe.sh script.

081b1526-6747-417e-af94-d33ffbbc08cb-image.png

In addition, please try running the following script and see if it shows continuous messages indicating that data is being received. If it still fails to receive data, please run sudo dmesg to check whether there are any error messages.

export WIDTH=2560 export HEIGHT=1544 export FPS=50 v4l2-ctl --set-ctrl roi_x=0 v4l2-ctl --set-ctrl roi_y=0 v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY v4l2-ctl --set-ctrl frame_rate=$FPS v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null

@joe

@joe said in VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected:

Questions:
What could be preventing /dev/video0 from being created, even though the sensor is detected by the kernel?

Under normal circumstances, as long as the I2C communication is working, the /dev/video0 node should be generated properly. Based on my initial assessment, your issue likely stems from differences in the usage of MIPI CSI pins between the J401 carrier board and NVIDIA's official developer kit when paired with the Orin Nano core module. Since our DTBO is based on the device tree of NVIDIA's official developer board, it may not be fully compatible with the J401 out of the box. You can try analyzing the full dmesg output to identify any errors. I suggest reaching out to Seeed for further assistance on this issue.

@golden0514 你好。
我们相机有一个底层逻辑，fps参数会优先于曝光时间设置。
如果你想要1秒的曝光时间，需要先将帧率设置为1帧/秒，然后再设置曝光时间即可。

@veye_xumm 这样啊，好的麻烦您了，我再跟公司里沟通一下

@nian 好的

@nian 不客气

@linoooooo
你好，fps参数是可以修改的。但是需要先停止取图。曝光时间是被限制到1/fps的。 你可以先设置合适的fps，然后在范围内进行曝光时间的修改。

在这个脚本中，带星号的命令，都是取图中写保护的。
你也可以参考寄存器清单中的part1.3来理解这个设置规则。

@fumyang 请问您用的是哪个相机模组？

@veye_xumm Thanks! I'll read and reinstall the SO.
Hopefully, I'll be able to show if the problem is resolved in the next few days.

@dragos You are welcome.

@linoooooo 你好，我们的相机内部isp流程是没有整帧缓存的，相机本身引入的delay是毫秒之内。
我觉得你这个延时主要是v4l2取图缓存和显示缓存的缘故。不过说实话SDL库我们不太懂，怎样优化需要您自己研究一下。
至于相机采集后，您这边程序直接导入算法的话，延迟肯定要比这种测量方法小的多。

@otca
The camera is now successfully probed, which confirms that both the I2C and the enable pin are functioning correctly.
The current issue indicates that the I2C control channel is working, but the MIPI CSI data channel is not. Please verify whether the MIPI CSI interface pin assignment on this carrier board matches that of the official Orin NX development board.
The Device Tree Source (DTS) should be adjusted accordingly to match the carrier board.

@stiwana Sorry, we do have this in mind, but no actual plans or projected time of completion at this time.

@阿坎德 你好，有进一步的结果吗？

@veye_xumm now it works, thanks

@阿坎德 看现象感觉是内存泄漏。这个demo现在基本用途上是客户做一下出图验证和聚焦。所以只是个简单的例子。回头我们会安排时间跟进一下。

@megan
First of all, please go to the following link to update the driver of mvcam. The latest driver will set the lane number in the camera according to the configuration of the DTS.

https://github.com/veyeimaging/rk35xx_veye_bsp/tree/main/linux/drivers/kernel_v5.10

Secondly, the DTS needs to be configured according to your RK3588 board, and I can't do it directly for you. You can make analogies and modifications by referring to the DTS of the camera originally supported by your board.