Can't flash Jetson Xavier NX board

We just received two new Jetson Xavier NX’s are are trying to flash it using the standard Jetson Flash Tools. Both terminal outputs freeze at tegrarcm_v2 --isapplet when trying to flash the boards. The output before it freezes looks like the output below.

[ 8.6166 ]
[ 8.6193 ] tegrahost_v2 --chip 0x19 --generateblob blob.xml blob.bin
[ 8.6203 ] number of images in blob are 11
[ 8.6205 ] blobsize is 6293480
[ 8.6206 ] Added binary blob_nvtboot_recovery_cpu_t194_sigheader.bin.encrypt of size 238144
[ 8.6228 ] Added binary blob_nvtboot_recovery_t194_sigheader.bin.encrypt of size 173216
[ 8.6232 ] Added binary blob_preboot_c10_prod_cr_sigheader.bin.encrypt of size 24016
[ 8.6237 ] Added binary blob_mce_c10_prod_cr_sigheader.bin.encrypt of size 145184
[ 8.6240 ] Added binary blob_mts_c10_prod_cr_sigheader.bin.encrypt of size 3430416
[ 8.6245 ] Added binary blob_bpmp-2_t194_sigheader.bin.encrypt of size 1007392
[ 8.6276 ] Added binary blob_tegra194-a02-bpmp-p3668-a00_sigheader.dtb.encrypt of size 391920
[ 8.6283 ] Added binary blob_spe_t194_sigheader.bin.encrypt of size 95232
[ 8.6286 ] Added binary blob_tos-optee_t194_sigheader.img.encrypt of size 525232
[ 8.6289 ] Added binary blob_eks_sigheader.img.encrypt of size 5136
[ 8.6291 ] Added binary blob_tegra194-p3668-0001-p3509-0000_sigheader.dtb.encrypt of size 257408
[ 8.6358 ]
[ 8.6359 ] Sending bootloader and pre-requisite binaries
[ 8.6410 ] tegrarcm_v2 --download blob blob.bin
[ 8.6436 ] Applet version 01.00.0000
[ 8.7273 ] Sending blob
[ 8.7274 ] […] 100%
[ 9.6078 ]
[ 9.6112 ] tegrarcm_v2 --boot recovery
[ 9.6120 ] Applet version 01.00.0000
[ 9.6913 ]
[ 10.6968 ] tegrarcm_v2 --isapplet

We have flashed many Jetsons with these tools and don’t have this problem with any of them. I am using an Ubuntu 20.04 and I have tried many different versions of the flash tools only to arrive at the same problem with these particular boards.

Please help me troubleshoot this problem. Could there be a new hardware update that is causing this issue?

Does this ubuntu 20.04 indicate you are flashing jetpack5.x? Or you are still falshing jp 4.x but with some hack to make 20.04 able to flash?

What do you mean by jetpack? Is that the drivers? We download the L4T Driver Package (BSP) and Sample Root Filesystem separately, untar them and apply binaries (downloaded from L4T Archive | NVIDIA Developer). We usually use 32.7.2 version however on these jetsons I’ve tried everything between 32.6.1 and 34.1.1

Yes, the jetpack means the BSP. Please also dump the uart log from the device.

Also, is this on devkit or your custom board?

Could you send me a resource for how to get the uart log?

We are using NVIDIA Jetson Xavier NX Developer Kit

Here is the UART log while in recovery mode

[0024.005] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[0024.013] I> MB1 (prd-version: 2.2.0.0-t194-41334769-3540ffaa)
[0024.019] I> Boot-mode: Platform RCM
[0024.022] I> Platform: Silicon
[0024.025] I> Chip revision : A02P
[0024.028] I> Bootrom patch version : 15 (correctly patched)
[0024.033] I> ATE fuse revision : 0x200
[0024.037] I> Ram repair fuse : 0x0
[0024.040] I> Ram Code : 0x0
[0024.042] I> rst_source: 0x0, rst_level: 0x0
[0024.047] I> USB configuration success
[0026.289] I> mb2 image downloaded
[0026.374] I> Recovery boot mode 0
[0026.379] I> UPHY full init done
[0026.386] I> MB1 done

[0026.391] I> Welcome to MB2(TBoot-BPMP) Applet (version: default.t194-mobile-a1105112)
[0026.399] I> DMA Heap @ [0x40020000 - 0x40065800]
[0026.403] I> Default Heap @ [0xd486400 - 0xd48a400]
[0026.408] W> Profiler not initialized
[0026.412] E> Error in command_complete 18000 int_status
[0026.417] E> OCR failed, error = f0f0706
[0026.421] I> SDMMC is not present.
[0026.426] I> QSPI-0l initialized successfully
[0026.433] E> CLK_RST: instance 6 not found in module 44.
[0026.438] E> MPhy CAR configuration failed error = 1747992077
[0026.444] E> UFS initialization failed
[0026.447] I> UFS is not present
[0026.452] I> Found 47 partitions in QSPI_FLASH (instance 0)
[0026.457] W> Profiler not initialized
[0026.460] I> Entering 3p server
[0026.464] I> USB configuration success
[0027.757] I> Populate chip info
[0027.849] I> Populate eeprom info
[0027.853] I> Populate eeprom info for module cvm
[0027.858] > DEVICE_PROD: device prod is not initialized.
[0028.064] I> Rebooting : reboot-recovery

