Camera error

JP6.2.0 Jetson-agx-orin

MAX9265+MAX96712

在使用v4l2-ctl验证时,取不到数据,

这是为什么喃 我的相机是D457 d4m0_d: d4m0_d@1d {
compatible = “intel,d4xx”;
status = “ok”;
def-addr = <0x1a>;
reg = <0x1d>;
cam-type = “IMU”;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
d4xx_cam_out3: endpoint {
vc-id = “3”;
port-index = <0>;
bus-width = <2>;
remote-endpoint = <&d4xx_csi_in3>;
};
};
};

			mode0 { /*D4xx IMU */
				phy_mode = "DPHY";
				discontinuous_clk = "yes";
				dpcm_enable = "false";
				cil_settletime = "0";
				pixel_t = "grey_y16";
				num_lanes = "2";
				csi_pixel_bit_depth = "16";
				active_w = "640";
				active_h = "480";
				tegra_sinterface = "serial_a";
				mclk_khz = "24000";
				pix_clk_hz = "74250000";
				serdes_pix_clk_hz = "375000000";
				line_length = "1280"; /* 2200 */
				embedded_metadata_height = "0";
				vc_id = "3";
			};
		};

*** Please note that this reply is generated by LLM automatically ***

The provided information appears to be a collection of documentation pages from the Jetson Linux Developer Guide, specifically related to the Jetson AGX Orin module.

The Jetson AGX Orin is a high-performance module from NVIDIA, designed for AI, robotics, and other applications that require intense computational power. The module is based on the NVIDIA Ampere architecture and features a powerful GPU, CPU, and other peripherals.

The provided text snippet seems to be related to the camera interface configuration on the Jetson AGX Orin module. Specifically, it appears to be a configuration file or a dump of the camera interface settings.

Here’s a breakdown of the information:

  • The first line mentions the Jetson AGX Orin JP620 module and some other components, including the MAX9265 and MAX96712, which are likely camera interface chips.
  • The v4l2ctl command is used to configure and control the camera interface.
  • The following lines appear to be a dump of the camera interface settings, including the device tree configuration and the camera module information.
  • The compatible property is set to inteld4xx, indicating that the camera module is compatible with the Intel D4xx camera interface.
  • The status property is set to ok, indicating that the camera module is functioning correctly.
  • The defaddr property is set to lt0x1agt, which is likely the default address of the camera module.
  • The reg property is set to lt0x1dgt, which is likely the register address of the camera module.
  • The camtype property is set to IMU, indicating that the camera module is an Inertial Measurement Unit (IMU) camera.
  • The ports property is set to addresscells lt1gt sizecells lt0gt, which is likely the port configuration of the camera module.
  • The port0 property is set to reg lt0gt, which is likely the register address of the camera module’s port 0.
  • The d4xxcamout3 property is set to endpoint vcid 3, which is likely the endpoint configuration of the camera module’s output 3.
  • The portindex property is set to lt0gt, which is likely the port index of the camera module.
  • The buswidth property is set to lt2gt, which is likely the bus width of the camera module.
  • The remoteendpoint property is set to ltampd4xxcsiin3gt, which is likely the remote endpoint configuration of the camera module’s input 3.

In comparison to other Jetson modules, the Jetson AGX Orin has a more advanced camera interface configuration, with support for multiple camera modules and more complex configuration options. However, the specific configuration options and settings may vary depending on the specific use case and application.

It’s worth noting that the provided information is likely specific to the Jetson AGX Orin module and may not be applicable to other Jetson modules or devices. Additionally, the information provided is likely a subset of the full configuration and settings for the camera interface, and may not be comprehensive or up-to-date.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

你这个答案好像并没什么用

hello 1725941956,

please aware this is not supported by default, you’ll need to work on driver development to extend supports.

besides.. there’s CHANSEL_FAULT according to VI tracing logs.
it usually due to the device tree settings has mismatch with actual coming signaling.

else if (strncmp(pixel_t, "yuv_vyuy16", size) == 0)
	*format = V4L2_PIX_FMT_VYUY;
  • else if (strncmp(pixel_t, “grey_y8”, size) == 0)
  •   *format = V4L2_PIX_FMT_GREY;
    
  • else if (strncmp(pixel_t, “grey_y16”, size) == 0)
  •   *format = V4L2_PIX_FMT_Y16;我有增加