Jetson Orin Nano HDMI/DisplayPort Output Failure — Comprehensive Technical Summary

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
,
1

Hello,

I am requesting official NVIDIA technical support for a Jetson Orin Nano Super Developer Kit that cannot output video through HDMI or DisplayPort.

Device identification

Product type: Jetson Orin Nano Super Developer Kit

Board configuration: P3768-0000 + P3767-0005-super

Model string: NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super

Compatible string: nvidia,p3768-0000+p3767-0005-super

Purchase source: Naver Smart Store, South Korea

Intended use: Internal development and testing; not integrated into a commercial end product

Current software information

BIOS / Firmware: 36.4.7

NVIDIA Driver: 595.78

CUDA: 13.2

Current operating status

NVMe SSD boot: Working

SSH access: Working

VNC GUI: Working

HDMI output: Not working

DisplayPort output: Not working

The operating system and remote GUI are accessible, but the display engine and GPU initialization do not complete successfully.

Repeated error messages

DCE ucode abort occurred
DCE bootstrapping failed
dce boot wait failed (-110)
NVRM: GPU0 RmInitAdapter: Cannot initialize DCE firmware RM
Failed to allocate NvKmsKapiDevice
nvidia-modeset: ERROR: Failed to open GPU

nvidia-smi displays the Orin GPU name, but temperature, power, memory usage, and GPU utilization are shown as N/A.

Main technical concern

The most likely cause appears to be a version mismatch between the board firmware and the installed JetPack/BSP/GPU driver stack. However, I need NVIDIA to confirm this officially.

I also need clarification on whether the identification string Engineering Reference Developer Kit Super is normal for an official NVIDIA Developer Kit. This string alone should not be treated as proof that the board is a third-party carrier board without further verification.

Information requested from NVIDIA

Please provide an official response to the following:

Is P3768-0000 + P3767-0005-super an officially supported NVIDIA Jetson Orin Nano Super Developer Kit configuration?

Is the model string NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super normal for an official NVIDIA Developer Kit?

Is firmware 36.4.7 officially compatible with NVIDIA driver 595.78 and CUDA 13.2?

If this combination is unsupported, what exact JetPack, Jetson Linux, firmware, and driver versions should be installed?

What is the official NVIDIA full-flash procedure to update QSPI firmware, bootloader, BSP, and the operating system together?

Does installing an SD card or NVMe image update QSPI firmware, or is Recovery Mode flashing from an Ubuntu host required?

Can the DCE bootstrapping, GPU initialization, and HDMI/DP failures above be caused by a firmware/BSP version mismatch?

What diagnostic commands and logs are required for formal technical analysis?

If HDMI/DP still fails after the official supported full-flash procedure, will NVIDIA treat this as a possible hardware defect and provide RMA guidance?

Can NVIDIA verify product authenticity and warranty eligibility using the product P/N and S/N?

Please provide the official response by email to:

getmored@gmail.com

Thank you.

4

— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —

Based on the provided context, I will address the questions and concerns raised about the Jetson Orin Nano Super Developer Kit.

  1. Is P3768-0000 + P3767-0005-super an officially supported NVIDIA Jetson Orin Nano Super Developer Kit configuration?

    • The context does not explicitly confirm this as an officially supported configuration. However, it mentions the model string “NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super,” which suggests it could be related to official development kits.

  2. Is the model string NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super normal for an official NVIDIA Developer Kit?

    • The provided documentation does not explicitly state that this model string is normal or expected for an official NVIDIA Developer Kit. It implies that “Engineering Reference” might be part of official development or reference designs, but clarity on this would require further confirmation from NVIDIA.

  3. Is firmware 36.4.7 officially compatible with NVIDIA driver 595.78 and CUDA 13.2?

    • The context does not provide a direct compatibility matrix between firmware versions and driver/CUDA versions. However, the mention of version mismatches as a potential cause for the observed issues suggests that compatibility between these components is crucial.

  4. What exact JetPack, Jetson Linux, firmware, and driver versions should be installed?

    • The provided context does not specify the exact versions that should be installed for compatibility. It suggests that a version mismatch could be the cause of the issues, implying the need for compatible versions, but does not provide a list of compatible versions.

  5. What is the official NVIDIA full-flash procedure to update QSPI firmware, bootloader, BSP, and the operating system together?

    • The context mentions flashing the device but does not detail the full-flash procedure for updating QSPI firmware, bootloader, BSP, and the operating system together. It suggests that installing an SD card or NVMe image might update QSPI firmware, but the exact procedure, especially for a full update, is not provided.

  6. Can the DCE bootstrapping, GPU initialization, and HDMI/DP failures above be caused by a firmware/BSP version mismatch?

    • Yes, the context implies that a version mismatch between the board firmware and the installed JetPack/BSP/GPU driver stack could be a likely cause of the observed issues, including DCE bootstrapping, GPU initialization, and HDMI/DP failures.

  7. What diagnostic commands and logs are required for formal technical analysis?

    • The context does not specify the exact diagnostic commands and logs required for a formal technical analysis. However, it mentions error messages related to DCE ucode abort, DCE bootstrapping failure, and GPU initialization issues, suggesting that logs related to these components could be relevant.

  8. If HDMI/DP still fails after the official supported full-flash procedure, will NVIDIA treat this as a possible hardware defect and provide RMA guidance?

    • The provided context does not explicitly state NVIDIA’s policy on treating persistent issues after a full-flash procedure as potential hardware defects. It suggests the importance of following official procedures for troubleshooting and updating the device.

  9. Can NVIDIA verify product authenticity and warranty eligibility using the product P/N and S/N?

    • The context does not provide information on how NVIDIA verifies product authenticity and warranty eligibility. It implies that official channels and documentation are crucial for such verifications.

Given the information provided and the constraints of the context, some aspects of the question are not fully covered, such as the exact compatibility matrix between firmware, driver, and CUDA versions, and the detailed procedure for a full-flash update of the device. For comprehensive support and to address all concerns, including product authenticity and warranty eligibility, it is recommended to contact NVIDIA support directly as suggested in the question.

— We support team will also look into your issue to have further suggestions soon. please stay tuned. —

5

Hi,

The P3767-0005 development module on the P3768-0000 reference carrier board is an officially supported Jetson Orin Nano Developer Kit configuration. The jetson-orin-nano-devkit-super configuration is also supported. Please refer to the Jetson Linux r39.2 supported configurations.

The Engineering Reference Developer Kit Super model string alone does not indicate that the system uses a third-party carrier board, but it also cannot be used to verify the product’s authenticity or warranty status.

Also, the Jetson Orin Nano Developer Kit has one native DisplayPort output and no native HDMI port. To use an HDMI display, connect it through a DisplayPort-to-HDMI adapter. Please see the Developer Kit hardware layout.

Firmware 36.4.7 is not, by itself, evidence of a firmware/BSP mismatch. JetPack 7.2 for Jetson Orin uses Jetson Linux 39.2 and CUDA 13.2.1, and its documented installation path accepts JetPack 6.x-generation UEFI/QSPI firmware newer than 36.0. See the JetPack 7.2 release information and Orin Nano installation guide.

To confirm whether the installed BSP, kernel, firmware, and display packages form a consistent release, please run the following commands through SSH and share the complete output:

cat /etc/nv_tegra_release
uname -r
dpkg-query -W -f='${Package}\t${Version}\n' \
  nvidia-l4t-core nvidia-l4t-kernel nvidia-l4t-firmware \
  nvidia-l4t-display-kernel nvidia-l4t-bootloader 2>&1
sudo nvbootctrl dump-slots-info

Please also confirm:

  1. How the current system was installed: JetPack 7.2 ISO, SDK Manager, an SD/NVMe image, or manual package upgrades.
  2. Whether a monitor was tested with a direct DisplayPort-to-DisplayPort connection, or only through a DisplayPort-to-HDMI adapter.

The reported DCE and GPU initialization errors require investigation, but they do not yet establish either a version mismatch or a hardware defect. A full flash or RMA recommendation should wait until the installed release state above is confirmed.

Thanks.

6

Hello Wichiu,

Thank you for your detailed guidance and clarification.

The display output issue on my Jetson Orin Nano Ubuntu system has now been resolved successfully. The DisplayPort-to-HDMI output is working normally, and the Ubuntu desktop is displayed correctly after login.

Your explanation regarding the supported P3767-0005 + P3768-0000 configuration, firmware compatibility, and the required diagnostic checks was very helpful in resolving the issue.

Thank you again for your support.

Best regards,