# Jetson AGX Orin Hdmi not working **URL:** \ **Category:** Jetson AGX Orin\ **Tags:** hdmi, board-design\ **Created:** [February 7, 2025, 1:07pm UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937 "2025-02-07T13:07:22Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![s.innn](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@s.innn](https://forums.developer.nvidia.com/u/s.innn)\ **Post date:** [February 7, 2025, 1:07pm UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/1 "2025-02-07T13:07:22Z")
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](https://forums.developer.nvidia.com/uploads/short-url/AiCoCLNtfDrhMIDYKjsEl7DXxa0.txt) (65.8 KB) [Orin-gpio-default.txt](https://forums.developer.nvidia.com/uploads/short-url/upNh9CxsTYyM86p094puFIzxASU.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](https://forums.developer.nvidia.com/uploads/short-url/zOCRZWN2JnGj4YuT0DCJpkbd1xt.txt) (68.1 KB) [ACER\_XORG.txt](https://forums.developer.nvidia.com/uploads/short-url/9u86JlJ7HZv8Rv1hFdTbQ6jzXPd.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](https://forums.developer.nvidia.com/uploads/short-url/eIivFxH0NbMip6KkkZKpjuJ9V2v.txt) (68.2 KB) [LG\_XORG.txt](https://forums.developer.nvidia.com/uploads/short-url/8QbTuR2XJLmBwy2sz90AhkEmgs1.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. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [February 10, 2025, 2:42am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/4 "2025-02-10T02:42:08Z")
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? ---
**Author:** ![s.innn](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@s.innn](https://forums.developer.nvidia.com/u/s.innn)\ **Post date:** [February 10, 2025, 7:48am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/5 "2025-02-10T07:48:20Z")
Jetpack version is JetPack 5.1.2. Sorry, correct file name is “tegra234-dcb-p3701-0000-a02-p3737-0000-a01.dtsi”. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [February 10, 2025, 8:11am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/6 "2025-02-10T08:11:26Z")
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. ---
**Author:** ![s.innn](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@s.innn](https://forums.developer.nvidia.com/u/s.innn)\ **Post date:** [February 10, 2025, 3:43pm UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/7 "2025-02-10T15:43:08Z")
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](https://forums.developer.nvidia.com/uploads/short-url/4YhJ5N236vpULzm69PksuOeogpA.txt) (19.5 KB) [Boot\_log.txt](https://forums.developer.nvidia.com/uploads/short-url/4GZJvSI3FwW2dOSSOx4Eb5Lcjtp.txt) (69.9 KB) ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [February 10, 2025, 3:48pm UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/8 "2025-02-10T15:48:37Z")
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? ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [February 10, 2025, 3:54pm UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/9 "2025-02-10T15:54:17Z")
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. ---
**Author:** ![s.innn](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@s.innn](https://forums.developer.nvidia.com/u/s.innn)\ **Post date:** [February 11, 2025, 7:03am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/10 "2025-02-11T07:03:20Z")
> [@WayneWWW](#): > > 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? 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](https://forums.developer.nvidia.com/uploads/short-url/scATnNX7EklzwzeJahyGtJlLYGG.txt) (575.2 KB) > [@WayneWWW](#): > > 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. Okay , understood. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [February 11, 2025, 7:30am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/11 "2025-02-11T07:30:09Z")
Please try to make your xorg log back to normal situation that is more readable first. ---
**Author:** ![s.innn](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@s.innn](https://forums.developer.nvidia.com/u/s.innn)\ **Post date:** [February 11, 2025, 11:05am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/13 "2025-02-11T11:05:11Z")
Hi, More readable version Xorg log is : [Xorg.0.log.txt](https://forums.developer.nvidia.com/uploads/short-url/oAK6rygrn4mlNQsrHeh1Mtmzk8S.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 ? ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [February 11, 2025, 11:07am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/14 "2025-02-11T11:07:02Z")
You could follow the HDMI version as Orin NX pinmux did. It could be just minor software change. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [February 11, 2025, 11:08am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/15 "2025-02-11T11:08:55Z")
> [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. ---
**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\ **Post date:** [March 12, 2025, 5:51am UTC](https://forums.developer.nvidia.com/t/jetson-agx-orin-hdmi-not-working/322937/17 "2025-03-12T05:51:03Z")
Closed on March 12, 2025, 5:51am UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.