Jetson Xavier AGX 32GB flashing fails

Hello!
We bought a new Jetson AGX 32GB dev kit in December 2020. Unfortunately, we are not able to flash it.
File system and OS creation is successful, but flashing always fails /never started at all.

The latest SDK-Manager was used, the device is in Force Recovery Mode.

lsusb shows:
Bus 001 Device 015: ID 0955:7019 NVidia Corp.

Copy from terminal log:


11:21:39 SUMMARY: File System and OS: Install completed successfully.
11:21:39 INFO: Start to check if only one device connected…


11:21:40 INFO: Only one NVIDIA device detected, as expected.
11:21:40 INFO: Start to check if in device recovery mode…


11:21:40 INFO: Jetson device is in recovery mode.
11:21:40 INFO: Start to check if the right device connected…


11:21:40 DEBUG: running command < lsusb | grep 0955:7019 >
11:21:40 INFO: Bus 001 Device 012: ID 0955:7019 NVidia Corp.
11:21:40 INFO: command finished successfully
11:21:40 INFO: Verified, 0955:7019 detected in recovery mode.
11:21:40 DEBUG: running command < true >
11:21:40 INFO: command finished successfully
11:21:40 DEBUG: Device Mode Host Setup in Flash: using adapter to install NV_DEVICE_MODE_SETUP_IMAGE_COMP@JETSON_AGX_XAVIER to
11:21:40 INFO: Device Mode Host Setup in Flash: Found route default wlo1, setting up device mode
11:21:40 INFO: Device Mode Host Setup in Flash: net.ipv4.ip_forward = 1
11:21:40 INFO: Device Mode Host Setup in Flash: Device mode on host successfuly set with DNS 8.8.8.8!
11:21:40 INFO: Device Mode Host Setup in Flash: command finished successfully
11:21:40 SUMMARY: Device Mode Host Setup in Flash: Install completed successfully.
11:21:40 DEBUG: running command < true >
11:21:40 INFO: command finished successfully
11:21:40 DEBUG: Flash Jetson AGX Xavier 16GB/32GB: using adapter to install NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER to
11:21:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: exec_command: /tmp/tmp_NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.sh
11:21:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: *** Checking ONLINE mode … OK.
11:21:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: *** Checking target board connection … 1 connections found.
11:21:47 INFO: Flash Jetson AGX Xavier 16GB/32GB: Put the target board in RCM mode and retry.
11:21:47 ERROR: Flash Jetson AGX Xavier 16GB/32GB: command terminated with error
11:21:48 SUMMARY: NVIDIA Nsight Systems: Depends on failed component


Copy from exported logfile with more details:


