Jetson-35.6.2 AGX Orin 64G – HDMI not working

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Jetson-35.6.2 AGX Orin 64G – HDMI not working

绘图1
绘图11222×1781 161 KB

The SDK defaults to DP output, but our carrier board is wired for HDMI.
We have already applied the pinmux changes generated from Orin_Jetson_Series_Pinmux_Config_Template-v2.1.xlsm:

b/bootloader/t186ref/BCT/tegra234-mb1-bct-pinmux-p3701-0000-a04.dtsi
dp_aux_ch0_hpd_pm0 {
nvidia,pins = “dp_aux_ch0_hpd_pm0”;

  •           nvidia,function = "dp";  

  •           nvidia,function = "rsvd1";  
          nvidia,pull = <TEGRA_PIN_PULL_NONE>;  
          nvidia,tristate = <TEGRA_PIN_ENABLE>;  
          nvidia,enable-input = <TEGRA_PIN_ENABLE>;

/bootloader/tegra234-mb1-bct-gpio-p3701-0000-a04.dtsi
TEGRA234_MAIN_GPIO(Q, 6)
TEGRA234_MAIN_GPIO(Q, 7)
TEGRA234_MAIN_GPIO(R, 1)

  •           TEGRA234_MAIN_GPIO(M, 0)  
          TEGRA234_MAIN_GPIO(N, 4)  
          TEGRA234_MAIN_GPIO(N, 1)  
          TEGRA234_MAIN_GPIO(G, 0)

hardware/nvidia/platform/t23x/concord/kernel-dts/tegra234-p3701-0000-p3737-0000.dts
display@13800000 {
status = “okay”;
+ os_gpio_hotplug_a = <&tegra_main_gpio TEGRA234_MAIN_GPIO(M, 0) GPIO_ACTIVE_HIGH>;
};

However, i2cdetect -y 6 still shows:

root@tegra-ubuntu:~# i2cdetect -y 6
Warning: Can’t use SMBus Quick Write command, will skip some addresses
0 1 2 3 4 5 6 7 8 9 a b c d e f
00:
10:
20:
30: [ 1194.266632] tegra-i2c 31c0000.i2c: I2C transfer timed out
– [ 1194.374857] tegra-i2c 31c0000.i2c: I2C transfer timed out
– [ 1194.482853] tegra-i2c 31c0000.i2c: I2C transfer timed out
– [ 1194.590840] tegra-i2c 31c0000.i2c: I2C transfer timed out
– [ 1194.698848] tegra-i2c 31c0000.i2c: I2C transfer timed out

and /sys/kernel/debug/pinctrl/2430000.pinmux/pinmux-pins does not contain
DP2_AUX_CH_P → I2C6_CLK
DP2_AUX_CH_N → I2C6_DAT

How can I further verify and fix this issue?

5

We smt 3 pieces PCBA, 1# PCBA is with AGX module, 2# PCBA is without AGX module. 1# and 2# plug in HDMI display, Q3400 PIN3 goes high, pull out HDMI display, Q3400 PIN3 goes low. 1# Q3406 PIN3 hardware to GND, Q3406 PIN2 is 2.8V, Q3406 PIN3 hardware to VDD_3V3_HDMI, Q3406 PIN2 is also 2.8V. 2# Q3406 PIN3 hardware to GND, Q3406 PIN2 is low, Q3406 PIN3 hardware to VDD_3V3_HDMI, Q3406 PIN2 is high. 2# PCBA Q3403/Q3404 PIN3 hardware to GND/VDD_5V0_HDMI_CON, Q3403/Q3404 PIN2 is low/high.

LD630 HDMI P34.pdf (210.1 KB)

LD630 HDMI P5.pdf (103.1 KB)

6

boot_log_20251114.txt (132.7 KB)

7

please refer to

8

Still no job. Regarding the HDMI peripheral circuit, it has also been confirmed. And PM.00 → gpio424 can detect the HDMI insertion status. Insertion is 1, and removal is 0.

dp2i2c
dp2i2c1582×187 13.3 KB

dp2hdmi
dp2hdmi1781×262 21.2 KB

Moreover, I have another question: Why is there no change when using Orin_Jetson_Series_Pinmux_Config_Template-v2.1.xlsm to convert the DP signal into HDMI and generate Orin-jetson_agx_orin-pinmux.dtsi,Orin-jetson_agx_orin-gpio-default.dtsi?

9

those pinmux does not need to change. Only the pinmux for hpd change is needed.

Above link already includes everything you need.

If something does not work, you need to make sure doing full reflash instead of partial update.

10

I re-deployed the SDK and executed the command “sudo ./flash.sh jetson-agx-orin-devkit internal” multiple times, and confirmed that the updates to the kernel dts and the dtsi-related entries in the bootloader were effective.

  1. hdmi power PN.02 output high
  2. Change the model description to tegra234-p3701-0005-p3737-000
    Both of these changes are in effect, so the other changes should also be in effect.

Are there any other methods for troubleshooting the problem?

DP2_AUX_CH_P ->I2C6_CLK
DP2_AUX_CH_N ->I2C_DAT

If DP2_AUX_CH cannot be reconfigured to use i2c6, how can HDMI achieve communication? Because our baseboard is directly connected to the HDMI screen.

11

If the above DP function cannot be reused, I would like to know how HDMI communication is achieved under the default configuration. Are there any related explanations or what kind of mechanism is it?

12

It is more like the driver would do the conversion for you and you don’t need to change these by yourself manually.

Just to clarify. This thing has been applied multiple times before this topic by other users.

The only thing that could lead to problem here are

  1. Not apply items correctly.
  2. the applied items didn’t get flashed to the board correctly.
  3. hardware design is not expected.
13

Thank you for clearly defining my question.

15

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.