I checked the latest status and there were some mistakes in my previous comments so I deleted them.
Jetson Nano has passed the HDMI2.0 certification. However, we still have some 4k@60 modes that are not supported.
The mode we are using for the compliance test are below.
Below are the modes we test for HDMI2.0 compliance :
3840x2160p@60hz RGB
3840x2160p@50hz RGB
and we are using rel-32.4.2.
Also, thanks for all the log you’ve provided. However, we don’t see any error in your log. The clk shows 533Mhz and no error from display and graphic drivers. I cannot tell why you could only see 133Mhz measured on scope.
Could you try to use a real monitor with 4k@60 mode and see if this module is able to output?
If you could find a monitor that has 533Mhz, it would be better.
As what I said, we connect Nano with a real 4K monitor, it will display 3840x2160@60Hz. but it failed to test when we connect Nano with HDMI2.0 test fixture, we will keep on debug this issue, thanks for your advice.
Another problem we want to discuss with you:
We have tested HDMI1.4 4K@30, but test item eye pattern fail;the fail picture as enclosure.We want to know if Nvdia have any solutions to strengthen HDMI output signals, likes some Linux commands,etc…
Or any suggestions about this failed eye pattern?
As what I said, we connect Nano with a real 4K monitor, it will display 3840x2160@60Hz. but it failed to test when we connect Nano with HDMI2.0 test fixture, we will keep on debug this issue, thanks for your advice.
Maybe you could find a monitor also with 533Mhz or maybe a 594Mhz mode and see if you could still measure 133M pclk. Actually, from your log and clk data from software node, there is no error.