Xavier NX wont boot, sdkmanager hangs up while trying to flash

logs.txt (5.0 KB)
Xavier NX won’t boot. when plugged in the green light turns on, fan remains off while the board gets hot. Nothing shows up on the computer monitor. I tried using the sdkmanager to install but the system fails at the flashing step. The last line on the console states, “CPU Bootloader is not running on device.”

Any help and guidance will be greatly appreciated!

Thanks!

There is a “export button” on the sdkm GUI. Use that to dump the whole log and attach it here.

SDKM_logs_2021-09-29_22-48-08.zip (483.9 KB)
Thanks!

Your first comment does not match the result of this full log.

Your flash result in jetpack4.4 gives

###############################################################################
# L4T BSP Information:
# R32 , REVISION: 4.3
###############################################################################
Error: probing the target board failed.
       Make sure the target board is connected through 
       USB port and is in recovery mode.

And your jetpack4.6 gives below.

**********************
Info: exec_command: /tmp/tmp_NV_L4T_FLASH_XAVIER_NX_WITH_OS_IMAGE_COMP.sh
sudo ./nvautoflash.sh
*** Checking ONLINE mode ... OK.
*** Checking target board connection ... 1 connections found.
*** Reading ECID ... *** Error: ECID read failed.
Put the target board in RCM mode and retry.

Thanks for the reply. I saw that in the logs as well but it doesn’t make sense because the sdkmanager only detects the xavier when I put a jumper cap on pins 9 and 10 (J14). I’m using the barrel power connector and power plug provided with the kit and a usb micro B to usb A to connect to the host computer running Ubuntu 18. I tried installing jetpack 4.6 and went down to 4.4 but both fail when it gets to the flash portion of the install.

  1. Is your ubuntu 18 a virtual machine?
  2. Are you sure the micro B cable here has a data line but not only just a usb charging cable?
  3. Do you have experience of flashing any other jetson platforms?

SDKM_logs_JetPack_4.6_(rev.1)Linux_for_Jetson_Xavier_NX[developer_kit_version]_2021-09-30_08-14-11.zip|attachment (95.2 KB)
Here is another log file after I started everything all over again and also changed the usb port on the host.

To answer your question:

  1. ubuntu is running natively
  2. the usb cable is a data line
  3. No, I haven’t flashed jetson platforms before

Can you directly

  1. Use your method that you think is correct to put the board into recovery mode.

  2. Go to /home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra

  3. Run the command “sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1”.
    (if your board is emmc one, use jetson-xavier-nx-devkit-emmc instead)

  4. Share the result.

rnowrang@rnowrang-MS-7C02:~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 0955:7e19 NVidia Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 046d:0893 Logitech, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1b1c:1b5a Corsair
Bus 001 Device 002: ID 1b1c:1b3d Corsair
Bus 001 Device 004: ID 1e71:2006 NZXT
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
rnowrang@rnowrang-MS-7C02:~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra$ sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 6.1

###############################################################################

Target Board Information:

Name: jetson-xavier-nx-devkit, Board Family: t186ref, SoC: Tegra 194,

OpMode: production, Boot Authentication: NS,

Disk encryption: disabled ,

