Jetpack 6.2.1 Linux 36.4.4, HDMI Trouble

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
,
1

Hello!.

I’m working on building a HOST PC for setting up AGX ORIN INDUSTRIAL.
But I’m trying to use HDMI port instead of DP port, and I got a problem in this process.

First, Display Configuration and Bring-Up — Jetson Linux
Developer Guide 34.1 documentation

I tried to change the HDMI setting by referring to the URL above, but the version above does not seem to work because it does not match my current version.

Path: <Kernel_Sources>/hardware/nvidia/platform/t23x/concord/kernel-dts/

In particular, this path doesn’t seem to match my version.

How can I modify the settings so that DP can be used as HDMI in my version?

2

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are trying to modify the display configuration on a Jetson AGX Orin Industrial module to use the HDMI port instead of the DP port. However, the documentation you are referring to is for a different version, and the path hardware/nvidia/platform/t23x/concord/kernel-dts does not match your current version.

To modify the settings to use HDMI instead of DP on your version, you can try the following:

  1. Check the documentation for your specific version of the Jetson AGX Orin Industrial module. You can find the documentation on the NVIDIA website or by searching for “Jetson AGX Orin Industrial documentation” along with your version number.
  2. Look for the section on display configuration and HDMI support. This section should provide information on how to modify the settings to use HDMI instead of DP.
  3. Check the kernel device tree (DTB) files for your version. The DTB files are usually located in the hardware/nvidia/platform/t23x/concord/kernel-dts directory, but the exact path may vary depending on your version. You can try searching for “kernel-dts” along with your version number to find the correct path.
  4. Modify the DTB files to enable HDMI support. You can do this by adding or modifying the HDMI-related nodes in the DTB files. For example, you may need to add a node for the HDMI controller or modify the existing node to enable HDMI output.
  5. Rebuild the DTB files and update the kernel configuration to use the modified DTB files.

Alternatively, you can try using the p3509-a02-p3767-0000.conf config file to flash the board, as mentioned in the provided context. This config file is specifically designed for HDMI support on the Jetson Orin NX and Nano modules, but it may also work on the Jetson AGX Orin Industrial module.

Here is an example of how to flash the device with HDMI support using the p3509-a02-p3767-0000.conf config file:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 p3509-a02-p3767-0000 internal

Note that this is just an example, and you may need to modify the command to match your specific version and configuration.

In comparison to the provided context, the main difference is that the original context is for the Jetson Orin NX and Nano modules, while your question is for the Jetson AGX Orin Industrial module. However, the general steps for modifying the display configuration and enabling HDMI support are similar, and you can try using the same config file and modifying the DTB files to achieve the desired result.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

1 Like
5

p3509-a02-p3767-0000.conf has the files you need to enable HDMI.

You could not directly use the pinmux file from it because that is for Orin NX/Nano.
Pinmux setting for the HPD pin needs to be GPIO input. You need to apply similar things to the Orin AGX pinmux.

And enable HDMI mode in the dcb image. The overlay file inside of p3509-a02-p3767-0000.conf could be in use directly.

1 Like
6

Hello. Wayne.

I checked your answer carefully. However, I was a novice hardware developer, so I didn’t understand your answer correctly.

Summarizing your response I understood, I understood that the p3509-a02-p3767-0000.conf file has the file I need to activate HDMI, but I can’t use this myself.

Does it mean that I need to download Jetson AGX Orin Series Pinmux from the above site and change it to suit the user’s environment?

If it’s not something I understand or there’s a simpler way than this, I’d appreciate it if you could elaborate.

7

I think the problem here is that you need to get into familiar with how this whole BSP is doing first.
For example, how to flash a board, What files to modify,. Whether you have some basic knowledge for Linux kernel.

Our document won’t cover some basic things like how a Linux kernel works here. So want to know if you have any software engineer on your side first.

1 Like
8

To be exact, we previously created a Host PC using the Jetpack 6.0 DP version. Based on the instruction manual for this, we are trying to reconstruct the Host PC using Jetpack 6.2.1.

