@joe The RAW-MIPI-AR0234M is a MONO camera that has no color information and therefore does not support the UYVY data format. Please refer to this link below:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson#Configuring_global_variables
@joe
Please get tegra234-p3767-camera-p3768-veyecam2m-raw_ar0234m.dtbo
from here:
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/dtbs/Orin/JetPack_6.1_Linux_JETSON_ORIN_TARGETS/orin_nx_nano
@joe
It is better to compile dtbo in the cross-compile environment of the jetson system, because there are some references that may not be available on the orin board.
I'll arrange to do a bit of compiling for you as soon as possible.
@joe said in different modules simultaneously on jetson nano mipi interface:
It's still the same procedure：
What you need to do is to reintegrate the DTS based on our released code and compile it into the required DTB file.
Specifically, the DTB file we are currently releasing configures both CAM0 and CAM1 as the same camera model.
Now, you need to integrate the DTS files of the two camera models into one DTB file. This will specify that CAM0 is one model and CAM1 is another model of the camera.
@xym
你参考这个脚本试试：
export I2C_BUS=7
export WIDTH=1456
export HEIGHT=1088
export FPS=60
v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_x=0
v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_y=0
media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'
v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null
@aike 我们对接rk平台的经验中，只有一个厂家的板子遇到了给你这个完全一样的问题，就是用上次帖子中的方法解决的。该问题原因是此板厂提供的linux内核，调用veyecam2m_enum_frame_sizes时没有正确的传入fse->code参数，导致参数验证失败。
如果你这个方法解决不了问题，建议打开驱动中的DEBUG_PRINTK宏定义，查找一下哪个函数返回报错了。
如果只是打开这个宏定义不够，需要你手动在这些函数返回错误的地方增加打印信息，进行查找报错处。
For third-party carrier boards on the Orin Nano or Orin NX platform, we have indeed encountered issues with MIPI signal transmission quality. There isn't a good solution at the moment, so we recommend switching to an official NVIDIA board.
@aike
你试一下将驱动中下面这个函数改成如下：
static int veyecam2m_enum_frame_sizes(struct v4l2_subdev *sd,
struct v4l2_subdev_pad_config *cfg,
struct v4l2_subdev_frame_size_enum *fse)
{
VEYE_TRACE
if (fse->index >= ARRAY_SIZE(supported_modes))
return -EINVAL;
//if (fse->code != VEYECAM2M_MEDIA_BUS_FMT/*MEDIA_BUS_FMT_UYVY8_2X8*/)
// return -EINVAL;
fse->min_width = supported_modes[fse->index].width;
fse->max_width = supported_modes[fse->index].width;
fse->max_height = supported_modes[fse->index].height;
fse->min_height = supported_modes[fse->index].height;
return 0;
}
然后重新编译一下再测测。
@mv
May I ask what model of module you are using? Also, please repeat the test on an official nvidia board.
@paul-chang
这个只是一个提示信息，不影响驱动加载和后续测试的。
你可以看看有没有生成/dev/video0,如果没有，看看dtb是不是用对了。
@paul-chang
你可以先忽略这个提示，直接按照wiki文档的说明，继续测试一下取图等功能。
@dan Yes, we have this program and we have purchased a firelfy ROC-RK3576-PC board planned for driver porting.
It is estimated that this will be done within this month.
@aike 可能性很小。你试试用这个脚本抓一下图：
v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat='NV12' --stream-mmap --stream-count=100 --stream-to=nv12-1920x1080.yuv
``@aike 这个我们在其他的板卡上没有遇到过。你的板子本身没有带gstreamer吗？ 或者问问板卡厂家。
@aike 首先，我们这个模组是带有isp的，因此在dts中，isp部分都给bypass掉了。
其次，你可以先试试我们wiki上的gstreamer例子，看看能不能预览。
@aike 我觉得dts没问题，你可以试试把veyecam2m直接编译到内核里面，而不是独立ko的形式试试。
关于dts的逻辑关系，你可以参考这篇文章。
https://www.cnblogs.com/armsom/articles/17449250.html
@aike 试试这个
// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
/*
* Copyright (c) 2022 www.veye.cc
*
*/
#include "tl3588-evm.dts"
&i2c1 {
status = "okay";
// pinctrl-names = "default";
// pinctrl-0 = <&i2c1m2_xfer>;
veyecam2m: veyecam2m@3b{
compatible = "veye,veyecam2m";
reg = <0x3b>;
clocks = <&cru CLK_MIPI_CAMARAOUT_M1>;
clock-names = "xvclk";
status = "okay";
// pinctrl-names = "default";
// pinctrl-0 = <&mipim1_camera1_clk>;
//power-domains = <&power RK3588_PD_VI>;
//power-gpios = <&gpio4 RK_PB5 GPIO_ACTIVE_LOW>;
reset-gpios = <&gpio2 RK_PC3 GPIO_ACTIVE_LOW>;
//pwdn-gpios = <&gpio2 RK_PC3 GPIO_ACTIVE_LOW>;
//avdd-supply = <&vcc_mipidcphy1>;
//firefly,clkout-enabled-index = <0>;
rockchip,camera-module-index = <0>;
rockchip,camera-module-facing = "back";
rockchip,camera-module-name = "NC";
rockchip,camera-module-lens-name = "NC";
port {
veyecam2m_out0: endpoint {
remote-endpoint = <&mipi_dphy1_in_ucam0>;
data-lanes = <1 2>;
};
};
};
};
&csi2_dphy0_hw {
status = "okay";
};
&csi2_dphy1 {
status = "okay";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
#address-cells = <1>;
#size-cells = <0>;
mipi_dphy1_in_ucam0: endpoint@1 {
reg = <1>;
remote-endpoint = <&veyecam2m_out0>;
data-lanes = <1 2>;
};
};
port@1 {
reg = <1>;
#address-cells = <1>;
#size-cells = <0>;
csidphy1_out: endpoint@0 {
reg = <0>;
remote-endpoint = <&mipi2_csi2_input>;
};
};
};
};
&mipi2_csi2_hw {
status = "okay";
};
&mipi2_csi2 {
status = "okay";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
#address-cells = <1>;
#size-cells = <0>;
mipi2_csi2_input: endpoint@1 {
reg = <1>;
remote-endpoint = <&csi_dphy1_out>;
};
};
port@1 {
reg = <1>;
#address-cells = <1>;
#size-cells = <0>;
mipi2_csi2_output: endpoint@0 {
reg = <0>;
remote-endpoint = <&cif_mipi2_in0>;
};
};
};
};
&rkcif_mipi_lvds2 {
status = "okay";
firefly,yuv_camera;
port {
cif_mipi2_in0: endpoint {
remote-endpoint = <&mipi2_csi2_output>;
};
};
};
&rkcif_mipi_lvds2_sditf {
status = "disabled";
port {
mipi_lvds2_sditf: endpoint {
remote-endpoint = <&isp0_vir2>;
};
};
};
&rkisp0_vir2 {
status = "disabled";
port {
#address-cells = <1>;
#size-cells = <0>;
isp0_vir2: endpoint@0 {
reg = <0>;
remote-endpoint = <&mipi_lvds2_sditf>;
};
};
};
&gpio2 {
pinctrl-names = "default";
pinctrl-0 = <&mipidphy0_pwr>;
camera3-pwdn-set {
gpio-hog;
gpios = <19 GPIO_ACTIVE_HIGH>;
output-high;
};
};
&pinctrl {
cam {
mipidphy0_pwr: mipidphy1-pwr {
rockchip,pins =
/* camera power en */
<2 RK_PC3 RK_FUNC_GPIO &pcfg_pull_up>;
};
};
};
&rkcif {
status = "okay";
// memory-region = <&cif_reserved>;
};
&rkcif_mmu {
status = "okay";
};
&rkisp0 {
status = "disabled";
};
&isp0_mmu {
status = "disabled";
};
@aike 你现在i2c是通的，能识别到摄像头型号，对吗？
@aike
第一步，i2c要调通。上次你曾经调好过。
第二步，dts中关于mipi接口的节点连接关系要写对。你这个原理图是外设接插件的，并没有能表明最终接入到3588用的是哪几个接口。
如果这个板子本身有默认支持的camera，比如ov5640之类的，你可以 参考那个dts。
或者你把这个板子原生支持的摄像头的dts和你现在移植的VEYE模组的dts都发出来，我帮你看看。
@jihua 我们在rk平台没有遇到过这个问题。看ecc2这个错误提示的话，像是mipi信号劣化了。