Dear Experts,
I am working on bringing up the HDMI output for the the Jetson Orin Nano 8GB (picked from the Nvidia Jetson Orin Nano Developer Kit) on top of our custom carrier board that works fines with Xavier NX.
The custom board does not dispose EEPROM,
I tested in both Jetpack-5.1.2 and Jetpack-6.2.
So far the first problem I faced was “Waiting for target to boot-up…” in loop. I resolved this as below :
In Jetpack-5.1.2, I followed this link Jetson Orin NX and Nano Series — Jetson Linux Developer Guide documentation
In Jetpack-6.2 : I did similarly (cvb_eeprom_read_size = <0x0>) for the file JetPack_6.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts.
then flashed the NVMe on the board :
In Jetpack-5.1.2, with command :
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
(Please note that I used p3509-a02+p3767-0000.conf as it was said the one having all the software patches working for the use-case of Jetson Orin Nano on top of Xavier NX carrier board with HDMI output)
The flashing was NOT successful with the following error :
saving flash command in flashcmd.txt
*** no-flash flag enabled. Exiting now... ***
User can run above saved command in factory environment without
providing pkc and sbk keys to flash a device
Example:
$ cd bootloader
$ sudo bash ./flashcmd.txt
Save initrd flashing command parameters to /workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/initrdflashparam.txt
/tmp/tmp.AVVELzJnPP /workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
/tmp/tmp.AVVELzJnPP/initrd /tmp/tmp.AVVELzJnPP /workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
58247 blocks
84699 blocks
/tmp/tmp.AVVELzJnPP /workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
flashimg0=boot0.img
/workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
Success
Cleaning up...
Finish generating flash package.
No devices to flash
Full flashing log :
flash_1-4_0_20250312-133324.log (7.4 KB)
Then in Jetpack-6.2, with command :
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 p3509-a02-p3767-0000 internal
(Please note that the p3509-a02+p3767-0000.conf in Jetpack-5.1.2 became p3509-a02-p3767-0000.conf in Jetpack-6.2)
The flashing seemed to be successful but NO HDMI output seen :
Writing /mnt/internal/gpt_secondary_3_0.bin (16896 bytes) into /dev/mtd0:67091968
Copied 16896 bytes from /mnt/internal/gpt_secondary_3_0.bin to address 0x03ffbe00 in flash
[ 206]: l4t_flash_from_kernel: Successfully flash the qspi
[ 206]: l4t_flash_from_kernel: Flashing success
[ 206]: 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-4_0_20250312-140429.log
Full flashing log :
flash_1-4_0_20250312-140429.log (48.2 KB)
Could you help to share some insight to resolve the issue, please ?
Thanks and best regards,
K