Flashing Jetson Xavier fails

Hi ,

I have been trying to flash my Jetson Xavier. I have a dedicated ubuntu laptop, and the specifications are given below,

Host Laptop used: Dell I7 8th Gen, Ubuntu 18.04 Bionic, 64 bit, with 3 USB ports.

When I try to flash with SDK Manager, the flash does not go beyond 0.8%. So, I tried manual flashing, but it says,

“Error: Probing the target board Failed”. When I try lsusb, I could see the board is connected.

The below link for your reference:

Also, I have followed the suggestion given in the below link, but did not help,

(Tried disconnecting and connected again, but the error remains same)

the Jetson board needs to be connected to the HOST PC via the recovery port; It also needs to be in the recovery mode;
What is the output of
lsusb
after conencting the board and putting it into the recovery mode?
once the nvidia corp with correct parameters is reflected in lsusb outputs it will be possible to probe it by sdkmanager, whatever

Hi,

I have connected it through J512 port, which is detected for flashing only. After I connect, I could see the below,

BUS 001: DEVICE 011 ID: 0955:7019 Nvidia Corp.

This clearly shows that the board is connected in recovery mode.

(To put the board in recovery mode, I pressed the middle button and then pressed the power button, then released both simultaneously)

Please refer to the attached image in the blog, shows clearly that the board is connected

if the board is connected and listed as in the recovery mode it might be a software or access permissions issue;
could you either uninstall the current jetpack, then reinstall or try the following:

 sudo sdkmanager --cli  install --user your@email.com --logintype devzone --product Jetson --version 4.4 --targetos Linux --target P2888-0001 --flash all --targetimagefolder /home/youruser/Downloads/nvidia/installation_agx --downloadfolder /home/youruser/Downloads/nvidia

Hello Andrey,

Thanks for the support. I used the command that you provided and I get the below message.

sudo sdkmanager --cli install --user somasundaram.s@ --logintype devzone --product Jetson --version 4.4 --targetos Linux --target P2888-0001 --flash all --targetimagefolder /home/somasundaram/nvidia/installation_agx --downloadfolder /home/somasundaram/nvidia
Please enter password for user somasundaram.s@:
Logging in…
Login succeeded.
Loading user information…
User information loaded successfully.
Loading server data…
Server data loaded successfully.
Target Image is already installed on this host machine (/home/somasundaram/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_AGX_XAVIER). Please use SDK Manager to uninstall the Target Image, or select a different location using ‘targetimagefolder’.

change the --cli install
to --cli uninstall
complete it,
then try again with
--cli install

I used uninstall, but the output remains the same. Check below,

sudo sdkmanager --cli uninstall --user somasundaram.s@ --logintype devzone --product Jetson --version 4.4 --targetos Linux --target P2888-0001 --flash all --targetimagefolder /home/somasundaram/nvidia/installation_agx --downloadfolder /home/somasundaram/nvidia
Please enter password for user somasundaram.s@ :
Logging in…
Login succeeded.
Loading user information…
User information loaded successfully.
Loading server data…
Server data loaded successfully.
Target Image is already installed on this host machine (/home/somasundaram/nvidia/nvidia_sdk/JetPack_4.4_Linux_JETSON_AGX_XAVIER). Please use SDK Manager to uninstall the Target Image, or select a different location using 'targetimagefolder

for uninstall also version 4.3 might need to be used
as in --version 4.3 instead of --version 4.4;
then switch back

sudo sdkmanager --cli uninstall --user somasundaram.s@ --logintype devzone --product Jetson --version 4.3 --targetos Linux --target P2888-0001 --flash all --targetimagefolder /home/somasundaram/nvidia/installation_agx --downloadfolder /home/somasundaram/nvidia
Please enter password for user somasundaram.s@ :
Logging in…
Login succeeded.
Loading user information…
User information loaded successfully.
Loading server data…
Server data loaded successfully.
Target Image is already installed on this host machine (/home/somasundaram/nvidia/nvidia_sdk_4.2/JetPack_4.3_Linux_JETSON_AGX_XAVIER). Please use SDK Manager to uninstall the Target Image, or select a different location using ‘targetimagefolder’.

it points out that uninstallation or change of paths will need to be done

