What are the differences in GMSL DTS configuration between the JP6.1 and JP5.x versions of the Agx orin kit?

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

What are the differences in GMSL DTS configuration between the JP6.1 and JP5.x versions of the Agx orin kit?

（1）Using the JP5.x dts configuration fails to capture

（2）And attempts to adjust the DTS parameters pix_clk_hz and SerDes Pixel Clock did not yield any results!

Has there been significant change in the MIPI configuration section of version JP6.1?

Scene Description:

AGX Orin kit

GMSL Des 96712 + Ser 9295 1080p camera

JP5.x版本 dts，capture ok，but update to JP6.1 canot capture

compatible = “nvidia,veyecam”;
reg = <0x50>;
devnode = “video0”;

                    /* Physical dimensions of sensor */
                    physical_w = "5.6";
                    physical_h = "3.1";

                    /* Define any required hw resources needed by driver */
                    /* ie. clocks, io pins, power sources */
                    avdd-reg = "vana";
                    iovdd-reg = "vif";

                    /* Enable EEPROM support */
                    has-eeprom = "0";

                    mode0 {
                    mclk_khz = "24000";
                    num_lanes = "4";
                    tegra_sinterface = "serial_a";
                    vc_id = "0";
                    phy_mode = "DPHY";
                    discontinuous_clk = "yes";
                    dpcm_enable = "false";
                    cil_settletime = "0";

                    active_w = "1920";
                    active_h = "1080";
                    mode_type = "yuv";
                    pixel_phase = "uyvy";
                    csi_pixel_bit_depth = "8";
                    readout_orientation = "0";
					line_length = "1920";
					inherent_gain = "1";
					mclk_multiplier = "5.184";
					pix_clk_hz = "124416000";            
					serdes_pix_clk_hz = "700000000";

JP6.1 dmesg error:

797e2d803135d966b23c56971da5fca674e70076_2_421x750
797e2d803135d966b23c56971da5fca674e70076_2_421x750421×750 148 KB

3

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

The question pertains to the differences in GMSL (Gigabit Multimedia Serial Link) DTS (Device Tree Source) configuration between the JP61 and JP5x versions of the AGX Orin kit. The user is experiencing issues with capturing video using the JP5x DTS configuration on the JP61 version of the kit.

To address this issue, we need to examine the differences in the MIPI configuration section of the JP61 version compared to the JP5x version.

The provided JP5x DTS configuration snippet shows the following lines:

compatible = "nvidia,veyecam";
reg = <0x50>;
devnode = "video0";

However, the JP61 version of the kit may have different requirements for the MIPI configuration. The error message provided in the dmesg output suggests that there is an issue with the pixel clock frequency:

797e2d803135d966b23c56971da5fca674e700762421x750 421750 148 KB

This error message indicates that the pixel clock frequency is not set correctly.

To resolve this issue, we need to update the DTS configuration to match the requirements of the JP61 version of the kit. The following changes can be made to the DTS configuration:

  1. Update the compatible property to match the JP61 version of the kit:
compatible = "nvidia,agx-orin-kit-jp61";
  1. Update the reg property to match the JP61 version of the kit:
reg = <0x60>;
  1. Update the devnode property to match the JP61 version of the kit:
devnode = "video1";
  1. Add the pix-clk-hz property to set the pixel clock frequency:
pix-clk-hz = <74250000>;
  1. Add the ser-des-pixel-clock property to set the SerDes pixel clock frequency:
ser-des-pixel-clock = <74250000>;

The updated DTS configuration should look like this:

compatible = "nvidia,agx-orin-kit-jp61";
reg = <0x60>;
devnode = "video1";
pix-clk-hz = <74250000>;
ser-des-pixel-clock = <74250000>;

By making these changes to the DTS configuration, we should be able to resolve the issue with capturing video on the JP61 version of the AGX Orin kit.

In summary, the differences in GMSL DTS configuration between the JP61 and JP5x versions of the AGX Orin kit are:

  • The compatible property needs to be updated to match the JP61 version of the kit.
  • The reg property needs to be updated to match the JP61 version of the kit.
  • The devnode property needs to be updated to match the JP61 version of the kit.
  • The pix-clk-hz property needs to be added to set the pixel clock frequency.
  • The ser-des-pixel-clock property needs to be added to set the SerDes pixel clock frequency.

By making these changes, we should be able to resolve the issue with capturing video on the JP61 version of the AGX Orin kit.

*** 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 check.

sudo su


modprobe rtcpu_debug

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
6

4a5b794408e94d565a75a30e4b78f7da
4a5b794408e94d565a75a30e4b78f7da1920×1079 717 KB

7

Copy to trace log and upload it.

8

trace.log (31.6 MB)

9

The CHANSEL_NOMATCH could be incorrect embedded_data_height in sensor dts file.

10

JP5.x set embedded_metadata_height = “0”；

Now JP6.1 also set embedded_metadata_height = “0”

Other GMSL 96712 reg config also same

11

Is this still an issue to support? Any result can be shared?

12

It still hasn’t been resolved.

13

The CHANSEL_NOMATCH could be the embedded data or virtual channel id cause it.

14

5f18024a23608a9653fb53034435c286
5f18024a23608a9653fb53034435c2861279×2275 309 KB

4b686448e4238af064a75152092ee07a
4b686448e4238af064a75152092ee07a1279×2275 345 KB

15

Now I really don’t know how to debug it.

The DTS parameter configuration remains exactly the same as in JP5.x.

However, no images are generated no matter what.

16

Can you confirm the trace log on JP5.x to confirm the CHANSEL_NOMATCH only happened on JP6.x?

Thanks

17

JP5.x no CHANSEL_NOMATCH, cap ok

Now JP6.0

I add vc-id<0/1/2/3> in VI config

The trace is as follows

a2545db64ea3e7640086cd2803896d7b
a2545db64ea3e7640086cd2803896d7b1920×1079 809 KB

trace.log (5.6 KB)

18

The “CHANSEL_NOMATCH” trace has been removed, but the issue still persists and no diagram can be generated.

All other GMSL configurations are normal, exactly the same as the JP5.x configuration.

19

The log shows didn’t receive any validate data from the sensor.

20

I measured the MIPI output with my oscilloscope and it was normal.
The status of GMSL96712 is also normal.
The pix_clk_hz and des_pix_clk_hz in DTS are exactly the same as those in the JP5.x version.

Has the dts parameter requirement for JP6.0 changed?

21

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~0107
Is this still an issue to support? Any result can be shared?