Orin nx qspi flash error - NV3P_SERVER: Failed to initialize partition table from GPT

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

Hello
We have a problem flashing some Orin NX modules more then once.

The error is:
[ 9.3332 ] Start flashing
[ 9.3367 ] tegradevflash_v2 --pt flash.xml.bin --create
[ 9.3374 ] Bootloader version 01.00.0000
[ 9.3418 ] Erasing spi: 0 … [Done]
[ 10.3510 ] Writing partition secondary_gpt with gpt_secondary_3_0.bin [ 16896 bytes ]
[ 10.3525 ] […] 100%
[ 10.3562 ] 000000004d4d2c01: E> NV3P_SERVER: Failed to initialize partition table from GPT.

It seems to be and old issue that might not have been solved:

bug-flash-gpt.log (68.1 KB)

Looks like after the first flash, the qspi is locked for writing somehow.
Jetpack is 6.2 using Orin NX.
Our current (not nice) sollution is to flash on an un-bugged OrinNX, then transferring the nvme to a bugged (but flashed once) module.

Full flash log attached.

thanks.

5

Hi,

Please provide the serial console log for us to review.

Thanks

6

adding console log
I should add that the crash is on the qspi erasing part.
It’s says ‘done’ on the flash log, (Erasing spi: 0 … [Done]) but it’s not.
bug-flash-qspi-console.log (29.4 KB)

7

Hi David.
Log added

8

tried also this part-of-flash command:
Linux_for_Tegra/bootloader: bash -x ./flashcmd.txt

  • ./tegraflash.py --bl uefi_jetson_minimal_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --bldtb tegra234-p3768-0000+p3767-0000-nv.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_
    1_encrypt.rcm --cmd ‘secureflash;reboot’ --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_b
    oot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sighea
    der.bct.encrypt --bins ‘psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; tsec_fw tsec_t234_sigheader.bin.encrypt; mb2_applet applet_t234_si
    gheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; pva_fw nvpva_020_sigheader.fw.encrypt; dce_fw display-t234
    -dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sig
    header.dtb.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt
    ; eks eks_t234_sigheader.img.encrypt’ --bct_backup
    Welcome to Tegra Flash
    version 1.0.0
    Type ? or help for help and q or quit to exit
    Use ! to execute system commands

[ 0.0170 ] Parsing partition layout
[ 0.0174 ] tegraparser_v2 --pt secureflash.xml.tmp
[ 0.0204 ] Parsing partition layout
[ 0.0209 ] tegraparser_v2 --pt secureflash.xml.tmp
[ 0.0219 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[ 0.0219 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[ 0.0219 ] Boot Rom communication
[ 0.0222 ] tegrarcm_v2 --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_al
igned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 0.0225 ] BR_CID: 0x80012344705DE7DD1400000017000280
[ 0.0235 ] Sending bct_br
[ 0.0236 ] Sending mb1
[ 0.0244 ] Sending psc_bl1
[ 0.0359 ] Sending bct_mb1
[ 0.0425 ] Boot Rom communication completed
[ 0.0426 ] Generating blob for T23x
[ 0.0454 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[ 0.0459 ] Stat for blob_display-t234-dce_sigheader.bin.encrypt failed
Error: Return value 19
Command tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin

9

Hi Noam, I’ve got some suggestions that may help:
A. Try repairing exclusively the QSPI with the following command:

sudo ./flash.sh -c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg <your-board-id> internal

This should reprogram only the QSPI without flashing. If it writes partitions successfully after the [ 9.3418 ] Erasing spi: 0 … [Done] log line, then you can flash normally using the initrd flash script instead of the plain one:

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 --no-systemimg" --network usb0 <your-board-name> external

B. If you still see the same issue after reprogramming the QSPI:

[ 10.3510 ] Writing partition secondary_gpt with gpt_secondary_3_0.bin [ 16896 bytes ]
[ 10.3525 ] […] 100%
[ 10.3562 ] 000000004d4d2c01: E> NV3P_SERVER: Failed to initialize partition table from GPT.
Reboot the board, enter in recovery mode and try directly with the same initrdflash script. If neither work, please save the UART and flashing logs and share them please.

Hope this is useful!

Fabian Munoz
Embedded SW Engineer at RidgeRun**

Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com

10

Hello Fabian, thanks for the answer.
The first ‘flash.sh’ command (with changes) failed on the same error.
The second ‘l4t_initrd_flash.sh’ (with changes) worked up to having the Orin boot to initrd shell state, which is fine because the qspi rewriting worked fine!
That’s was the command to fit Jetpack6.2 with our setup:
./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_nvme.xml --no-systemimg” --network usb0 --showlogs jetson-orin-nano-devkit-super-maxn-nvme external

Now the full flash procedure works fine.
Thank U very much