Info: exec_command: /tmp/tmp_NV_L4T_FLASH_XAVIER_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.
Info: [ Component Install Finished with Error ]
Info: [host] [ 12.00 KB used. Disk Avail: 935.57 GB ]
Info: [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 7s ]
Error: [error]: : [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.sh; [error]:


Is the device faulty?

Hello,

Generally, I don’t take the log from sdkmanager to debug. Please directly use flash.sh to flash your board and see what log is shown.

https://elinux.org/Jetson/General_debug

Hello,
thanks for the link.

Here is the output of the console call of the flash.sh script:
call: sudo ./flash.sh jetson-xavier mmcblk0p1


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

L4T BSP Information:

R32 , REVISION: 5.0

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


I also listened to the serial output on the micro-usb port…
It shows a long log on a regular boot.

But shows nothing at all (no output) when the device in RCM-mode!?

I also disabled the tlp system service oh the host pc before. (TX2...probing the target board failed(ok) - #4 by dpl19980219)

It was further suspicious that the USB-Ports on my notebook were shut down due to a device failure.

It really looks to me like we did not receive a new or flawless product…

Hi,

There are few things to check

  1. Could you make sure the board is really in recovery mode? Actually, the lsusb command is not the precise way to check rcm anymore. Because lsusb will also show device when tegra boots up. Thus. make sure your board totally gives no response from both serial output and monitors.

  2. Did this board ever get flashed by this host before? If not, I would suggest you can try different host too. If you have other xavier modules, you can use them to test your host too. Generally, if more than one device not able to get flashed with the same host, then I would suspect this host has something wrong.

  3. Which type C port are you using for flash? Make sure you are not using the wrong port.

Hi,
thanks for your quick reply.

  1. The SDK output says that recovery mode is detected, if the SDK is used. There is no response on the serial port and no video output, before the flash script is called manually. lsusb shows: Bus 001 Device 010: ID 0955:7019 NVidia Corp.

  2. The board was bought as new and sealed. Flashing failed from day one, it never got flashed at all. The device had Jetpack 4.3 (?) pre-installed. I also tried a different host (no notebook), which shows the same error. And I don’t have a second device/jetson agx to try.

  3. I use the usb-c port on the front side - where the micro usb port is also located. Indicated as flash port here (NVIDIA Xavier - Nvidia developer kit)

I also noticed an error/failure warning displayed during the OS shutdown:

“[FAILED] Failed to start Configure USB flashing port for device mode.”

Hi,

This log has nothing to do with the recovery mode but it has something to do with the port itself.

Could you boot up your device, connect the type C cable and see if host side can detect the tegra?

Hi,
thanks for the clarification.
On the host side, the tegra will only be detected in RCM-mode. Not, when its OS is running.

You can also swap some type C cable and see whether new cable can give you positive result.

If they don’t, then maybe you should file RMA request and see if you can get a new one (jetson).

I used the cable from the dev kit as well as a third-party product. Same result :(.
I think I have to replace the device…

Ok, sorry for that. Please file a RAM request.

If you still have issue, please file topics.

Ok, I’ll try to get another one through the distributor. Thanks for your help!

Hello,
I have the same issue, meaning I just bought a Jetson AGX Xavier in January and the flashing process fails.
The flashing seems to be somewhat successful if I believe the first three lines I pasted, but the process fails, with this log: SUMMARY: NVIDIA Nsight Systems: Depends on failed component
I’m just pasting the end section of the logs as they are very long, please tell me if you want the complete logs.

02:02:36 INFO: Device Mode Host Setup in Flash: Device mode on host successfuly set with DNS 8.8.8.8!
02:02:36 INFO: Device Mode Host Setup in Flash: command finished successfully
02:02:36 SUMMARY: Device Mode Host Setup in Flash: Install completed successfully.
02:02:36 DEBUG: running command < true >
02:02:36 INFO: command finished successfully
02:02:36 DEBUG: Flash Jetson AGX Xavier 16GB/32GB: using adapter to install NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER to
02:02:36 INFO: Flash Jetson AGX Xavier 16GB/32GB: exec_command: /tmp/tmp_NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.sh
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: sudo ./nvautoflash.sh
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: *** Checking ONLINE mode … OK.
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: *** Checking target board connection … 1 connections found.
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: *** Reading ECID … FUSELEVEL=fuselevel_production hwchipid=0x19 bootauth=NS
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: “/home/lweingart/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_AGX_XAVIER/Linux_for_Tegra/bootloader/tegraflash.py” --chip 0x19 --applet “/home/lweingart/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_AGX_XAVIER/Linux_for_Tegra/bootloader/mb1_t194_prod.bin” --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins “mb2_applet nvtboot_applet_t194.bin” --skipuid --cmd “dump eeprom boardinfo cvm.bin; reboot recovery”
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 0.0065 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader /home/lweingart/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_AGX_XAVIER/Linux_for_Tegra/bootloader/mb1_t194_prod.bin zerosbk
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 0.0241 ] Assuming zero filled SBK key
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 0.0341 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg.pdf sfuse.bin
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 0.0534 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
02:02:37 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 0.0600 ] RCM version 0X190001
02:02:39 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 2.0935 ] tegrarcm_v2 --isapplet
02:02:39 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 2.1332 ] tegrarcm_v2 --ismb2
02:02:39 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 2.1782 ] adding BCH for nvtboot_applet_t194.bin
02:02:39 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 2.2047 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_sigheader.bin.encrypt nvtboot_applet_t194_sigheader.bin.hash zerosbk
02:02:39 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 2.2490 ] Sending mb2
02:02:39 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 2.2490 ] […] 100%
02:02:39 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 2.3038 ] Applet version 01.00.0000
02:02:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.3630 ] tegrarcm_v2 --isapplet
02:02:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.4037 ] tegrarcm_v2 --ismb2
02:02:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.4451 ] tegrarcm_v2 --ismb2
02:02:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.4942 ] tegrarcm_v2 --oem platformdetails chip chip_info.bin
02:02:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.4975 ] MB2 Applet version 01.00.0000
02:02:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.5997 ] Chip Sample: non es
02:02:40 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.6164 ] MB2 Applet version 01.00.0000
02:02:41 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.6928 ] Saved platform info in /home/lweingart/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_AGX_XAVIER/Linux_for_Tegra/bootloader/cvm.bin
02:02:41 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.7704 ] tegrarcm_v2 --ismb2
02:02:41 INFO: Flash Jetson AGX Xavier 16GB/32GB: [ 3.8168 ] MB2 Applet version 01.00.0000
02:02:43 INFO: Flash Jetson AGX Xavier 16GB/32GB: — Reading board information succeeded.
02:02:43 INFO: Flash Jetson AGX Xavier 16GB/32GB: — Parsing board SKU succeeded.
02:02:43 INFO: Flash Jetson AGX Xavier 16GB/32GB: /home/lweingart/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_AGX_XAVIER/Linux_for_Tegra/flash.sh jetson-agx-xavier-devkit mmcblk0p1
02:02:43 INFO: Flash Jetson AGX Xavier 16GB/32GB: ###############################################################################
02:02:43 INFO: Flash Jetson AGX Xavier 16GB/32GB: USB port and is in recovery mode.
02:02:43 ERROR: Flash Jetson AGX Xavier 16GB/32GB: command terminated with error
02:02:45 SUMMARY: NVIDIA Nsight Systems: Depends on failed component

