# Hdmi 1.0 related queries **URL:** \ **Category:** Jetson TX2\ **Created:** [November 4, 2019, 4:36am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294 "2019-11-04T04:36:31Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![shrinathchoudhary](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shrinathchoudhary](https://forums.developer.nvidia.com/u/shrinathchoudhary)\ **Post date:** [November 4, 2019, 4:36am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/1 "2019-11-04T04:36:31Z")
my tx2 dev kit has hdmi 2.0 but my custom carrier card has hdmi 1.4 output. im getting display in devkit but not on my custom carrier card. in both case same software is used(jetpack 3.3 rel 28.2.1). im getting edid data from monitor but nothing is displayed on monitor. do we have to change anything in software so that it support hdmi 1.4 as well ?? thank you ! ---
**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:** [November 4, 2019, 6:46am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/2 "2019-11-04T06:46:18Z")
Please try to dump the boot log and xorg log. [https://elinux.org/Jetson\_TX2/r28\_Display\_debug](https://elinux.org/Jetson_TX2/r28_Display_debug) ---
**Author:** ![shrinathchoudhary](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shrinathchoudhary](https://forums.developer.nvidia.com/u/shrinathchoudhary)\ **Post date:** [November 4, 2019, 9:28am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/3 "2019-11-04T09:28:48Z")
please find the attached logs for jetson\_tx2\_devkit & jetson tx2i custom carrier card please note edid data is different in both cases while the same monitor being used. and there is no x11 directory to capture xorg.conf log in both cases. [custom\_carrier\_hdmi.txt](https://forums.developer.nvidia.com/uploads/short-url/7lRyJE82t52gtZjfV5pYYYje5Je.txt) (86.1 KB) [jetson\_devkit\_hdmi.txt](https://forums.developer.nvidia.com/uploads/short-url/rf5Z2Rslz1OIIKnF2Ph4ZEK8y4y.txt) (380 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:** [November 4, 2019, 9:46am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/4 "2019-11-04T09:46:05Z")
Yes, the edid is different because it fails to read edid from your monitor when using your carrier board. What is the hardware difference between your board and devkit in this part? ```auto [4.498614] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.502714] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.506816] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.510909] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.515027] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.519125] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.523234] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.527317] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.531441] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.535537] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.539631] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.543726] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.547821] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.551913] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.556023] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.560119] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.564213] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.568330] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.572434] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.576532] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.580630] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.584738] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.588833] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.592928] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.597019] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.601115] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.605215] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.609316] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.613416] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.617517] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.621622] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.625717] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.629814] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.633910] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.638001] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.642099] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.646214] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.650345] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.654446] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.658560] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.662677] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.666779] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.670904] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.674977] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.679086] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.683176] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.687275] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.691371] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.695481] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.699575] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.703670] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.707759] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.711859] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.715962] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.720063] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.724155] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.728252] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.732352] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.736448] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.740543] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.744647] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.748743] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.752838] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.756949] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.761046] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.765140] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.769237] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.773336] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.777432] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.781529] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.785635] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.789736] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.793831] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.793923] random: nonblocking pool is initialized [4.797928] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.802032] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.806127] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.810312] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.814383] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.818447] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.822544] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.826657] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.830763] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.834872] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.838965] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.843057] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.847164] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.851261] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.855353] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.859462] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.863555] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.867647] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.871743] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.875834] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.879926] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.884024] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.888124] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.892233] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.896343] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.900441] tegra-i2c 3190000.i2c: no acknowledge from address 0x50 [4.901103] tegradc 15210000.nvdisplay: hdmi: edid read failed [4.901159] tegradc 15210000.nvdisplay: hdmi: using fallback edid ``` ---
**Author:** ![shrinathchoudhary](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shrinathchoudhary](https://forums.developer.nvidia.com/u/shrinathchoudhary)\ **Post date:** [November 4, 2019, 10:11am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/5 "2019-11-04T10:11:26Z")
hardware wise, differences are that we are using **ESD protection IC with part no - tpd12s521** & **hdmi 1.4 port** is used in custom carrier card. please find the attached schematic. ```auto [4.901103] tegradc 15210000.nvdisplay: hdmi: edid read failed [4.901159] tegradc 15210000.nvdisplay: hdmi: using fallback edid ``` **can I update default edid in source to the edid data im getting on devkit ?? if yes how can i update please let me know !!** thank you !! ![HDMI.JPG](https://global.discourse-cdn.com/nvidia/original/2X/c/c25866535e48d3433a76ac0b440fce53cf6cd532.jpeg) ![HDMI.JPG](https://global.discourse-cdn.com/nvidia/original/2X/c/c25866535e48d3433a76ac0b440fce53cf6cd532.jpeg) ---
**Author:** ![Trumany](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/trumany/32/14043_2.png) [@Trumany](https://forums.developer.nvidia.com/u/Trumany)\ **Post date:** [November 5, 2019, 3:14am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/6 "2019-11-05T03:14:59Z")
It looks like no level shift on DDC and HPD lines, please refer to OEM DG and dev kit reference schematic in [DLC](https://developer.nvidia.com/embedded/downloads) to make design. ---
**Author:** ![shrinathchoudhary](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shrinathchoudhary](https://forums.developer.nvidia.com/u/shrinathchoudhary)\ **Post date:** [November 5, 2019, 5:33am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/7 "2019-11-05T05:33:29Z")
Hi, tpd12s521 will work as ESD as well as level shifter also. please note we are getting proper edid,hdmi-0 configuration in xorg.log,tegradc log in dmesg log after doing rework on i2c lane. which are same as devkit now logs are exactly same as devkit log. hardware design is also same only difference is that we have hdmi 1.4 where as on Devkit it is hdmi 2.0 is there any way to downgrade from 2.0 to 1.4 from software side ??? ---
**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:** [November 5, 2019, 5:45am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/8 "2019-11-05T05:45:40Z")
hdmi 2.0 driver is compatible with hdmi1.4. I don’t get the point here to do the downgrade. ---
**Author:** ![shrinathchoudhary](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shrinathchoudhary](https://forums.developer.nvidia.com/u/shrinathchoudhary)\ **Post date:** [November 7, 2019, 9:01am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/9 "2019-11-07T09:01:43Z")
okey thanks for the information… whenever i connect or disconnect hdmi cable, hdmi hot-plug status is not toggling. ```auto cat /sys/kernel/debug/tegra_hdmi/hotplug ``` do u have any idea about this issue ?? ---
**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:** [November 7, 2019, 9:15am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/10 "2019-11-07T09:15:48Z")
1. According to previous discussion, your hardware design does not match our OEM design guide. Could you confirm that first? 2. Also, what does that mean you have a hdmi1.4 port here? Sorry in advanced I am not a hardware guy, so need some explanations. 3. Even on devkit, the node “/sys/kernel/debug/tegra\_hdmi/hotplug” seems not give the hpd state. Thus, to debug your issue from sw, I think dumping dmesg should be sufficient. Hotplug should trigger the driver to print log in dmesg. If it does not print, then I would think it is a hardware issue. ---
**Author:** ![shrinathchoudhary](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shrinathchoudhary](https://forums.developer.nvidia.com/u/shrinathchoudhary)\ **Post date:** [November 7, 2019, 11:50am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/11 "2019-11-07T11:50:27Z")
1. we have followed OEM design guide, attached schematic. 2. hdmi 1.4 port means, in our design the hdmi lines coming out from tx2i module are connected to hdmi 1.4 connector port while in case of devkit those lines are connected to hdmi 2.0 connector port. 3. we tested the hot-plug detection status from “/sys/kernel/debug/tegra\_hdmi/hotplug” on devkit by removing and connecting the hdmi cable & we observed the toggling of states while on our carrier card this behavior not observed. Please find logs. [tx2i\_carrier\_card.txt](https://forums.developer.nvidia.com/uploads/short-url/hWYVzOU12t1SUKAsR9wbgj5HiJt.txt) (67.4 KB) [jetson\_tx2\_devkit.txt](https://forums.developer.nvidia.com/uploads/short-url/azkcH44YtkvL50lRuioxRh1eJpA.txt) (83.2 KB) ![HDMI.JPG](https://global.discourse-cdn.com/nvidia/original/2X/c/c25866535e48d3433a76ac0b440fce53cf6cd532.jpeg) ---
**Author:** ![Trumany](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/trumany/32/14043_2.png) [@Trumany](https://forums.developer.nvidia.com/u/Trumany)\ **Post date:** [November 8, 2019, 2:34am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/12 "2019-11-08T02:34:20Z")
Did you measure the HPD signal close to HDMI connector? Is there a level change on it? If you can see the level change, is it same high/low to devkit? If not, you need to change the value of hotplug detection in dts. Also I don’t see the Rpd and beads to ground on data lines in your schematic. ---
**Author:** ![shrinathchoudhary](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@shrinathchoudhary](https://forums.developer.nvidia.com/u/shrinathchoudhary)\ **Post date:** [November 8, 2019, 9:51am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/13 "2019-11-08T09:51:31Z")
HPD are getting level change when connected or disconnected on both i.e same behavior as devkit. Rpd & beads are taken care in back-plane board. ---
**Author:** ![haoye94](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@haoye94](https://forums.developer.nvidia.com/u/haoye94)\ **Post date:** [July 15, 2021, 12:43pm UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/14 "2021-07-15T12:43:47Z")
Did you manage to solve this? Im used a similar design with TPD12S016 and got the same problem as you. Can you share how did you solve it? Thanks! ---
**Author:** ![JamesVx](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@JamesVx](https://forums.developer.nvidia.com/u/JamesVx)\ **Post date:** [July 16, 2021, 4:27am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/15 "2021-07-16T04:27:45Z")
I’d like to know as well. Should an HDMI 1.4 interface IC be able to work for HDMI 2.0? ---
**Author:** ![haoye94](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@haoye94](https://forums.developer.nvidia.com/u/haoye94)\ **Post date:** [July 19, 2021, 3:03am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/16 "2021-07-19T03:03:07Z")
UPDATE: I found that the HPD was active low, and if we just used TPD12S016 as is, it performs logic level translation perfectly but it is active high. I did some rework to make it active low and it works now. ---
**Author:** ![kayccc](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/kayccc/32/14043_2.png) [@kayccc](https://forums.developer.nvidia.com/u/kayccc)\ **Post date:** [July 28, 2021, 6:42am UTC](https://forums.developer.nvidia.com/t/hdmi-1-0-related-queries/84294/17 "2021-07-28T06:42:58Z")
Closed on July 28, 2021, 6:42am UTC