About using the HDMI port

Hello, according to your instructions, I followed the content of the community forum to try to achieve the HDMI interface that can open AGX orin, but the puzzled thing is that the operation did not achieve the effect I wanted. Can you give me any specific hints to get me there?

麻煩先照這個步驟上patch, 做full flash. 這是有其他用戶已經驗證過的檔案.
另外, 麻煩對照一下flash log確認你燒進去的pinmux跟dtb真的是你改的那一份
因為市面上有多款Orin module. dtb跟pinmux檔案有可能不是你預期要改的那份

apply the [orin-hdmi-support-pinmux.patch]
use the new hdmi dcb file '[tegra234-dcb-p3701-0000-a02-p3737-0000-a01-hdmi-4-ga5.0.2.dtsi]
apply the kernel hdmi hotplug patch [0001-orin-hdmi-hotplug-support-kernel-dts.patch]
rebuilt the kernel dtb and “reflash the image” //Note : make sure ‘reflash’ the image, no substitute dtb in exlinux!!
I differ from the above in that I am running the script file, and I say that the words a04 in the script file are removed
This question has been bothering me for a long time, and I look forward to hearing from you.

  1. How did you update the device tree?

  2. Any flash log to share?

Regarding the device tree I followed the Display Configuration and Bring-Up — Jetson Linux<br/>Developer Guide 34.1 documentation Instructions to add the provided dtsi file to the tegra234-p3701-0000-p3737-0000.dts file, as for Pinmux I think the patch you provided has GPIO and multiplexing pins turned on, so only the patch was updated.

Uploading: flas1h.txt…

I mean how did you build out the device tree and make sure you really flash it to your board?

Sorry I misunderstood you
After I changed the dts file, I did not manually generate the corresponding dtb file, but used the flash.su, and after running it, I found that the HDMI pin can already provide 5v voltage, so I think that the content I changed has been burned into the kernel, and the reason why the HDMI cannot run is because some operations are missing.

id not manually generate the corresponding dtb file, but used the flash.su,

看不太懂這一句想表達的意思. 所以你改了source code, 沒build任何東西 然後覺得這樣可以更新到機器上的binary?

Yes, I encountered some errors in the process of manually generating DTB with dtc -I dts -O dtb -o, and could not generate dtb files, so I chose to compile directly with flash, and got a part of the effect I needed, I don’t understand the specific compilation process, I judge that the script file you provided has the relevant operations of automatically generating dtb, I don’t know if my understanding is correct

The error encountered in generating dtb is about syntax, but I found no relevant syntax error when I located to the specific location, and the specific reason is still being found, which is why I directly chose to compile

That sounds wrong… flash.sh does not build anything.
You should build the dtb from source code. Not using dtc tool.

Download source code from the website.

Follow the document to build.


Thank you for the guidance, I will go and deal with the kernel problem now, please do not close the topic Thank you

I’d like to confirm if the new DCB file and the patch you provided have done the changes to the ORIN regarding the HDMI pins, and if there is anything else I need to do to complete the changes to convert the DP pins to the HDMI pins

You can try to do some experiment on your side.

For example, what is the result of

export DISPLAY=:0

Does dmesg give something new print after you hotplug the HDMI cable

Sorry I don’t know enough about this, in my understanding, this log should be connected to HDMI and output log in the display, but the display can’t work now, so I don’t know how to observe the status of the display. Not sure if you can provide a patch on changing pins and multiplexing, I’d like to check if there are any errors in my changes。
Thank you very much for your guidance

You cannot rely on display when doing bring up.

Need to use uart serial console to dump log.

Also, I already applied all the patches you need on that post. The most reason that it cannot take effect is because users didn’t apply them correctly.

Thus, dump the log and use the console to check things first.

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