Currently, I downloaded BSP, ROOTFsS, Kernel Source Code, Bootlin Toolchain 11.3 and finished copying the generated files after the kernel build.

However, since the manual I have is based on the DP version, there is a difference from the current system. Looking at other forums, should there be a process to correct p3768-0000-p3768-0000-a0.conf by writing Pinmux based on the board I designed?

9

Just to clarify. Those board configs are just a sample for NV devkit

p3768-0000-p3768-0000-a0.conf is for Orin Nano devkit. This thing has no HDMI port on it. So by default you won’t see any HDMI enabled from it.
p3509-a02-p3767-0000.conf is for Orin Nano + Xavier NX devkit. This one has HDMI port on it. So the software will have HDMI enabled.

The file name itself is just a string. It does not matter. It is the file in use inside of it that matters.

For example, I can create a 123.conf and still able to flash the board if this 123.conf has correct files in use inside of it.

Please be aware that both files mentioned above are not for Orin AGX.

So I think the basic item here is you should locate what file you are using to flash the board.

Also, I don’t know what is your point to mentiond JP6.0 DP. Are you talking about you once enable HDMI on this version? Or you just talking about you flashed your board before with this version?

1 Like
10

Thank you very much for your sincere reply.

First of all, my mention of JP 6.0 DP version was about activating HDMI in this version as you understood, and similar to this version, JP 6.2.1 version was a question about having to activate HDMI in a similar way

Also, when I saw the answer, the name of the actual .conf file itself doesn’t matter, and I mentioned that the board can be flash if the correct file is in use inside, so could you tell me how to find or create a file that I use to flash the board?

11

Hi,

Just to clarify. You could answer the question by yourself actually.

How did you flash your board? If you don’t even know how to flash your board, then that is another problem.

1 Like
12

Thank you for your reply, Wayne.

To clarify my current situation:

I have already flashed the AGX Orin Industrial board before, but I’m not fully sure which .conf file was used during that process. That’s why I asked about how to find or create the correct .conf file to enable HDMI — especially 6.2.1.

I understand that if I’ve flashed the board, I should know which configuration I used. However, as a relatively beginner hardware developer, I followed existing flashing guides without fully understanding the role of each file. Now I want to learn how to identify or build the proper .conf file for my board.

So, could you please help clarify. If I want to create a custom .conf file for the AGX Orin Industrial (to enable HDMI), is there any official guideline or example I can follow?

Any guidance or documentation links would be greatly appreciated. Thank you for your patience.

13

Hi,

I need you to tell this by yourself… How did you flash your board?

Just answer this question first. No need to tell anything else…

1 Like
14

Hi,

I flashed my board “sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1”

Is that the answer you thought of?

15

Then your board config in use now is jetson-agx-orin-devkit.conf.

The flash command will tell which board config is in use.

1 Like
16

Are you sure this for Orin AGX industrial? This config file only support Orin AGX. Not Orin AGX industrial.

1 Like
17

umm, I understand that in the installation guidebook I have, I can copy and use AGX Origin Industrial File, tegra234-p37-0000-p3701-0008-nv.dtb.

18

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 <board_configuration> nvme0n1p1

Sorry I was mistaken, I gave you the wrong command. The actual command is the same as above

19

Hi,

I am not sure why you just hide the most important thing by yourself… What is that “<board_configuration>” in use in your actual flash command…

Without this info, you just gave out a dummy information…

That board configuration is the file you should modify.

20

HI,

sudo ./tools/kernel_flash/l4t_initrd_flash.sh –external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml
–showlogs --network usb0 cti/orin-agxi/ nvme0n1p1

The actual command is the same as above

21

Why are you flashing a CTI board here? Are you a engineer working for ConnectTech? This whole discussion seems kind of confusing.

22

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-agx-orin-devkit nvme0n1p1

sorry I was mistaken, I gave you the wrong command. The actual command is the same as above.

As far as I know, there is no separate Industrial config file in NVIDIA JetPack 6.2.1 / L4T 36.4.4 even for Industrial SKU, so I understand that there is no problem using the jetson-agx-orin-devkit default config in flash, is that correct?