We have a custom carrier board that was previously designed for and has been working with the Jetson Xavier NX modules (8GB/16GB). We would like to use it for validating our hardware with the Jetson Orin NX 8GB module before migrating to this later definitively.
I followed the advice from here to flash this combo of custom carrier board + Jetson Orin NX 8GB SoM on top :
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
...
[ 270]: l4t_flash_from_kernel: Successfully flash the qspi
tar: Read checkpoint 470000
tar: Read checkpoint 480000
tar: Read checkpoint 490000
tar: Read checkpoint 500000
tar: Read checkpoint 510000
tar: Read checkpoint 520000
tar: Read checkpoint 530000
tar: Read checkpoint 540000
tar: Read checkpoint 550000
tar: Read checkpoint 560000
writing item=16, 9:0:secondary_gpt, 62545444352, 16896, gpt_secondary_9_0.bin, 16896, fixed-<reserved>-0, d8be6bac8ad811e28a4a22fbfb2f247274bbc063
[ 324]: l4t_flash_from_kernel: Successfully flash the external device
[ 324]: l4t_flash_from_kernel: Flashing success
[ 324]: l4t_flash_from_kernel: The device size indicated in the partition layout xml is smaller than the actual size. This utility will try to fix the GPT.
Flash is successful
Reboot device
Cleaning up...
Log is saved to Linux_for_Tegra/initrdlog/flash_1-8_0_20240501-131335.log
But right after that, there was nothing happen on the HDMI display connected to the board even-though the system was then mounted as USB device (L4T-README) on host machine (where sdkmanager is installed) later.
I also applied the patch in the Adaptation to the Carrier Board with HDMI for the Orin NX/Nano Modules section of the Jetson_Linux_Release_Notes_r35.4.1.pdf as suggested here :
To update, the HDMI output has not been working yet (especially for the displays I tested : Philips 23.8" 243V7QJAB, SAMSUNG 24" LF24T450FQEXXV, SAMSUNG 24" LS24C330GAEXXV) but it shows blinking cursor on my small FOXTECH 10" display : IMG_2543.MOV - Google Drive
I also notice that with the smaller HDMI display, there’s been UEFI screen appear during the (re-)flashing using the l4t_initrd_flash.sh command (Step 3 and the final Step where rebooting of the system is needed) :
Step 3 : Flash_Step3.MOV - Google Drive
Final step : Flash_final.MOV - Google Drive
And also with the 10-inch HDMI display, I am able to enter the UEFI configuration : UEFI.MOV - Google Drive
But then it shows nothing (no signal) when I press Continue button. After that the board reboots in loop (to the same UEFI screen) after a while. It looks like the UEFI looks for booting from the SSD NVMe but unnable to read/find necessary resources.
Got it. I just wanted to prove that the HDMI hardware was working in some case. Now I attach the flash log file and the associated debug log file during the flashing until the first attempt of rebooting right after the successful flashing.
I tested the hotplugging of HDMI cable in two cases :
a. Same hardware as I shared in the initial comment/description in which the R75 (connected to the HDMI_HPD signal of the Micro HDMI port) is still available : In this case nothing happens even with dmesg.
b. Reworked hardware by removing the R75 after double-checking the schematic of Jetson_Xavier_NX_Carrier_Board_Design_Files_A01 as well as the design guide for Orin Series :
Could you elaborate more about “The 2nd log from tegra186_gpio_irq is expected” as it seemed to be a kernel crash and it does not show anything still? I understood that the reworked hardware followed better the reference design/design guide from Nvidia.
nvidia@viansight-onx:~$ xrandr
Screen 0: minimum 8 x 8, current 640 x 480, maximum 32767 x 32767
HDMI-0 disconnected primary (normal left inverted right x axis y axis)
We finally got the HDMI of our custom Xavier NX based carrier board work with the Orin NX SoM. So far, there’s only one necessary fix documented in the Jetson_Linux_Release_Notes_r35.4.1.pdf that should be applied in terms of BSP.
Yes, I did do that very early prior the flashing. I meant that it was hardware issue, even-though it’d been working with the Xavier NX SoM without problem but it needs some tweaks for the Orin NX SoM by referencing the design guide.
