Flash Orin NX custom board - stay in waitinng for target to boot-up

jose41 · September 29, 2023, 6:56pm

Hello,

I am trying to flash a new Orin NX module on a custom carrier board with a NVMe. I am using SDKManager, I tried NVMe with fat and ext4 partition. the result is the same:

Entering RCM boot

[ 0.0232 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[ 0.0232 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[ 0.0232 ] rcm boot with presigned binaries
[ 0.0241 ] tegrarcm_v2 --instance 3-7 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 0.0247 ] BR_CID: 0x80012344705DD74F2000000019020240
[ 0.0320 ] Sending bct_br
[ 0.0382 ] Sending mb1
[ 0.0388 ] Sending psc_bl1
[ 0.0558 ] Sending bct_mb1
[ 0.0647 ] Generating blob for T23x
[ 0.0663 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[ 0.0669 ] The number of images in blob is 18
[ 0.0670 ] blobsize is 81059487
[ 0.0670 ] Added binary blob_uefi_jetson_with_dtb_sigheader.bin.encrypt of size 3182656
[ 0.0888 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 375168
[ 0.0892 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 190592
[ 0.0893 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 277312
[ 0.0894 ] Not supported type: mb2_applet
[ 0.0895 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 437984
[ 0.0896 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[ 0.0897 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 9097216
[ 0.0936 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[ 0.0948 ] Added binary blob_bpmp_t234-TE990M-A1_prod_sigheader.bin.encrypt of size 1048000
[ 0.0953 ] Added binary blob_tegra234-bpmp-3767-0001-3509-a02_with_odm_sigheader.dtb.encrypt of size 138880
[ 0.0955 ] Added binary blob_camera-rtcpu-sce_sigheader.img.encrypt of size 166304
[ 0.0958 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 537952
[ 0.0960 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 400960
[ 0.0962 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[ 0.0963 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1064752
[ 0.0968 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[ 0.0969 ] Added binary blob_boot0.img of size 63055872
[ 0.1267 ] Added binary blob_tegra234-p3767-0001-p3768-0000-a0.dtb of size 345391
[ 0.1716 ] tegrarcm_v2 --instance 3-7 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 0.1723 ] BL: version 0.32.0.0-t234-54845784-57325615 last_boot_error: 0
[ 0.2956 ] Sending bct_mem
[ 0.3163 ] Sending blob
[ 5.2081 ] RCM-boot started

/home/jeslava/nvidia/nvidia_sdk/JetPack_5.1.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra

```
                                *
```
Step 3: Start the flashing process *
```
                                *
```

Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Waiting for target to boot-up…
Timeout
Cleaning up…
20:15:06.258 - Info: [ Component Install Finished with Error ]
20:15:06.258 - Info: [host] [ 19.52 MB released. Disk Avail: 21.61 GB ]
20:15:06.258 - Info: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 3m32s ]

I tried 2 different cables and they are OK as I have already used for other modules.
The carrier board works correctly, I plugged an already flashed module and it boots correctly.

Any idea please?

The complete logs are here:

SDKM_logs_JetPack_5.1.1_(rev._1)_Linux_for_Jetson_Orin_NX_modules_2023-09-29_20-10-56.zip (203.1 KB)

WayneWWW · September 30, 2023, 4:12am

If you see any “Waiting for target to boot-up…”, during flash, then you need to dump the serial console log from device.

And sdkmanager by default does not support custom board.

jose41 · October 2, 2023, 9:31am

Hello,

Please find here the console log:

log_during_flash_orinnx.txt (39.6 KB)

Any suggestion please?

WayneWWW · October 2, 2023, 9:35am

It is a common mistake for custom board to get flashed by sdkmanager.

Please refer to doc:

https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonOrinNxNanoSeries.html#eeprom-modifications

jose41 · October 2, 2023, 10:11am

Thanks, The custom board is very similar to dev kitn the only different is we have an extra ethernet interfaced by a Ethernet - PCIe bridge.

I want to try flash script (in Jetpack 5.1.1) like this (I am not sure about the used config file).
sudo ./flash.sh jetson-orin-nano-devkit-nvme external

Here there is the log of host console and Orin NX serial console:

log_using_script_flash.txt (82.6 KB)

log_serial_console_using_script_flash.txt (23.2 KB)

Any idea?

Thanks in advance

WayneWWW · October 2, 2023, 10:53am

Hi,

This comment does not matter. The point here is your custom board does not have a eeprom so that you have to disable it to pass the flash.

Thanks, The custom board is very similar to dev kitn the only different is we have an extra ethernet interfaced by a Ethernet - PCIe bridge.

flash.sh cannot flash orin nano and orin nx. Please refer to this document to check how to initrd flash to flash the board.
Quick Start — Jetson Linux Developer Guide documentation

jose41 · October 2, 2023, 3:20pm

Thanks, sorry about the missunderstanding. I tried this time with initrd_flash, it is not clear for me if I still need to deactivate EEPROM check with initrd_flash.

I tried the following steps according to the documentation (Quick Start — Jetson Linux Developer Guide documentation) :

$ tar xf ${L4T_RELEASE_PACKAGE}
$ sudo tar xpf ${SAMPLE_FS_PACKAGE} -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./apply_binaries.sh
$ sudo ./tools/l4t_flash_prerequisites.sh

$ 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 custom_board nvme0n1p1

I obtained the following output:
cmd_output_initrd_flash.txt (217.7 KB)

And this is the output of serial console:
serial_console_initrd_flash.txt (4.3 KB)

The custom_board.conf file contents:

source “${LDK_DIR}/p3768-0000+p3767-0000.conf”;
unset -f process_board_version

EMMC_CFG=“flash_t234_qspi_nvme.xml”;

Regards

WayneWWW · October 2, 2023, 3:54pm

Hi,

Yes, you still need to deactivate EEPROM. If your board does not have this thing, then you need to do that. Default BSP only has software for devkit case. If your carrier board is different, then you must apply corresponding software patch.
Please also tell me what you are doing, what files did you modify in case you did it wrong.
Please clarify what is the content of “custom_board.conf”. I think you could directly use jetson-orin-nano-devkit first instead of your own board config in case you did something wrong.

WayneWWW · October 2, 2023, 3:57pm

Also, do you have NV devkit on your side so that you could practice how to flash the board first?

system · October 16, 2023, 3:58pm

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.