Nvidia Jetson Orin Nano Dev Board HDMI Enablement Help

Issue Overview

Users are experiencing issues when attempting to enable HDMI output on custom carrier boards for the Nvidia Jetson Orin Nano module. The specific symptoms include:

• Errors occur during the flashing process when using custom board configurations
• The Orin Nano module fails to detect the NVMe storage on the custom carrier board
• HDMI output does not function on the custom carrier board after flashing

The problem occurs when flashing the Orin Nano module using a custom board configuration in order to enable HDMI support. It impacts the ability to use the Orin Nano with custom carrier boards that have HDMI output.

Possible Causes

There are a few potential causes for the HDMI enablement issues on custom Orin Nano carrier boards:

1. Incorrect flashing commands or parameters for the custom board configuration
2. Missing or incompatible device tree files in the custom board configuration
3. NVMe storage not detected due to PCIe controller configuration differences between the dev kit and custom carrier board
4. Driver or firmware incompatibilities between the Orin Nano module software and custom carrier board hardware

The root cause seems to be that the Orin Nano module expects certain PCIe controller configurations that are present on the dev kit carrier board but not on the custom carrier board. This prevents the NVMe storage from being detected which causes the flashing process to fail.

Troubleshooting Steps, Solutions & Fixes

To troubleshoot the HDMI enablement issues on a custom Orin Nano carrier board:

1. Double check that you are using the correct flashing commands and parameters for your custom board configuration. Make sure the device tree files and board names match your setup.

2. Verify that the necessary custom device tree files for your carrier board are present in the Linux4Tegra (L4T) board support package and being used in your flashing command:

   • tegra234-mb1-bct-pinmux-p3767-hdmi-a03.dtsi
   • tegra234-mb1-bct-padvoltage-p3767-hdmi-a03.dtsi

3. If the NVMe storage is not detected after flashing, it may be due to differences in the PCIe controller configuration between the dev kit and custom carrier board. To resolve this:

   • Identify which PCIe controller the NVMe storage is connected to on your custom board
   • Modify the device tree files to enable the required PCIe controller(s)
   • Re-flash the Orin Nano module with the updated device tree

4. If the issue persists, there may be a driver or firmware incompatibility. Collect logs from the dev kit and your custom board and contact Nvidia for further assistance:

   • Boot logs
   • Flashing logs
   • dmesg output
   • Board schematics and documentation

Some additional tips:

• Make sure you can successfully flash an unmodified Jetson Orin Nano dev kit before attempting a custom board configuration. This will isolate issues with your flashing setup.
• Compare the PCIe controller and NVMe storage connections between the dev kit and your custom carrier board to identify differences
• Double check the board SKU and revision information in your flashing commands and configuration files
• Search the Nvidia forums for posts from other users working on custom Orin Nano carrier board designs to see if they have encountered similar issues

If you continue to have trouble enabling HDMI on your custom Orin Nano carrier board, it’s best to reach out to Nvidia directly for support. They can provide more specific guidance and troubleshooting assistance.