Fail to flash orin nx with custom carrie board

I am using the Jetpack 6.2 SDK to flash the Orin NX core board. When I use the devkit, it can be flashed normally. However, when I use the customized carrier board, it stops at booting into RCM mode. Our carrier board completely follows the devkit design for the USB part for flashing.

The flashing command I am using is:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit-super internal

The log printed by the flashing terminal is as follows:

Entering RCM boot

[ 0.0290 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[ 0.0291 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[ 0.0291 ] rcm boot with presigned binaries
[ 0.0295 ] tegrarcm_v2 --instance 3-1 --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.0298 ] BR_CID: 0x80012344705DF3C95000000001FF81C0
[ 0.0384 ] Sending bct_br
[ 0.0472 ] Sending mb1
[ 0.0478 ] Sending psc_bl1
[ 0.0583 ] Sending bct_mb1
[ 0.0650 ] Generating blob for T23x
[ 0.0664 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[ 0.0668 ] The number of images in blob is 19
[ 0.0673 ] blobsize is 100081089
[ 0.0674 ] Added binary blob_uefi_jetson_minimal_with_dtb_sigheader.bin.encrypt of size 2043968
[ 0.1239 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 310768
[ 0.1246 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 187120
[ 0.1251 ] Added binary blob_tsec_t234_sigheader.bin.encrypt of size 176128
[ 0.1254 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 279808
[ 0.1258 ] Not supported type: mb2_applet
[ 0.1259 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 440944
[ 0.1264 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[ 0.1267 ] Added binary blob_nvpva_020_sigheader.fw.encrypt of size 2164640
[ 0.1276 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 12070576
[ 0.1374 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[ 0.1400 ] Added binary blob_bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt of size 1027008
[ 0.1409 ] Added binary blob_tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sigheader.dtb.encrypt of size 383296
[ 0.1415 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 458096
[ 0.1420 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 415008
[ 0.1424 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[ 0.1429 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1887312
[ 0.1434 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[ 0.1439 ] Added binary blob_boot0.img of size 77246464
[ 0.1997 ] Added binary blob_tegra234-p3768-0000+p3767-0000-nv.dtb of size 249505
[ 0.2687 ] tegrarcm_v2 --instance 3-1 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 0.2691 ] BL: version 1.4.0.4-t234-54845784-e89ea9bc last_boot_error: 0
[ 0.3260 ] Sending bct_mem
[ 0.3379 ] Sending blob
[ 4.6421 ] RCM-boot started

/home/platform/nvidia/nvidia_sdk/JetPack_6.2_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…
Timeout
Device failed to boot to the initrd flash kernel. Please retrive the serial log during flashing to debug further.
Cleaning up…

The serial port output log is as follows:
serial.txt (25.2 KB)

May I ask what could be the reason that the BL cannot enter RCM boot mode? Does the EEPROM on the Carrie board need to be programmed with additional firmware?
Please guide me if there is any issue with the operation. Thank you!

Hi,

The situation of this post is more like you didn’t dump the log correctly but not related to why BL cannot enter RCM boot mode yet.

I only saw you posted some parital logs that got grep or truncated by you and came back to ask why it cannot enter RCM boot.
Why should we know that? You should provide full logs.

Hi

Here are the full logs.
carrier_flash.log (309.3 KB)
serial_log.txt (42.3 KB)

Actually, the serial log stop at “JetsonMinimal UEFI firmware (version 36.4.3-gcid-38968081 b▒”

Your boot mode is already in RCM boot. It just stuck in UEFI.

You could enable full UEFI log by rebuild UEFI binary and it will tell why it got stuck.

I just found the cmd to flash miniUEFI for AGX:

$ sudo ADDITIONAL_DTB_OVERLAY=“BootOrderEmmc.dtbo” ./flash.sh jetson-agx-orin-devkit internal

How can I flash the miniUEFI for Orin NX with nvme ?

The command you posted didn’t flash miniUEFI either… I really don’t know what you are trying to ask here.

Also, it seems not related to your original question either…

請問如果用中文跟你說明你會清楚一點嗎? 感覺你問的問題很發散, 沒有很進入狀況的感覺.

我编译了minuUEFI, 然后想要烧录它。我在文档上看到只有agx的教程。我想知道如何Orin NX如何烧录mini UEFI。

先確認一下. 所以你的板子在使用正常的UEFI情況下是能燒的嗎?

使用配套的devkit 开发板是可以正常烧录的。使用我们自己做的carrier board烧录时会出现上述的问题。

ok. 那能否先討論正常UEFI在你們開發板的狀況… 你現在不應該增添額外的變因..

通过devkit开发板烧录好的Orin nx模组放到我们自己的板子上可以正常启动和工作,看起来一切都是正常的。只有使用我们自己的板子进行烧录时,会出现问题。

還是請你先使用UEFI debug build進行燒錄. 我們再來看到底是卡在哪裡

你說的這些只代表這問題在RCM boot會發生. 其餘要確認還是得靠debug build.

你好,我拉取了edk2-nvidia的代码,但是其中没有文档 UEFI Adaptation — NVIDIA Jetson Linux Developer Guide中所说的edk2-nvidia/Platform/NVIDIA/JetsonMinimal/build.sh目录。
只有edk2_docker edk2-nvidia/Platform/NVIDIA/Tegra/build.sh文件用于编译tegra设备的UEFI。
请问是我拉取的edkrepo仓库有问题,还是文档没有更新?使用 edk2-nvidia/Platform/NVIDIA/Tegra/build.sh编译的文件可以使用吗?
Build without docker · NVIDIA/edk2-nvidia Wiki · GitHub

Your question has nothing to do with the debug here.. Please just focus on building the original UEFI.
I mean please do not use any mini UEFI at all…

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