[0028.069] I> Reset to recovery mode
��
[0035.420] W> RATCHET: MB1 binary ratchet value 4 is larger than ratchet level 2 from HW fuses.
[0035.428] I> MB1 (prd-version: 2.2.0.0-t194-41334769-3540ffaa)
[0035.433] I> Boot-mode: RCM
[0035.436] I> Platform: Silicon
[0035.439] I> Chip revision : A02P
[0035.442] I> Bootrom patch version : 15 (correctly patched)
[0035.447] I> ATE fuse revision : 0x200
[0035.450] I> Ram repair fuse : 0x0
[0035.453] I> Ram Code : 0x0
[0035.456] I> rst_source: 0xb, rst_level: 0x1
[0035.461] I> USB configuration success
[0037.597] I> bct_bootrom image downloaded
[0037.606] W> PROD_CONFIG: device prod data is empty in MB1 BCT.
[0037.613] I> Temperature = 28500
[0037.616] W> Skipping boost for clk: BPMP_CPU_NIC
[0037.621] W> Skipping boost for clk: BPMP_APB
[0037.625] W> Skipping boost for clk: AXI_CBB
[0037.629] W> Skipping boost for clk: AON_CPU_NIC
[0037.633] W> Skipping boost for clk: CAN1
[0037.637] W> Skipping boost for clk: CAN2
[0037.641] I> Boot-device: QSPI (instance: 0)
[0037.645] I> Qspi flash params source = mb1bct
[0037.649] I> bct_mb1 image downloaded
[0037.659] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0037.667] W> Thermal config not found in BCT
[0037.675] W> MEMIO rail config not found in BCT
[0037.685] I> bct_mem image downloaded
[0038.972] I> blob image downloaded
[0039.056] I> Recovery boot mode 0
[0039.100] W> Platform config not found in BCT
[0039.133] I> MB1 done

