After flashing the jetson OS and entering the ubuntu desktop screen (for the Jetson AGX Xavier), I couldn’t install the Jetson SDK Components. The error thrown was: Jetson device is in recovery mode. I rebooted the Xavier and logged in, but I still get this error.
Can someone shed some light on this? thanks.
The following is the logs:
09:54:13 INFO : Flash Jetson AGX Xavier : install ‘Flash Jetson AGX Xavier’ success
10:01:45 DEBUG : running command < ip addr | grep 192.168.55.100/24 >
10:01:45 ERROR : command terminated with error
10:01:45 DEBUG : running command < lsusb | grep “NVidia Corp” >
10:01:46 INFO : Bus 002 Device 007: ID 0955:7020 e[01;31me[KNVidia Corpe[me[K.
10:01:46 INFO : command finished successfully
10:01:46 ERROR : Jetson device is in recovery mode.
10:02:05 DEBUG : running command < ip addr | grep 192.168.55.100/24 >
10:02:05 ERROR : command terminated with error
10:02:05 DEBUG : running command < lsusb | grep “NVidia Corp” >
10:02:05 INFO : Bus 002 Device 007: ID 0955:7020 e[01;31me[KNVidia Corpe[me[K.
10:02:05 INFO : command finished successfully
Run “dmesg” on the host and provide the full output. This might show any errors the host might have had when enumerating the Jetson USB device.
Now, connect jetson device with a ethernet cable, get its IP address, ssh to Jetson and:
Run “journalctl -u nv-l4t-usb-device-mode” to show any errors configuring the USB device mode service on Jetson, during boot.
As root, run “/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh”. This is expected to show some errors; ignore them.
As root, run “bash -x /opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode.sh” and provide the entire output that prints. This should (a) show the same errors as in (2) above, and/or (b) actually make L4T USB device mode work, if the reason it failed the first time was due to some missing dependency that wasn’t available right when the script ran at boot.
Thanks for your clarification. But is seems that the issue has not been solved. Please see the following command lines. Please help address how to solve the Recovery Mode issue. Thanks in advance.
684 packages can be updated.
396 updates are security updates.
New release ‘18.04.2 LTS’ available.
Run ‘do-release-upgrade’ to upgrade to it.
Last login: Tue Apr 23 18:33:48 2019 from 192.168.0.104
nvidia@tegra-ubuntu:~$ journalctl -u nv-l4t-usb-device-mode
– Logs begin at Tue 2019-04-23 16:48:30 UTC, end at Tue 2019-04-23 18:37:30 UTC
Apr 23 16:48:32 tegra-ubuntu systemd[1]: Started Configure USB flashing port for
Apr 23 16:48:33 tegra-ubuntu nv-l4t-usb-device-mode.sh[658]: /
lines 1-3/3 (END)
root@tegra-ubuntu:~# ./opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh
sudo: ./opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh: command not found
root@tegra-ubuntu:~# bash -x/opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode.sh
bash: -/: invalid option
Usage: bash [GNU long option] [option] …
bash [GNU long option] [option] script-file …
GNU long options:
–debug
–debugger
–dump-po-strings
–dump-strings
–help
–init-file
–login
–noediting
–noprofile
–norc
–posix
–rcfile
–restricted
–verbose
–version
Shell options:
-ilrsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
Can you please remove the extra dot before “/opt” from the beginning of the command and retry:
root@tegra-ubuntu:~# ./opt/nvidia/l4t-usb-device-mode/nv-l4t-usb-device-mode-stop.sh