Target Image is already installed on this host machine (/home/somasundaram/nvidia/nvidia_sdk_4.2/JetPack_4.3_Linux_JETSON_AGX_XAVIER). Please use SDK Manager to uninstall the Target Image, or select a different location using ‘targetimagefolder’.

the uninstallation procedure is straightforward.
you could use unique path & targetimagefolder
it is an alternative for uninstallation, as it seems to me

did the uninstallation ever succeed?
uninstallation argument should result in uninstallation menu that manages the uninstallation procedure.
once uninstalled successfully it would be able to install to the same target folder;
without uninstaling it might still be possible to manually set just differnt targetfolder value

does the graphical sdkmanager also fail uninstalling?
does the headless sdk open the uninstall dialog ever?
I would uninstall the sdkmanager itself and would erase all folders, thne downloaded the latest sdkmanager, then make sure that all images are uninstalled from it; then would try again
Did you at all take steps to uninstall the target image after firing up the headless sdk command? Ddi it open any pop up window? or uninstall interface?

I followed your procedure, uninstalled all the previous versions via the graphics sdkmanager. Ran the command you suggested,

sudo sdkmanager --cli install --user somasundaram.s@einfochips.com --logintype devzone --product Jetson --version 4.4 --targetos Linux --target P2888-0001 --flash all --targetimagefolder /home/somasundaram/nvidia/installation_agx --downloadfolder /home/somasundaram/nvidia

But again the Flashing stopped at 0.8%. Exactly as it happend in the graphics sdkmanager before. Below image for your reference,

https://drive.google.com/file/d/1JH6Q8kZsw4fYB-krt-z84VHn-ovu6G5A/view?usp=sharing

When I check the connection using -lsusb, connection shows up as in the below image,

https://drive.google.com/file/d/1b2vxtJ8oTZ_B0ALHzvjuJbTKah0v1yGb/view?usp=sharing

FYI: I am using the cable came along with the board. Keyboard, mouse and ethernet cable connected.

what is the output of
df -h
?

df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.7G 0 7.7G 0% /dev
tmpfs 1.6G 2.1M 1.6G 1% /run
/dev/nvme0n1p3 463G 65G 375G 15% /
tmpfs 7.8G 68M 7.7G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/loop0 15M 15M 0 100% /snap/gnome-logs/34
/dev/loop1 63M 63M 0 100% /snap/gtk-common-themes/1506
/dev/loop2 2.5M 2.5M 0 100% /snap/gnome-calculator/748
/dev/loop3 56M 56M 0 100% /snap/core18/1885
/dev/loop5 140M 140M 0 100% /snap/gnome-3-26-1604/64
/dev/loop6 1.0M 1.0M 0 100% /snap/gnome-logs/100
/dev/loop7 87M 87M 0 100% /snap/core/4650
/dev/loop4 13M 13M 0 100% /snap/gnome-characters/96
/dev/loop9 32M 32M 0 100% /snap/gtk-common-themes/3
/dev/loop8 97M 97M 0 100% /snap/core/9665
/dev/loop10 55M 55M 0 100% /snap/core18/1880
/dev/loop11 141M 141M 0 100% /snap/gnome-3-26-1604/100
/dev/loop12 2.4M 2.4M 0 100% /snap/gnome-calculator/170
/dev/nvme0n1p1 786M 46M 741M 6% /boot/efi
/dev/loop13 256M 256M 0 100% /snap/gnome-3-34-1804/36
/dev/loop14 2.3M 2.3M 0 100% /snap/gnome-system-monitor/148
/dev/loop15 3.8M 3.8M 0 100% /snap/gnome-system-monitor/41
/dev/loop16 384K 384K 0 100% /snap/gnome-characters/550
tmpfs 1.6G 16K 1.6G 1% /run/user/120
tmpfs 1.6G 44K 1.6G 1% /run/user/1001

does it stuck at 8% if to reflash it again few more attempts?

it gets stuck at 0.8%

are you using the devkit AGX ? or a module with custom carrier board? industrial module? else?
do you have usb-c port on your HOST PC to try flashing with cable
usb-c <-> usb-c ?

I have a AGX Developer module. Below image for your reference.

I have USB -C port. But I dont have a USB C <–> USB C connector. Instead, suggest if I can use the USB female to USB-C connector that came with the module to join the USB Male to USB Connector ?

USB C <–> USB Male + USB Female <–> USB C