Jetson VI Timeout with Custom FPGA CSI-2 Camera

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

Hi

Setup Details:

Platform: NVIDIA Jetson Orin Nx
Source: Custom FPGA (acting as CSI-2 camera sensor)
Resolution: 640 × 480
Pixel Format: RGB565
Frame Rate: 10 FPS
Number of Lanes: 1
pix_clk_hz: 38.8 MHz
Issue:

I am integrating a custom FPGA-based CSI-2 camera with Jetson and am facing the following capture timeout error:

image
image1177×381 6.58 KB

Dmesg logs:

image
image747×307 8.07 KB

I have also enabled and analyzed rtcpu_debug traces, but I was not able to find any clear clue pointing to the root cause.

I have also verified the FPGA CSI-2 output using a MIPI analyzer, and the analyzer shows proper CSI-2 waveforms and packet transmission.

Has anyone encountered a similar issue with a custom FPGA CSI-2 source? If so, could you please share how you resolved it?

It would also be helpful to know if the root cause was related to the driver, DTS configuration, CSI-2 packet generation, timing issues, Jetson-side settings, or any specific debugging method that helped identify and resolve the issue.

Thanks in advance for any suggestions.

3

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

To address the issue of a capture timeout error with a custom FPGA-based CSI2 camera sensor on the Jetson Orin NX platform, we need to consider several factors, including the driver, DTS configuration, CSI2 packet generation, timing issues, and Jetson-side settings.

Driver and DTS Configuration:

  1. Ensure that the CSI2 driver is properly configured and enabled in the device tree source (DTS) file. The DTS file should include the CSI2 controller and the FPGA-based camera sensor as a child node.
  2. Verify that the CSI2 driver is correctly configured to handle the custom FPGA-based camera sensor. This may involve modifying the driver to accommodate the specific requirements of the FPGA-based camera sensor.

CSI2 Packet Generation:

  1. Verify that the FPGA-based camera sensor is generating CSI2 packets correctly. This includes ensuring that the packet format, timing, and data integrity are correct.
  2. Use a MIPI analyzer to verify that the CSI2 packets are being transmitted correctly. As you have already done this, it is likely that the issue is not with the FPGA-based camera sensor.

Timing Issues:

  1. Verify that the CSI2 clock and data signals are properly synchronized. This includes ensuring that the clock signal is stable and that the data signals are properly aligned with the clock signal.
  2. Check the timing of the CSI2 packets to ensure that they are being transmitted within the required time frame.

Jetson-side Settings:

  1. Verify that the Jetson Orin NX platform is properly configured to handle the CSI2 camera sensor. This includes ensuring that the CSI2 controller is enabled and that the camera sensor is properly configured.
  2. Check the Jetson Orin NX platform’s settings to ensure that they are compatible with the custom FPGA-based camera sensor.

Debugging Methods:

  1. Use the rtcpudebug traces to analyze the CSI2 packet transmission and reception. This can help identify any issues with the CSI2 packet transmission or reception.
  2. Use a logic analyzer to analyze the CSI2 clock and data signals. This can help identify any timing issues or signal integrity problems.
  3. Use a camera sensor debugging tool, such as the v4l2-ctl command, to analyze the camera sensor’s settings and configuration.

Comparison with Similar Issues:

There are several similar issues reported on the Jetson forums and other online platforms. For example, some users have reported issues with the CSI2 camera sensor on the Jetson TX2 platform, which were resolved by modifying the DTS file and the CSI2 driver.

In another case, a user reported an issue with the CSI2 camera sensor on the Jetson Xavier NX platform, which was resolved by adjusting the CSI2 clock and data signal timing.

Conclusion:

The capture timeout error with the custom FPGA-based CSI2 camera sensor on the Jetson Orin NX platform is likely due to a combination of factors, including the driver, DTS configuration, CSI2 packet generation, timing issues, and Jetson-side settings.

To resolve the issue, it is recommended to:

  1. Verify the CSI2 driver and DTS configuration.
  2. Analyze the CSI2 packet transmission and reception using rtcpudebug traces.
  3. Check the timing of the CSI2 packets and adjust the clock and data signal timing as needed.
  4. Use a logic analyzer to analyze the CSI2 clock and data signals.
  5. Use a camera sensor debugging tool to analyze the camera sensor’s settings and configuration.

By following these steps, it should be possible to identify and resolve the root cause of the capture timeout error.

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

5

Get the trace log to analysis the problem.

sudo su
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 3 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace

v4l2-ctl --stream-mmap -c bypass_mode=0

cat /sys/kernel/debug/tracing/trace