Hi everyone,
I’m bringing up an 1 lane sensor connected via TI UB953/UB960 SerDes on a Jetson Orin , and I’m not getting any video output — even though the exact same setup and configuration works fine on Jetson Xavier Setup details
Sensor: 1 lane mipi sensor
Serializer: TI UB953
Deserializer: TI UB960
Connection: 1 CSI lane (YUYV 16-bit format)
Platform: Jetson Orin Jetpack 6.2
Same device tree and initialization sequence that worked on Xavier
Device tree snippet mode0 {
mclk = "extperiph1";
mclk_khz = "25000";
num_lanes = "1";
tegra_sinterface = "serial_g";
lane_polarity = "0";
discontinuous_clk = "no";
set_mode_delay_ms = "800";
dpcm_enable = "false";
cil_settletime = "0";
csi_pixel_bit_depth = "16";
pixel_phase = "yuyv";
active_w = "640";
active_h = "480";
readout_orientation = "0";
inherent_gain = "1";
serdes_pix_clk_hz = "50000000";
pix_clk_hz = "54000000";
embedded_metadata_height = "0";
vc_id = "0";
mode_type = "yuv";
};
i am getting “invalid frames“ error with debug trace. rtcpu_nvcsi_intr: … status:0x0a000000.
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, it appears that you are experiencing issues with bringing up a camera on a Jetson AGX Orin platform, specifically with a GMSL camera setup. Despite using the same setup and configuration that worked fine on a Jetson Xavier platform, you are not getting any video output on the Jetson AGX Orin.
Here are a few potential issues to consider:
Virtual Channel Configuration : The Jetson AGX Orin series supports a maximum of 16 virtual channels with ISP, or 24 virtual channels without ISP. Ensure that your virtual channel configuration is correct and matches the stream’s virtual channel ID programmed on the receiver side in the NVIDIA SoC.CSI Lane Configuration : The Jetson AGX Orin series has 4 CSI bricks, each with x4, x2, or x1 possible lane configurations. Verify that your CSI lane configuration is correct and matches the sensor’s output format (YUYV 16bit format in your case).Deserializer Connection : Ensure that the deserializer connection is correct, and the GMSL links are properly connected to the serializer and deserializer devices.Device Tree and Initialization Sequence : Although you mentioned that you are using the same device tree and initialization sequence that worked on Xavier, it’s possible that there are some differences in the device tree or initialization sequence that need to be accounted for on the Jetson AGX Orin platform.Debug Trace : The debug trace rtcpunvcsiintr: status 0x0a000000 indicates an invalid frame error. This could be related to a misconfiguration of the virtual channels, CSI lane configuration, or deserializer connection.
To troubleshoot the issue, you can try the following:
Verify the virtual channel configuration and ensure that it matches the stream’s virtual channel ID programmed on the receiver side in the NVIDIA SoC.
Check the CSI lane configuration and ensure that it matches the sensor’s output format (YUYV 16bit format in your case).
Verify the deserializer connection and ensure that the GMSL links are properly connected to the serializer and deserializer devices.
Review the device tree and initialization sequence to ensure that they are correct and account for any differences between the Jetson Xavier and Jetson AGX Orin platforms.
Use the debug trace to identify the source of the invalid frame error and adjust the configuration accordingly.
In comparison to the Jetson Xavier platform, the Jetson AGX Orin platform has some differences in terms of virtual channel configuration, CSI lane configuration, and deserializer connection. Therefore, it’s essential to ensure that the configuration is correct and accounts for these differences.
Additionally, you can refer to the provided context, which includes information on the Jetson Virtual Channel with GMSL Camera Framework, to ensure that your setup and configuration are correct.
If you are still experiencing issues, please provide more details about your setup and configuration, and I’ll be happy to help you troubleshoot the problem.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
i have already tried all the suggestions. how to identify source of invalid frame error?
HI @shivlal12345 ,
I hope you are doing well.
Can you please share the full dmesg output from a fresh boot up to where the camera streaming fails?
Also, can you try getting video output using the UB960’s internal test pattern generator ? This will help us identify whether the error is in the Deserializer/Jetson connection or on the sensor side.
Best regards,
Home Expertise & Work Our Expertise Case Studies Blog Pricing Contact Book NVIDIA Jetson Consultation Call Get Expert NVIDIA Jetson Support Book a free call now and get expert project consultation and a custom development plan within 2 business...
Est. reading time: 3 minutes
Get the trace log to check.
dmesg log.
[ 424.154076] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request tim ed out after 2500 ms
debug trace log.
cat /sys/kernel/debug/tracing/trace
kworker/5:2-369 [005] ....... 955.811752: rtcpu_string: tstamp:30761515997 id:0x04010000 str:"VM0 deactivating."
gst-launch-1.0-2461 [000] … 959.473607: tegra_channel_open: vi-output, ov5693 2-006d
kworker/5:2-369 [005] … 965.839455: rtcpu_nvcsi_intr: tstamp:31076082586 class:GLOBAL type:PHY_INTR0 phy:3 cil:0 st:0 vc:0 status:0x0a000000
Looks like deskew calibration issue.
Skew calibration is required if sensor or deserializer is using DPHY, and the output data rate is > 1.5Gbps.
An initiation deskew signal should be sent by sensor or deserializer to perform the skew calibration. If the deskew signals is not sent, the receiver will stall, and the capture will time out.
You can calculate the output data rate with the following equation:
Output data rate = (sensor or deserializer pixel clock in hertz) * (bits per pixel) / (number of CSI lanes)
is deskew calibration required for above configuration? how to configure it?
Modify the serdes_pix_clk_hz and pix_clk_hz to make the output data rate > 1.5
setting serdes_pix_clk_hz equal to pix_clk_hz worked. now i am getting video. how to calculate serdes_pix_clk_hz?
You can remove the serdes_pix_clk_hz but only use pix_clk_hz for Orin on your case.
system
November 18, 2025, 9:07am
16
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.