AGX Xavier Jetpack 4.2 Flashing Failed (At Around 98%)

Hi community, when flashing my AGX Xavier with Jetpack 4.2, I got the following error:

* 0:12:47 INFO : Flash Jetson AGX Xavier : [ 4087.9081 ] tegradevflash_v2 --iscpubl
* 20:12:48 INFO : Flash Jetson AGX Xavier : [ 4087.9107 ] CPU Bootloader is not running on device.
* 20:12:48 INFO : Flash Jetson AGX Xavier : [ 4087.9291 ]
* 20:12:48 INFO : Flash Jetson AGX Xavier : [ 4088.9338 ] tegrarcm_v2 --isapplet
* 20:12:48 INFO : Flash Jetson AGX Xavier : [ 4088.9528 ]
* 20:12:48 INFO : Flash Jetson AGX Xavier : [ 4088.9560 ] tegrarcm_v2 --ismb2
* 20:12:48 INFO : Flash Jetson AGX Xavier : [ 4088.9930 ]
* 20:12:48 INFO : Flash Jetson AGX Xavier : [ 4088.9963 ] tegradevflash_v2 --iscpubl
* 20:12:49 INFO : Flash Jetson AGX Xavier : [ 4088.9990 ] CPU Bootloader is not running on device.
* 20:12:49 INFO : Flash Jetson AGX Xavier : [ 4089.0174 ]
* 20:12:49 INFO : Flash Jetson AGX Xavier : [ 4090.0224 ] tegrarcm_v2 --isapplet
* 20:12:50 INFO : Flash Jetson AGX Xavier : [ 4090.0273 ]
* 20:12:50 INFO : Flash Jetson AGX Xavier : [ 4090.0303 ] tegrarcm_v2 --ismb2
* 20:12:50 INFO : Flash Jetson AGX Xavier : [ 4090.0475 ]
* 20:12:50 INFO : Flash Jetson AGX Xavier : [ 4090.0491 ] tegradevflash_v2 --iscpubl
* 20:12:51 INFO : Flash Jetson AGX Xavier : [ 4090.0505 ] CPU Bootloader is not running on device.
* 20:12:51 INFO : Flash Jetson AGX Xavier : [ 4090.0679 ]
* 20:12:51 INFO : Flash Jetson AGX Xavier : [ 4091.0727 ] tegrarcm_v2 --isapplet
* 20:12:51 INFO : Flash Jetson AGX Xavier : [ 4091.0935 ]
* 20:12:51 INFO : Flash Jetson AGX Xavier : [ 4091.0973 ] tegrarcm_v2 --ismb2
* 20:12:51 INFO : Flash Jetson AGX Xavier : [ 4091.1390 ]
* 20:12:51 INFO : Flash Jetson AGX Xavier : [ 4091.1422 ] tegradevflash_v2 --iscpubl
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4091.1451 ] CPU Bootloader is not running on device.
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4091.1647 ]
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4092.1702 ] tegrarcm_v2 --isapplet
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4092.1967 ]
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4092.1991 ] tegrarcm_v2 --ismb2
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4092.2329 ]
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4092.2354 ] tegradevflash_v2 --iscpubl
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4092.2381 ] CPU Bootloader is not running on device.
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 4092.2527 ]
* 20:12:52 INFO : Flash Jetson AGX Xavier : Error: None of the bootloaders are running on device. Check the UART log.
* 20:12:52 INFO : Flash Jetson AGX Xavier : Failed flashing t186ref.
* 20:12:52 INFO : Flash Jetson AGX Xavier : exit status 1
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ Component Install Finished with Error ]
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ 8.02 GB used. Disk Avail: 5.94 GB ]
* 20:12:52 INFO : Flash Jetson AGX Xavier : [ NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP Install took 1h11m44s ]
* 20:12:52 ERROR : Flash Jetson AGX Xavier : Run commands failed at step Install: command sudo ./flash.sh jetson-xavier mmcblk0p1 finished with error
* 20:12:52 INFO : Flash Jetson AGX Xavier :
* 20:12:52 ERROR : Flash Jetson AGX Xavier : command terminated with error
* 20:12:52 ERROR : Flash Jetson AGX Xavier : install 'Flash Jetson AGX Xavier' failure, command < cd '/home/khoongweihao/agx-xavier-sdk2/JetPack_4.2_Linux_P2888' ; '/opt/nvidia/sdkmanager/resources/app/output/installUtils/adapter' -a='install' -c='eyJpZCI6Ik5WX0w0VF9GTEFTSF9YQVZJRVJfV0lUSF9PU19JTUFHRV9DT01QIiwibmFtZSI6IkZsYXNoIEpldHNvbiBBR1ggWGF2aWVyIiwiZGVzY3JpcHRpb24iOiJGbGFzaCBKZXRzb24gQUdYIiwiY29tcFR5cGUiOiJmbGFzaCIsImlzVmlzaWJsZSI6dHJ1ZSwibGljZW5zZUlkIjoiTlZfSkVUUEFDS19PU19FVUxBIiwiaXNEZXRlY3RhYmxlSW5zdGFsbCI6ZmFsc2UsImlzSW5zdGFsbFBhdGhDdXN0b21pemFibGUiOnRydWUsInRpbWVvdXRTZWNvbmRzIjozNjAwLCJ2ZXJzaW9uIjoiMzIuMSIsIm9wZXJhdGluZ1N5c3RlbXMiOlsidWJ1bnR1MTYwNCIsInVidW50dTE4MDQiXSwiaW5zdGFsbFNpemVNQiI6MzAwNTMsImRvd25sb2FkRmlsZXMiOltdLCJpbnN0YWxsUGFyYW1ldGVycyI6eyJpbnN0YWxsRGlyIjoie3tUQVJHRVRfUk9PVH19L3t7QlVORExFX1RJVExFfX1fe3tCT0FSRF9JRH19L0xpbnV4X2Zvcl9UZWdyYSIsImluc3RhbGxDb21tYW5kcyI6W3sicmVtb3RlRXhlY0Jhc2giOlsic3VkbyByZWJvb3QgZm9yY2VkLXJlY292ZXJ5Il0sImlnbm9yZUVycm9yIjp0cnVlfSx7ImNvbW1lbnQiOiJ3YWl0IGZvciBkZXZpY2UgdG8gc2h1dGRvd24gYW5kIHRvIGdvIHRvIHJlY292ZXJ5IG1vZGUiLCJ1c2VyQ29tbWFuZCI6InNsZWVwIDIwIn0seyJ1c2VyQ29tbWFuZCI6InN1ZG8gLi9mbGFzaC5zaCBqZXRzb24teGF2aWVyIG1tY2JsazBwMSJ9LHsidXNlckNvbW1hbmQiOiJzbGVlcCAxMCJ9XX0sInRhcmdldElkcyI6WyJQMjg4OCJdLCJkZXBlbmRlbmNpZXMiOlt7ImlkIjoiTlZfTDRUX0ZJTEVfU1lTVEVNX0FORF9PU19YQVZJRVJfQ09NUCIsIm9wZXJhdG9yIjoiPT0iLCJ2ZXIiOiIzMi4xIiwiX2lkIjoiTlZfTDRUX0ZJTEVfU1lTVEVNX0FORF9PU19YQVZJRVJfQ09NUEBQMjg4OCJ9LHsiaWQiOiJOVl9MNFRfRFJJVkVSU19YQVZJRVJfQ09NUCIsIm9wZXJhdG9yIjoiPT0iLCJ2ZXIiOiIzMi4xIiwiX2lkIjoiTlZfTDRUX0RSSVZFUlNfWEFWSUVSX0NPTVBAUDI4ODgifSx7ImlkIjoiTlZfTDRUX0RFVklDRV9NT0RFX1NFVFVQX0NPTVBfSU5fRkxBU0giLCJvcGVyYXRvciI6Ij09IiwidmVyIjoiMS4wIiwiX2lkIjoiTlZfTDRUX0RFVklDRV9NT0RFX1NFVFVQX0NPTVBfSU5fRkxBU0hAUDI4ODgifV0sImV4dGVybmFsX2RlcGVuZGVuY2llcyI6W10sInRhcmdldElEIjoiUDI4ODgiLCJfaWQiOiJOVl9MNFRfRkxBU0hfWEFWSUVSX1dJVEhfT1NfSU1BR0VfQ09NUEBQMjg4OCIsInBhcmVudElEIjoiTlZfRFJJVkVfRkxBU0hfVEFSR0VUX0dST1VQIiwiX3BhcmVudElEIjoiTlZfRFJJVkVfRkxBU0hfVEFSR0VUX0dST1VQQFAyODg4IiwiaW5zdGFsbFN0YXR1cyI6Im5vbmUiLCJhY3Rpb24iOjEsInRhcmdldEFjY2Vzc0luZm8iOnsidXNlciI6IiIsInBhc3N3b3JkIjoiIiwiaG9zdCI6IiIsInBvcnQiOiIifSwiYnVuZGxlVGl0bGUiOiJKZXRQYWNrXzQuMl9MaW51eCIsImluc3RhbGxQYXRoIjoiL2hvbWUva2hvb25nd2VpaGFvL2FneC14YXZpZXItc2RrMi9KZXRQYWNrXzQuMl9MaW51eF9QMjg4OCIsImluc3RhbGxSb290IjoiL2hvbWUva2hvb25nd2VpaGFvL2FneC14YXZpZXItc2RrMiIsImJvYXJkSUQiOiJQMjg4OCIsImlzRHJ5UnVuIjpmYWxzZX0=' -i='NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP' -v='32.1' -l='/home/khoongweihao/agx-xavier-sdk2/JetPack_4.2_Linux_P2888' -L='/home/khoongweihao/.nvsdkm/logs/JetPack_4.2_Linux' -p='1742' -t='P2888' -e='undefined' > terminated with error
* 20:12:52 INFO : Device Mode Host Setup in Target SDK : install 'Device Mode Host Setup in Target SDK' Skipped
* 20:12:52 INFO : DateTime Target Setup : install 'DateTime Target Setup' Skipped
* 20:12:52 INFO : CUDA Toolkit for L4T : install 'CUDA Toolkit for L4T' Skipped
* 20:12:52 INFO : cuDNN on Target : install 'cuDNN on Target' Skipped
* 20:12:52 INFO : TensorRT on Target : install 'TensorRT on Target' Skipped
* 20:12:52 INFO : OpenCV on Target : install 'OpenCV on Target' Skipped
* 20:12:52 INFO : VisionWorks on Target : install 'VisionWorks on Target' Skipped
* 20:12:52 INFO : Multimedia API : install 'Multimedia API' Skipped
* 20:12:53 INFO : All done!

