Hi there, I am new to Nvidia Jetson. I am using Jetson Orin NX 16 GB with custom board. Here is the article I am using: Waveshare Jetson Orin NX 16 GB Dev Kit Wiki. The installation and flashing process is not different from Official Devkit as far as I understand. On sdkmanager I get stuck on “INFO: Flash Jetson Linux - flash: Waiting for target to boot-up…” and I get a timeout. I searched for similar problems on the forum and found that I need to do serial communication. When monitoring serial communication via Minicom, Jetson asks me to press certain keys. I have tried the keys there both through minicom and using a keyboard connected to jetson but without any results. SDKM_logs_JetPack_6.0_(rev._2)_Linux_for_Jetson_Orin_NX_modules_2024-07-21_19-29-17.zip (235.9 KB)
Custom board might not work using SDK manager flashing.
You need to use flashing script.
Also you need to set EEPROM size to 0 in the device tree file, if your custom board does not have a EEPROM , do dtlb build and then flash using script to make successful flashing
As @nagesh_accord said, SDK Manager may not work with your custom carrier board.
Please check with your vendor for the custom BSP package and use the flash script to flash the board.
It seems you are flashing Jetpack 6.0, please also try if Jetpack 5.1.3 works on your board.
I set the EEPROM read size to 0. And I executed the 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
But I got the same result.
I had installed Ubuntu 22.04 for sdkmanager, neither docker nor distrobox got me this far. I would not want to downgrade Ubuntu again. And if I have the chance, I would like to use the latest version for Jetson as much as possible. Also according to Waveshare’s Wiki, Jetpack 6 is supported.
Ok I built the kernel, then I built the DTBs, but still the same. I’m still getting
Jetson System firmware version 36.3.0-gcid-36191598 date 2024-05-:00
ESC to enter Setup.
F11 to enter Boot Manager Menu.
Enter to continue boot.
on Serial Debug
Shouldn’t I also do something in Linux_for_Tegre/source for the EEPROM setting? It seems to me that DTB compilation has nothing to do with “Linux_for_Tegra/bootloader/tegra234-mb2-bct-common.dtsi”.
E> LOADER: Invalid value Header magic.
E> Validation failed for 1 copy of BRBCT @ 0
I> strt_pg_num(512) num_of_pgs(16) read_buf(0x40071738)
E> LOADER: Invalid value Header magic.
E> Validation failed for 2 copy of BRBCT @ 262144
I> strt_pg_num(1024) num_of_pgs(16) read_buf(0x40071738)
E> LOADER: Invalid value Header magic.
E> Validation failed for 3 copy of BRBCT @ 524288
I> strt_pg_num(1536) num_of_pgs(16) read_buf(0x40071738)
E> LOADER: Invalid value Header magic.
E> Validation failed for 4 copy of BRBCT @ 786432
E> NV3P_SERVER: Failed to get address for br bct from nv3p helper.
I saw some errors in MB1 as above.
Do you have some modification in BCT for MB1?
Since the board is not designed from you, I would suggest you ask the help from your vendor to get the required custom BSP package and the steps to flash this custom carrier board.