###############################################################################
copying soft_fuses(/home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)… done.
./tegraflash.py --chip 0x19 --applet “/home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod.bin” --skipuid --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins “mb2_applet nvtboot_applet_t194.bin” --cmd “dump eeprom boardinfo cvm.bin;reboot recovery”
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.0019 ] Generating RCM messages
[ 0.0033 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader /home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod.bin zerosbk
[ 0.0040 ] Header already present for /home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod.bin
[ 0.0079 ]
[ 0.0101 ] tegrasign_v3.py --getmode mode.txt --key None
[ 0.0102 ] Assuming zero filled SBK key
[ 0.0124 ] tegrasign_v3.py --file /home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin --key None --length 1136 --offset 2960 --pubkeyhash pub_key.key
[ 0.0125 ] Assuming zero filled SBK key
[ 0.0216 ] tegrahost_v2 --chip 0x19 0 --updatesigheader /home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin /home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.hash zerosbk
[ 0.0247 ]
[ 0.0271 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg.pdf sfuse.bin
[ 0.0290 ]
[ 0.0308 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x19 0 --sfuses sfuse.bin --download rcm /home/rnowrang/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin 0 0
[ 0.0313 ] RCM 0 is saved as rcm_0.rcm
[ 0.0346 ] RCM 1 is saved as rcm_1.rcm
[ 0.0347 ] RCM 2 is saved as rcm_2.rcm
[ 0.0347 ] List of rcm files are saved in rcm_list.xml
[ 0.0347 ]
[ 0.0347 ] Signing RCM messages
[ 0.0368 ] tegrasign_v3.py --getmontgomeryvalues montgomery.bin --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0368 ] Assuming zero filled SBK key
[ 0.0423 ] Copying signature to RCM mesages
[ 0.0440 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[ 0.0452 ]
[ 0.0453 ] Boot Rom communication
[ 0.0471 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0476 ] RCM version 0X190001
[ 0.0485 ] Boot Rom communication completed
[ 1.0638 ]
[ 2.0682 ] tegrarcm_v2 --isapplet
[ 2.0693 ] Applet version 01.00.0000
[ 2.0709 ]
[ 2.0731 ] tegrarcm_v2 --ismb2
[ 2.0936 ]
[ 2.0948 ] tegrahost_v2 --chip 0x19 --align nvtboot_applet_t194.bin
[ 2.0989 ]
[ 2.1011 ] tegrahost_v2 --chip 0x19 0 --magicid PLDT --appendsigheader nvtboot_applet_t194.bin zerosbk
[ 2.1019 ] adding BCH for nvtboot_applet_t194.bin
[ 2.1044 ]
[ 2.1073 ] tegrasign_v3.py --key None --list nvtboot_applet_t194_sigheader.bin_list.xml --pubkeyhash pub_key.key
[ 2.1074 ] Assuming zero filled SBK key
[ 2.1115 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_sigheader.bin.encrypt nvtboot_applet_t194_sigheader.bin.hash zerosbk
[ 2.1134 ]
[ 2.1153 ] tegrarcm_v2 --download mb2 nvtboot_applet_t194_sigheader.bin.encrypt
[ 2.1161 ] Applet version 01.00.0000
[ 2.1377 ] Sending mb2
[ 2.1378 ] […] 100%
[ 2.1526 ]
[ 2.1548 ] tegrarcm_v2 --boot recovery
[ 2.1554 ] Applet version 01.00.0000
[ 2.1771 ]
[ 3.1813 ] tegrarcm_v2 --isapplet
[ 1008.7689 ]
[ 1008.7715 ] tegrarcm_v2 --ismb2
[ 2024.5770 ]
[ 2024.5837 ] tegradevflash_v2 --iscpubl
[ 2024.5851 ] CPU Bootloader is not running on device.
[ 3040.3882 ]
[ 3041.3925 ] tegrarcm_v2 --isapplet
[ 4056.1929 ]
[ 4056.1962 ] tegrarcm_v2 --ismb2

Please follow this guide to dump the serial console log in the meantime you run the flash.sh command. I am wondering what happened on device side.

I got the magic wire cable and connected the xavier nx to the computer and the boot process freezes after the following code:

[0000.024] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet lev.
[0000.033] I> MB1 (prd-version: 1.5.1.3-t194-41334769-d2a21c57)
[0000.038] I> Boot-mode: Coldboot
[0000.041] I> Chip revision : A02P
[0000.044] I> Bootrom patch version : 15 (correctly patched)
[0000.049] I> ATE fuse revision : 0x200
[0000.053] I> Ram repair fuse : 0x0
[0000.056] I> Ram Code : 0x0
[0000.058] I> rst_source : 0x0
[0000.061] I> rst_level : 0x0
[0000.065] I> Boot-device: QSPI
[0000.067] I> Qspi flash params source = brbct
[0000.071] I> Qspi using bpmp-dma
[0000.074] I> Qspi clock source : pllp
[0000.078] I> QSPI Flash Size = 32 MB
[0000.081] I> Qspi initialized successfully
[0000.085] W> No valid slot number is found in scratch register
[0000.091] W> Return default slot: _a
[0000.094] I> Active Boot chain : 0
[0000.097] I> Boot-device: QSPI
[0000.100] I> Qspi flash params source = brbct
[0000.106] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.113] I> Temperature = 20000
[0000.116] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.121] W> Skipping boost for clk: BPMP_APB
[0000.125] W> Skipping boost for clk: AXI_CBB
[0000.129] W> Skipping boost for clk: AON_CPU_NIC
[0000.133] W> Skipping boost for clk: CAN1
[0000.137] W> Skipping boost for clk: CAN2
[0000.141] !!! Exception !!! [lr:0x40020bf8, dfar:0x2212a8c, dfsr:0x1808]
[0000.147] I> MB1(1.5.1.3-t194-41334769-d2a21c57) BIT boot status dump :
00000000000111111111101111111111100000000000000000000000000000000000000000000000

Was this jetson NX ever running before?

yes it was. When I try to run the flash.sh, this is the error I get:

rnowrang@rnowrang-MS-7C02:~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra$ sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 6.1

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.
rnowrang@rnowrang-MS-7C02:~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra$

Can you try to read what is the error log you just shared here?

Not every error is same, ok?

that is all the text that prints out on the terminal when I run flash.sh

That was not what you said in 9/30.

Anyway, whatever that log is. I think this is hardware problem.

If you have other NX device, you can use it to validate your host setup. Please RMA this problematic module.

Here are the steps I took:

  1. I connected the nx to the computer with the magic wire.
  2. started minicom on the terminal.
  3. put the jumper cap on pins 9 and 10 to boot in recovery mode.
  4. plugged in the power cable in the barrel connector.
  5. Ran the flash.sh script

As soon as I run the flash script the following is the only text that prints out in my terminal:

rnowrang@rnowrang-MS-7C02:~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra$ sudo ./flash.sh jetson-xavier-nx-devkit mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 6.1

###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
USB port and is in recovery mode.

This means the flash is not starting at all. In 9/30, your board was still able to start the flash.

Did you remember to plug the micro usb cable? It is a silly question but I don’t see you said you connect it.

Do you think the problem is with the module or the carrier board?