In Need of Help for our Flashing Issue on Xavier Being Stuck at 99.8%

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
#1

Hi there,

First of all sorry for posting this repeatedly asked question but we are working on some important task and a few days are left before the deadline.

This problem of flash stuck at 99.8% is being issued before but we don’t know if the problem is about the hardware and we still keep trying. Shall we consider trying RMA?

Is there any final thought or solution about the problem somewhere?

This is what we get from UART

UART LOG
.
[0083.190] C> LOADER: Could not read preboot.
[0083.193] E> Task 58 failed (err: 0x1d290603)
[0083.198] E> Top caller module: LOADER, error module: FUSE, reason: 0x03, aux_info: 0x06
[0083.205] I> MB1(1.5.1.0-t194-41334769-59d8a47d) BIT boot status dump :
0000000000011111111111100111111111111100110001111111011000
10000000000000000000000000000000000000000000000000000000000000000000001
1101000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000
[0083.235] I> Reset to recovery mode

Any thoughts will be greatly appreciated.

#2

Are you using a VM for the host? Are you using the supplied micro-B USB cable? Which JetPack/SDK Manager release are you using? Is the carrier board from the dev kit?

#3

Our configuration :

Host (ubuntu 18.04 (not VM - dedicated)).
Supplied cable by Nvidia
Jetpack : 4.2.3
SDK Manager : 0.9.14.4964
Board : Nvidia Jetson Xavier Developer Kit (P2972)

#4

I recall recently seeing some possible flash issues in some cases (sorry, I don’t remember exactly which version that is with). Could you try JetPack 4.2.2 or 4.2.1 instead? This may be an issue of flashing software instead of the Xavier itself.

A list of JetPack releases is here, but you may need to log in first and then click on the link again:
https://developer.nvidia.com/embedded/jetpack-archive

#5

Thank you very much.
We failed after trying 4.2.2 and 4.2.1 but succeeded flashing with 4.2 . What is next step to do ? Will we be able to flash it against 4.2.3 in future or will there any updates or bug-fixes?

#6

Someone from NVIDIA would need to comment. I know the bug was recognized, and that there is some sort of fix in the works, but I do not remember any of the details (there were some recent threads on this, but unfortunately I do not have notes on that topic).

#7

Hi cherkesgiller,

I’ve encountered a similar issue as you describe it using the Jetson Xavier aswell. What I do in thoses cases is to let the sdkmanager to setup the whole JetPack environment but skip the flashing step. Then I flash the board with the following command:

sudo ./flash.sh jetson-xavier mmcblk0p1

And finally if additional SDK components are needed (CUDA, OpenCV, etc.) I use the sdkmanager again but unselecting the Jetson OS component.

Hope you find this useful!

#8

I’ve always done the same as what @jchaves mentions.

#9