Unable to see Display during Boot time in AGX Orin over HDMI

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hi,

I am using Jetson AGX Orin Industrial with Custom Carrier board. We have HDMI instead of DP in our design hence I enable the appropriate Pins for HDMI in Pinmux as well as added the below files in Configuration files-

PINMUX_CONFIG="tegra234-mb1-bct-pinmux-p3767-hdmi-a03.dtsi";
PMC_CONFIG="tegra234-mb1-bct-padvoltage-p3767-hdmi-a03.dtsi";
OVERLAY_DTB_FILE+=",tegra234-dcb-p3767-0000-hdmi.dtbo";
DCE_OVERLAY_DTB_FILE="tegra234-dcb-p3767-0000-hdmi.dtbo";

Along with os_gpio_hotplug changes-
os_gpio_hotplug_a = <&tegra_main_gpio TEGRA234_MAIN_GPIO(M, 0) 0>;

By doing above changes my HDMI display is working properly but,

the screen directly appears after full boot directly at login screen also sometimes I need to press monitior button to awake the display. with this I cant go to EFI settings and unable to see boot messages.
how to solve this issue?

2

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

The issue you’re facing with your custom carrier board for the Jetson AGX Orin Industrial, where the HDMI display works but you’re unable to access the EFI settings or see boot messages, is likely due to the display not being properly initialized during the boot process. This is a common challenge when using HDMI instead of DP on custom boards.

To address this issue, you’ll need to ensure that the display is properly configured and initialized during the boot process. Here are some steps you can take:

  1. Verify Pinmux Configuration: Double-check that the pinmux configuration for HDMI is correct. Ensure that the pins are properly set as HDMI outputs and that the pinmux configuration is applied during the boot process.
  2. Display Configuration and Bring-Up: Review the Display Configuration and Bring-Up component documentation to ensure that you’re following the correct procedure for initializing the display. This may involve modifying the device tree or adding specific configuration files.
  3. Orin Specific Display Configuration: As you’re using the Jetson AGX Orin, you may need to consult the Orin specific display configuration documentation. This may provide additional guidance on configuring the display for HDMI output.
  4. Boot Process: Understand the boot process of the Jetson AGX Orin, specifically the stages involved in initializing the display. You can refer to the Jetson Orin NX Boot Process documentation as a starting point.
  5. EFI Settings: To access the EFI settings, you may need to press a specific key during the boot process (e.g., the ‘Esc’ key). If you’re unable to access the EFI settings, try pressing the monitor button to wake up the display and then press the key to enter the EFI settings.
  6. Boot Messages: To see boot messages, you can try enabling the debug UART or using a serial console. This will allow you to view the boot messages and potentially identify any issues during the boot process.
  7. HDMI Hot-Plugging: As you’ve mentioned that you need to press the monitor button to wake up the display, it’s possible that the HDMI hot-plugging is not working correctly. You can try modifying the osgpiohotplug changes to see if it resolves the issue.
  8. Custom Board Configuration: As you’re using a custom carrier board, ensure that the board is properly configured for HDMI output. You may need to modify the board’s configuration files or device tree to enable HDMI output.

In comparison to other Jetson modules, the Jetson AGX Orin has specific requirements for display configuration and initialization. By following the steps above and consulting the relevant documentation, you should be able to resolve the issue and access the EFI settings and view boot messages.

Additionally, you can refer to the following resources for more information:

  • Jetson AGX Orin Developer Guide
  • Display Configuration and Bring-Up documentation
  • Orin Specific Display Configuration documentation
  • Jetson Orin NX Boot Process documentation
  • HDMI configuration tool documentation (if applicable)

If you’re still facing issues, you can try seeking help from the NVIDIA developer forums or contacting NVIDIA support for further assistance.

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

4

Hi jitendra.kolhe,

What’s the Jetpack version in use?

Do you mean that there’s no display output in UEFI so that you cannot enter into UEFI menu?

If so, please use the debug UEFI binary to check if there’re any errors.

5

I am using Jetpack 6.2.1 (r36.4)
Yes there is no display output in UEFI.
how to use debug UEFI binary?

6

You could not flash Orin AGX with tegra234-mb1-bct-pinmux-p3767-hdmi-a03.dtsi…

That whole file is for Orin NX/Nano. You need to pick up only the HPD pin setting from it to your Orin AGX pinmux setting.

7

currently I am using above 2 files only.
by mistake I used 4 but removed later

8

Are you trying to say you could not see HDMI monitor during bootlaoder stage or you are talking about kernel stage?

Or you have no idea what I am trying to ask here?

9

Are you trying to say you could not see HDMI monitor during bootloader stage.
yes exactly this is the issue. After full boot I can see the login screen

10

Could you share your xrandr result after you boot up into Linux for us to check if you really configure things correctly?

12

here is the xrandr result-

image
image1024×768 43.4 KB

13

Looks correct.

To check UEFI status, please rebuild the UEFI from source code, replace the binary with debug build one and reflash the board.

14

this page has 404 error. not correct link i guess can you please share the correct one

15

corrected.

17

we found the problem in wiring line sequence.
https://forums.developer.nvidia.com/t/hdmi-doesn-t-work-for-some-monitors-discovering-again/248932/47

this post solution helps me and now I can see the Display as soon as Bootloader starts.
but can you clarify that why the sequencing should be like this?

image
image716×197 103 KB

18

It is pure hardware rule. Not something special to clarify.

19

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