����main enter
SPE VERSION #: R01.00.18 Created: Jan 29 2021 @ 14:18:27
HW Function test
Start Scheduler.
in late init
��
[0039.143] I> Welcome to MB2(TBoot-BPMP) Recovery (version: default.t194-mobile-ded99dd3)
[0039.144] I> DMA Heap @ [0x526fa000 - 0x52ffa000]
[0039.144] I> Default Heap @ [0xd486400 - 0xd48a400]
[0039.146] E> DEVICE_PROD: Invalid value data = 70020000, size = 0.
[0039.151] W> device prod register failed
[0039.165] I> Relocating BR-BCT
[0039.167] > DEVICE_PROD: device prod is not initialized.
[0039.220] I> Relocating OP-TEE dtb from: 0x6bfffd40 to 0x70050000, size: 703
[0039.221] I> [0] START: 0x80000000, SIZE: 0x47c00000
[0039.221] I> dram_block larger than 80000000
[0039.222] I> [1] START: 0x100000000, SIZE: 0x180000000
[0039.224] I> Setting NS memory ranges to OP-TEE dtb finished.
[0039.362] I> EKB detected (length: 0x410) @ VA:0x526fa200
[0039.364] I> Setting EKB blob info to OPTEE dtb finished.
��NOTICE: BL31: v2.5(release):ef8af0b99
NOTICE: BL31: Built : 20:57:59, May 16 2022
I/TC:
��
bpmp: init
bpmp: tag is 128431eec76692047e1ac1ebc0392266
sku_dt_init: not sku 0x00
��I/TC: Non-secure external DT found
��clk_early initialized
mail_early initialized
fuse initialized
hwwdt initialized
t194_ec_get_ec_list: found 45 ecs
ec initialized
vmon_setup_monitors: found 3 monitors
vmon initialized
adc initialized
fmon_populate_monitors: found 73 monitors
fmon initialized
mc initialized
reset initialized
nvhs initialized
uphy_early initialized
emc_early initialized
392 clocks registered
clk initialized
io_dpd initialized
thermal initialized
thermal_mrq initialized
i2c initialized
vrmon_dt_init: vrmon node not found
vrmon_chk_boot_state: found 0 rail monitors
vrmon initialized
regulator initialized
��I/T��avfs_clk_platform initialized
��C: OP-TEE v��soctherm initialized
��er��aotag initialized
��si��powergate initialized
��on: 6f444acf (gcc version 9.3.0 (Buildroot 2020.08)) #2 Tue May 17 04:00:18 UTC 2022 aarch64
I/TC: Primary CPU initializing
��dvs initialized
pm initialized
suspend initialized
pg_late initialized
pg_mrq_init initialized
strap initialized
nvl initialized
emc initialized
emc_mrq initialized
clk_dt initialized
tj_init initialized
/uphy is not enabled status = disabled
uphy_dt initialized
uphy_mrq initialized
uphy initialized
ec_swd_poll_start: 281 reg polling start w period 47 ms
ec_late initialized
hwwdt_late initialized
reset_mrq initialized
ec_mrq initialized
fmon_mrq initialized
clk_mrq initialized
avfs_mrq initialized
mail_mrq initialized
i2c_mrq initialized
tag_mrq initialized
console_mrq initialized
mrq initialized
clk_sync_fmon_post initialized
clk_dt_late initialized
noc_late initialized
pm_post initialized
dbells initialized
dmce initialized
cvc initialized
avfs_clk_mach_post initialized
avfs_clk_platform_post initialized
cvc_late initialized
regulator_post initialized
rm initialized
console_late initialized
clk_dt_post initialized
mc_reg initialized
pg_post initialized
profile initialized
fuse_late initialized
extras_post initialized
bpmp: init complete
entering main console loop
] ��I/TC: Primary CPU switching to normal world boot
��
[0039.869] I> Welcome to TBoot-CPU Recovery
[0039.870] I> Heap: [0xa0f00000 … 0xa9f00000
[0039.870] I> gpio framework initialized
[0039.881] I> tegrabl_gpio_driver_register: register ‘nvidia,tegra194-gpio’ driver
[0039.887] I> tegrabl_gpio_driver_register: register ‘nvidia,tegra194-gpio-aon’ driver
[0039.887] I> tegrabl_tca9539_init: i2c bus: 1, slave addr: 0x46
[0039.894] W> fetch_driver_phandle_from_dt: failed to get node with compatible ti,tca9539
[0039.901] W> fetch_driver_phandle_from_dt: failed to get node with compatible nxp,tca9539
[0039.901] W> tegrabl_tca9539_init: failed to fetch phandle from dt
[0039.902] I> tegrabl_tca9539_init: i2c bus: 1, slave addr: 0x44
[0039.911] W> fetch_driver_phandle_from_dt: failed to get node with compatible ti,tca9539
[0039.919] W> fetch_driver_phandle_from_dt: failed to get node with compatible nxp,tca9539
[0039.921] W> tegrabl_tca9539_init: failed to fetch phandle from dt
[0039.932] I> fixed regulator driver initialized
[0040.120] I> CPU: Nvidia Carmel
[0040.121] I> CPU: MIDR: 0x4e0f0040, MPIDR: 0x80000000
[0040.121] I> Platform: Silicon
[0040.121] I> chip revision : A02P
[0040.122] I> Boot_device: QSPI_FLASH instance: 0
[0040.122] I> qspi flash-0 params source = boot args
[0040.123] I> QSPI source rate = 204000 Khz
[0040.123] I> Requested rate for QSPI clock = 12000 Khz
[0040.128] I> BPMP-set rate for QSPI clk = 12000 Khz
[0040.133] I> QSPI-0l initialized successfully
[0040.136] I> sdmmc-3 params source = safe params
[0040.525] E> Error in command_complete 18000 int_status
[0040.525] E> OCR failed, error = f0f0706
[0040.526] E> Failed to open sdmmc-3, err = f0f0706
[0040.526] E> Failed to initialize device 1-3
[0040.526] E> Top caller module: SDMMC, error module: SDMMC, reason: 0x06, aux_info: 0x07
[0040.527] I> TBoot-CPU Recovery hang

What is the command you are using on your host to flash your board?

The command is

sudo ./flash.sh jetson-xavier-nx-devkit-emmc external

Is your board a jetson NX module with sdcard slot on the module or not?

This is what the back of the board looks like

What we typically do is flash our own SSD with an image. We loosen the screw on the back and then put our SSD there. This is a separate step to flashing the board however.

Could we send these Jetsons back to Nvidia under an RMA?

Hi,

I think you didn’t get my point. There are two kinds of modules. One module is using emmc to boot and another module is using sdcard to boot. It does not matter with your SSD.

If your module is sdcard kind, then you cannot use jetson-xavier-nx-devkit-emmc to flash…

Also, I am asking for module, not the back of your carrier board…

Are you new user to jetson? The carrier board and module are separate components…

I am a new user to jetson however my team is very experienced and they have the same issues with these boards.

We never have sd card slots in our boards. We always order the same boards and flash them the same way with that command. It has worked in every other board we have ordered of this model.

Please let me know what you’d like to proceed with the issue. Perhaps we could set up a call. I can have someone from my team who is experienced with the boards join a meeting if that is what you require.

Hi,

Ok, can I get a confirmed answer that all the modules you ordered are emmc module?

If you are not sure, could you ask your team member to confirm this? Also, did you test this on devkit or custom board?

Sorry that there won’t be a call here. Please just reply the answer on forum.

Yes it is a emmc module and devkit

Ok, the reason why I asked this question is because your log says the emmc cannot be opened during flash.

If you are sure this is emmc module, then please RMA it.

Who can I contact to return these modules

Please check with RMA request here or contact your local seller.