From what I can see on the thread, I should retry using flash.sh.
You give a link that tells:
" For more detail about how to use flash.sh, please refer to Jetson quick start guide → Jetson Download Center | NVIDIA Developer"
However, all the information I could find following these links explain how to flash the Jetson with the GUI of the sdkmanager, I found nothing about using flash.sh.
Would you have a more specific link to suggest on how to use flash.sh ?
Or would you have another advice I should follow ?

Any help would be greatly appreciated.
Thank you very much in advance

Hi,

You already said “Jetson quick start guide”. But it looks like you didn’t check quick start guide.

Thus, please use this link directly. I add the “quick” as search keywords here.

For xavier, use the TX2 quick start guide.

Hi,

Thank you for your quick reply :-)
So, here is the flash.sh log:
/home/lweingart/nvidia/nvidia_sdk/JetPack_4.5_Linux_JETSON_AGX_XAVIER/Linux_for_Tegra/flash.sh jetson-agx-xavier-devkit mmcblk0p1
###############################################################################

L4T BSP Information:

R32 , REVISION: 5.0

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

Looking at it, it’s exactly the same log as mailm1l8a

I made sure to follow the recovery mode process and the GUI tells me that it detects the jetson.
I am using the right C port (the one next to the 40 pin)

The thing I don’t understand is that the installation process starts just fine, with the jetson well detected, and then fails.

EDIT:
I clicked on retry failed items and got that:
04:53:36 SUMMARY: NVIDIA Nsight Systems: Install completed successfully.
04:54:36 SUMMARY: Drivers for Jetson: Install completed successfully.
04:58:37 SUMMARY: File System and OS: Install completed successfully.
04:58:38 SUMMARY: Device Mode Host Setup in Flash: Install completed successfully.
04:58:45 SUMMARY: NVIDIA Nsight Systems: Depends on failed component

So in the end, did it partially work ?

I have to admit that I’m using an Ubuntu180.04 in a virtual machine with VMWare though, as I don’t have any PC on which I could install Ubuntu available, but as I only had jetson nano thus far, I didn’t know an Ubuntu was mandatory to properly install a jetson xavier.

Any idea where to look ?

Ok, so I decided to try and boot the jetson, and it booted in Ubuntu and asked for the basic configuration just fine.
I will poke around to see what works and what doesn’t

Hi,

Unfortunately, sdkmanager does not support VM. Thus, I think though it detects the board, it gets failed after the flash starts.

And sdkmanger starts running does not 100% your board is going to be flashed.

https://elinux.org/Jetson/General_debug

You can read this page to understand why I asked others to run flash.sh directly.

Alright, thank you for the clarification.

I can see that I have ubuntu 20.04 correctly installed on my jetson xavier now.
Could I install the jetpack directly from the xavier now that I have a working OS ?

“Directly from xavier” → No, because sdkmanager only supports the x86 machine.

The page I posted earlier should tell you how this sdkmanger things work. I still suggest you to read that first. Otherwise, I will just copy and paste same description from that page.

Your current situation is that you somehow able to bypass the flash process. I am not sure what image is on your device now, maybe it is a pre-flashed image from factory. However, if you break this OS someday, you will still need a host to re-flash it.

If you just want to run those sdk binaries now and don’t care about the flash, then use ethernet and only install the sdk to your xavier is also fine.