[Jetpack-5.1.2] HDMI not working with 900-13767-0010-0V1

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

Dear Forum,

We recently ordered a lot of 20 of Jetson Orin NX 8GB (900-13767-0010-0V1, origin Vietnam) and managed to flash them successfully with the instruction to apply the PCN210361

We used the SOM with a custom carrier board, however the HDMI seems not working with these new SOMs and keeps flashing the text about the resolution when entering Tegra Ubuntu interface.

f2e675c66f45ee1bb754
f2e675c66f45ee1bb7541156×646 83.4 KB

Meanwhile, the HDMI display worked very well with older Jetson Orin NX SOMs (both 16GB 900-13767-0000-001 or 8GB 900-13767-0010-001, origin China) as I’d already applied the following work-around from the release note :

Screenshot from 2026-07-24 15-03-25
Screenshot from 2026-07-24 15-03-251015×660 55.7 KB

The HDMI interface of the carrier board worked well with SOMs origin from China and with either of below flashing methods :

  • With SDK manager,

  • With command-line : *sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal

I wonder of there’s any missing configuration for the newer Jetson Orin NX SOM, please ? Please also note that the HDMI of the custom carrier board + newer Jetson Orin NX SOM also works well with Jetpack-5.1.5.

Thanks and best regards,
Khang

2

please check your serial log to see if this is fail to boot issue or HDMI not work issue…

The concepts between them are totally different.

HDMI mode is not enabled when you flashed the image from sdkmanager either. That one indicates you didn’t know the config behind it. Only the p3509 config truly enables the HDMI mode.

4

Hi @WayneWWW ,

I abandoned this as I decided to move to Jetpack-5.1.5 supporting SUPER mode as well as there was another problem relevant to jtop with this specific Jetson Orin NX 8GB for Jetpack-5.1.2.

Things (HDMI display, jtop, SUPER mode, …) work quite well with the Jetpack-5.1.5.

5

@khang.l4es

Want to clarify this again. We don’t know what was the original issue here because no log was shared.

If you think you are fine with current situation, then we could close this topic.

However, if you hit another issue next time. Make sure you could collect sufficient information so that others could tell what is going on.

6

Hi @WayneWWW ,

Our custom board does not dispose UART Debug interface therefore it was impossible to provide the log via that interface. One thing is sure is that the HDMI interface of our custom board worked perfectly with Jetpack-5.1.2 for both both 16GB 900-13767-0000-001 or 8GB 900-13767-0010-001, origin China. When it came to 8GB 900-13767-0010-0V1, there’s was flashing screen about the display timing with Jetpack-5.1.2, but no problem with Jetpack-5.1.5

7

This kind of comment still lacks of lots of necessary information which I could not comment on anything.

  1. Default config file does not enable HDMI mode. Using DP mode to run a HDMI monitor will only support to 1080p. 4k monitor won’t work.

  2. It is still unclear whether it is a boot failed case or HDMI not able to work case.
    I mean, boot up fail will make your HDMI not show anything, but it is clearly not a “HDMI issue” because HDMI monitor fails is just a result of boot failure.. Jetpack5.1.2 is quite old that maybe you hit PCN problem and leads to boot failure.

Again, as no log provided, everything here is just guess. No proof to tell what is going on.
If your carrier board is lacking of UART, you may still hit similar problem later if you want to upgrade to JP6 or JP7.
Better enable the UART on one board as debug board.