FLASHING FAILED 
Please review the terminal tab for details. Resolve and RETRY.

![](/opt/nvidia/sdkmanager/resources/app/output/dist/electron/images/icon_status_skipped.svg) Installation of target SDK components was skipped

EXPORT LOGS

RETRY

FAILED ITEMS

![](/opt/nvidia/sdkmanager/resources/app/output/dist/electron/images/icon_retry.svg)

STOP TRYING

![](/opt/nvidia/sdkmanager/resources/app/output/dist/electron/images/NVIDIA-logo-dark.svg)

Copyright © 2020, [NVIDIA CORPORATION](http://www.nvidia.com/page/home.html). All rights reserved. | [NVIDIA Developer](https://developer.nvidia.com/)

If it helps, I am using Ubuntu 18.04 LTS on a virtualbox VM, with close to 60GB of disk allocated, 5.2GB RAM.

I do understand that using a VM to flash is not supported by Nvidia, but I do not have any other choice as this is the only available terminal I can have access to back home…

Thank you and looking forward to receiving some help on this…

@khoongweihao

Could check to reconect the usb port to your virtalbox VM? you can check with lsusb within the ubuntu, ‘** NVIDIA corp’ will be appeared on one of the usb port indicating the target jetson device is in the right recover mode be ready to receive the flash command.

@alanz Yes, I obtained the following:

khoongweihao@khoongweihao-VirtualBox:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0955:7019 NVidia Corp. 
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Is it supposed to show that?

Yes, the jetson is right in recover mode and connected.

Could you try with jetpack 4.3 again and share the logs?

@alanz I was using Jetpack 4.2 earlier. Just to confirm, do you mean Jetpack 4.3 and not 4.2 as I’ve previously tried? Thank you.

Yes, pls try with jetpack 4.3 instead of jetpack 4.2 as you posted.

@alanz Got it, thanks for the help and clarifications. I’ll be in touch shortly.

@alanz I have just tried flashing the AGX with Jetpack 4.3, and an error occured at 99.8% (second time on 4.3) and exported the logs. Is there a particular name for the log file? When I clicked on export logs and export debug logs, I got 2 zip folders instead, each containing multiple ‘log’ files. I’m attaching the ones from “SDKM_logs_2020-04-06_23-32-10” here:

sdkm.log (3.2 MB) NV_CUDA_HOST_COMP.log (62.9 KB) NV_CUDA_HOST_CROSS_COMP.log (25.1 KB) NV_DEVICE_MODE_SETUP_IMAGE_COMP.log (2.3 KB) NV_L4T_DEVTOOLS_DOCS_HOST_COMP.log (602 Bytes) NV_L4T_DRIVERS_T194_COMP.log (4.1 KB) NV_L4T_FILE_SYSTEM_AND_OS_T194_COMP.log (10.7 KB) NV_L4T_FLASH_XAVIER_WITH_OS_IMAGE_COMP.log (40.2 KB) NV_L4T_NVIDIA_NSIGHT_GRAPHICS_HOST_COMP.log (2.6 KB) NV_L4T_NVIDIA_NSIGHT_SYSTEMS_HOST_COMP.log (5.4 KB) NV_OPENCV_HOST_COMP.log (13.6 KB) NV_VISIONWORKS_HOST_COMP.log (63.0 KB)
NV_CUDA_HOST_COMP.log (4.5 KB) NV_CUDA_HOST_CROSS_COMP.log (4.8 KB) NV_L4T_NVIDIA_NSIGHT_GRAPHICS_HOST_COMP.log (3.7 KB) NV_L4T_NVIDIA_NSIGHT_SYSTEMS_HOST_COMP.log (3.7 KB) NV_NVIDIA_NSIGHT_GRAPHICS_L4T_COMP.log (1.1 KB) NV_NVIDIA_SYSTEM_PROFILER_L4T_COMP.log (1.1 KB) NV_OPENCV_HOST_COMP.log (16.8 KB) NV_VISIONWORKS_HOST_COMP.log (32.6 KB)

Thank you and am looking forward to your assistance on this.

JetPack/SDK Manager will download content before running or installing components. Missing a basic file has me wondering if it is actually an internet access issue from before flash ever starting. Does your VM have full internet access without any special proxy setup?

@linuxdev Yes, I believe so. Is there a way I can check on this further in my terminal? Also, if all else fails, shall I remove all the downloaded files by the SDK Manager, then use SDK Manager to re-download all the files required when flashing JetPack 4.3? Thank you for the continued assistance on this matter.

@khoongweihao

Quick confirm:Are you flashing with devkit board right?And pls also confirm the disk size which sdkmanager could manage.

@alanz Yes I am flashing with the AGX developer kit, not the module. The VM’s current total size is 50GB (had to down-size it due to space limitations on my host PC), with actual size 45.59GB. I can increase the disk size, but my host PC may have issues.

Do let me know I I understood your questions right.

Thanks again!

Please refer to this wiki page for some debug tip.
https://elinux.org/Jetson/General_debug

Below log from your previous log blocks your flash procedure.

  • 20:12:52 INFO : Flash Jetson AGX Xavier : Error: None of the bootloaders are running on device. Check the UART log.

Also in your latest result of jetpack4.3, it hits this issue again.

Error: None of the bootloaders are running on device. Check the UART log.

I cannot tell whether it is due to VM or not. Better finding a native ubuntu host if possible.

Dump the UART log should also give out some clue.

@WayneWWW Thanks for the feedback and suggestions. I’ll take a look at the wiki page as you have suggested.

Just to clarify, by native Ubuntu host, do you mean something like Ubuntu 18.04 LTS downloaded (can be from Windows app store) and installed in Windows? I actually do have something like that, which looks like the following:

Hi,

No, I meant a host that installed ubutnu, not VM.

@WayneWWW Yes, what i was referring to is this https://waterprogramming.wordpress.com/2018/01/29/installing-a-native-ubuntu-terminal-on-windows-10/, not the VM like Virtualbox. Is the Ubuntu terminal from the Windows store considered a VM? Apologies I am not familiar with these…

@WayneWWW I’ve extracted the two possible zipped logs extractable from the sdkmanager. As I cannot upload .zip files here (don’t see the option for me to do so), I’ve added a .log extension to them to get by this limitation. Kindly remove the .log extensions when accessing the .zip folders, which I’ve attached below. For the UART log, I can’t seem to find it… is it within those two zip folders?

SDKM_logs_2020-04-07_21-22-49.zip.log (289.1 KB)
SDKM_logs_JetPack_4.3_Linux_for_Jetson_AGX_Xavier_2020-04-07_20-07-56.zip.log (287.0 KB)

i’ve also chanced upon a post where the user faced a similar problem: Flash Jetson OS fails on Jetson AGX Xavier.....stuck at 99.8%.

A simple Ubuntu terminal is probably insufficient for flash. You basically need a full install of Ubuntu 18.04, but this can be set up as dual boot with Windows. It sounds like you are short on disk space though, and I’d actually advise to install Ubuntu to a new disk and leave the original Windows alone (you’d end up picking which to boot to as you start your computer).

Understand that during a flash loopback devices are employed, and that these are more than terminal programs. Loopback requires an actual Linux kernel be running, and a VM will have this, but any standalone terminal which otherwise looks like Linux probably won’t have that ability.

Note that flashing can probably consume 40GB of space on the host PC without much effort. Actually installing Linux would take a lot of space, and so once you’ve installed SDK Manager your VM must be close to being full. In a case where your VM is running out of space, then it is possible some of the content is truncated…including that previously missing file, “icon_retry.svg”. Regardless, a VM tends to be a source of pain.

1 Like

For the UART log, I can’t seem to find it… is it within those two zip folders?

No, sdkmanager does not provide the uart log.
The UART log is the serial console log from your device. You must use some tools like minicom on your host to read it.
I put the info in the link of general debug page. Please do read it.

To make it more simple to understand, just forget about sdkmanager at this moment. I notice many users new to jetson platform would get confused by it.
Please use flash.sh script on your host directly. As for the info of this script, the wiki page also tells where to find it.

@linuxdev @WayneWWW Thank you for the continued support, feedback and suggestions once again. Do give me some time to digest all the information you have given, so that I do not make some deeper blunder on my end which may make debugging harder. In summary, I’ll address @WayneWWW’s points first, then try performing a dual-boot some time later as @linuxdev has suggested.

Thanks again and I’ll be in touch soon once I get the UART log extracted, or when I encounter any hitches (hopefully not).