Jetson AGX Orin Hdmi not working

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

Hi,
We designed own carrier board but hdmi not working with Jetson AGX Orin.
Our hardware design tested with Jetson AGX Xavier.

Here Our pinmux:
Orin-pinmux.txt (65.8 KB)
Orin-gpio-default.txt (3.1 KB)

We enabled hdmi hot plug gpios with the line below in device-tree :

→ os_gpio_hotplug_a = <0x4 0x60 0x1>;

There are two diffirent situations ;

First device-tree display configurations is here:

########## Tegra DCB BLOB ###############
########### Display Devices #############
Display Devices::
Display Devices : [0]
Type : [DP]
CCB : [0]
Heads : 0:[Y] 1:[Y]
Sor : [0 ]
DP Lane Count : [4]
DP Link Rate : [8.1GHz]
Connector : [0]
Bus : [0]
Display Devices : [1]
Type : [TMDS]
CCB : [0]
Heads : 0:[Y] 1:[Y]
Sor : [0 ]
HDMI capable : [1]
Connector : [0]
Bus : [0]
############### CCB Entries ###############
CCB::
*CCB entries that have both I2C and AUX ports unused (value = 31) are not displayed
CCB Index : 0
I2C Port : [6]
AUX Port : [0]
########### Connector entries #############
Connectors::
Connector Index : 0x0
Type : [DP]
Hotplug : A:[Y]
Connector Index : 0x0
Type : [DP]
Hotplug : A:[Y]

When using this tegra234-dcb-p3701-0000-a2-p3737-0000-a01.dtsi file hdmi is working but xrand command says SCREEN 0 DP-1 connected. How is this possible?

Second device-tree display configurations is here:

########## Tegra DCB BLOB ###############
########### Display Devices #############
Display Devices::
Display Devices : [0]
Type : [TMDS]
CCB : [0]
Heads : 0:[Y] 1:[Y]
Sor : [0 ]
HDMI capable : [1]
Connector : [0]
Bus : [0]
############### CCB Entries ###############
CCB::
*CCB entries that have both I2C and AUX ports unused (value = 31) are not displayed
CCB Index : 0
I2C Port : [6]
AUX Port : [0]
########### Connector entries #############
Connectors::
Connector Index : 0x0
Type : [HDMI]
Hotplug : A:[Y]

When using this tegra234-dcb-p3701-0000-a2-p3737-0000-a01.dtsi file and plugged ACER SA270 monitor, monitor says “Input not Suported” and hdmi is not working, Dmesg and Xorg log here :
ACER_DMESG.txt (68.1 KB)
ACER_XORG.txt (13.0 KB)

When plugged LG monitor says “Out of Range” then display HDMI and xrand command says SCREEN 0 Hdmi connected. Dmesg and Xorg log here :
LG_DMESG.txt (68.2 KB)
LG_XORG.txt (13.1 KB)

Why does it work on one monitor but not the other?
How to solve this problem? We want to hdmi work all monitors and xrand command shows HDMI connected.

4

Which Jetpack release are you using? We don’t have any file called "“tegra234-dcb-p3701-0000-a2-p3737-0000-a01.dts”. What is that?

5

Jetpack version is JetPack 5.1.2. Sorry, correct file name is “tegra234-dcb-p3701-0000-a02-p3737-0000-a01.dtsi”.

6

please make sure the dcb you are using for HDMI mode is a totally copy from ./nvidia/platform/t23x/p3768/kernel-dts/tegra234-dcb-p3767-0000-hdmi.dtsi.

I mean its content.

7

We totally copy from “tegra234-dcb-p3767-0000-hdmi.dtsi.” and reflashed module.
Monitor displayJETSON UEFI setting(Boot Menu) and than starting boot.
While display booting log messages , corrupt the screen and writing “Input not Supported” like around 11.-12. seconds.
Boot and Xorg log here:
Xorg_log.txt (19.5 KB)
Boot_log.txt (69.9 KB)

8

What is the result of xrandr when you run this?

BTW, I am not sure why your xorg log format looks almost hardly reading. It seems not a common format we have from default BSP. Did you configure anything by yourself there?

9

Also, if possible, move to use rel-35.6 instead of rel-35.4.1.

If better, directly moving to rel-36. Rel-35 won’t have significant display fix anymore.

10

xrandr result like that :

@tegra-ubuntu:~$ xrandr
Can’t open display

Also after run "export DISPLAY=:0” command, xrandr result like that :

@tegra-ubuntu:~$ xrandr
No protocol specified
Can’t open display :0

Yes , we changed something in device tree. Used device tree file is below here:
tegra234-p3701-0004-p3737-0000.txt (575.2 KB)

Okay , understood.

11

Please try to make your xorg log back to normal situation that is more readable first.

13

Hi,
More readable version Xorg log is :
Xorg.0.log.txt (13.8 KB)

I have checked “Jetson_AGX_Orin_Series_Pinmux_Config_Template_1.9” pinmux file. I noticed display nets are named DP++ . In my opinion, it should be work compatible with HDMI without any changes to the device tree. Is this right ?

14

You could follow the HDMI version as Orin NX pinmux did. It could be just minor software change.

15

[ 26.816] (–) NVIDIA(GPU-0): Acer SA270 (DFP-0): connected
[ 26.816] (–) NVIDIA(GPU-0): Acer SA270 (DFP-0): Internal TMDS
[ 26.816] (–) NVIDIA(GPU-0): Acer SA270 (DFP-0): 600.0 MHz maximum pixel clock
[ 26.816] (–) NVIDIA(GPU-0):

I saw HDMI is detected here. Thus, not sure if this is picky monitor or due to your hardware.

Ideally, you could use NV devkit to validate. Orin NX + xavier nx devkit carrier board is the only devkit you could use to validate HDMI monitors.

17

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