Unable to setup new Xavier

pleopard · March 11, 2020, 4:36pm

The title states the problem … here’s the steps I’ve taken. Please advise …

Thanks!

Nano started, verified internet access
Connect Nano to Xavier
- Standard USB port on Nano
- Front USB-C port on Xavier
Xavier connected to internet (same switch as Nano is using)
- Green light on switch confirms connection
Xavier Powered Up
- Booted up
- Shell prompt OK
Xavier Instructions
- “Download and run JetPack SDK | NVIDIA Developer”
- On host, opened this URL
Found following download:
“Jetson AGX Xavier series, Jetson TX2 series, Jetson TX1, and Jetson Nano
Download the NVIDIA SDK Manager.
Follow the steps at Install Jetson Software with SDK Manager.”
Clicked link “Download the NVIDIA SDK Manager”
Logged into NVIDIA developer program site
Clicked link “Now you can continue to download the file: NVIDIA SDK Manager”
Resulted in the download of “sdkmanager_1.0.1-5538_amd64.deb”
Ran “sudo apt install sdkmanager_1.0.1-5538_amd64.deb” with following results:
[sudo] password for username:
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package sdkmanager_1.0.1-5538_amd64.deb
E: Couldn’t find any package by glob ‘sdkmanager_1.0.1-5538_amd64.deb’
E: Couldn’t find any package by regex ‘sdkmanager_1.0.1-5538_amd64.deb’

dusty_nv · March 11, 2020, 4:45pm

Hi pleopard, you should flash from an x86_64 PC running Ubuntu 16.04/18.04. Flashing a Jetson from another Jetson isn’t supported.

For more info, please see the SDK Manager system requirements here: https://docs.nvidia.com/sdk-manager/system-requirements/index.html

pleopard · March 11, 2020, 5:41pm

I do not have access to a PC running Ubuntu. I suppose I am out of luck then, no?

dusty_nv · March 11, 2020, 6:10pm

Some forum users are able to use virtual machine on PC to flash, although others have issues with it due to virtual USB connection, so it isn’t officially supported. But if you have no other option, it’s worth a try I suppose. If you setup the VM host options to automatically connect/pass-through the USB device, you stand a greater chance of success. The issue is that the Micro-USB flashing port disconnects/reconnects multiple times throughout the flashing process, which can leave the VM out of the loop if it doesn’t pass-through the USB connection automatically.

pleopard · March 11, 2020, 9:07pm

I got lucky this afternoon and found a loaner PC with a fresh install of Ubuntu 18.04. I followed these steps:

Downloaded the sdk manager on the host
Connected the host from a standard USB port to the USB-C port on the front of the Xavier
Connected a monitor, keyboard, mouse, and internet to the Xavier
Connected the power to the Xavier and powered it on
Pressed the power and reset buttons simultaneously
Went back to the host and started the installation with the sdk manager

I get to the part “SDK Manager is about to install SDK components on your Jetson Xavier AGX” dialog and it asks for an IP address (192.168.55.1 for USB-C detect), user name (used root), password (used correct password). When I click FLASH I get an error “Cannot detect Nvidia Jetson device connected to USB”
I checked:

Cable is connected to host
Jetson Xavier is up and running (in terminal mode)
Ubuntu System Configuration wizard completed? I don’t see how to run that on the Xavier, where is it located?

lsusb does not detect the USB-C …

Help?

Thanks

pleopard · March 11, 2020, 9:25pm

Update …

System is in rescue mode.

Tried:

systemctl default

Got this error : “Failed to start default.target: Operation refused, unit may not be isolated. See system logs …”

Tried:

systemctl status default.target

Replied “Unit default.target could not be found”

Tried:

exit

Got “Restarting system manager configuration. Starting default target. Failed to start default.target: Operation refused, unit may not be isolated”

Ideas?

carolyuu · March 19, 2020, 6:01am

Hi pleopard,

Are you connected USB-C cable on J512 port? (the same with flash port)
Please connect USB-C cable on J512 port and run ‘ifconfig’ on your host machine to check you can see the 192.168.55.1 IP address.
If you still can’t see it, you can try using ‘eth0’ IP address instead of USB device IP address.

pleopard · March 19, 2020, 5:21pm

Right now I cannot even get the Xavier to boot. Here is a log of what I’ve done:

Connect J512 to host
Connect J504 to monitor HDMI
Connect J507 to keyboard
Connect J513 to mouse
Connect J510 to network
Connect J2 to power
Press and hold Force Recovery switch
Press and hold Power switch
Release both FR and Power switches

I get nothing on my screen at this point

From host terminal: ifconfig yields:

pleopard:~
% ifconfig

enp0s25:
flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

  inet 10.25.10.18  netmask 255.255.255.0

broadcast 10.25.10.255

  inet6 fe80::d602:7b01:3e4e:f56f  prefixlen 64  scopeid

0x20

  ether d8:9e:f3:36:d2:42  txqueuelen 1000

(Ethernet)

  RX packets 26414  bytes 32813303 (32.8 MB)


  RX errors 0  dropped 0  overruns 0  frame 0


  TX packets 11710  bytes 1256171 (1.2 MB)


  TX errors 0  dropped 0 overruns 0  carrier

0 collisions 0

  device interrupt 20  memory

0xf7400000-f7420000

ens1:
flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

  ether b4:96:91:22:1b:ee  txqueuelen 1000

(Ethernet)

  RX packets 0  bytes 0 (0.0 B)


  RX errors 0  dropped 0  overruns 0  frame 0


  TX packets 0  bytes 0 (0.0 B)


  TX errors 0  dropped 0 overruns 0  carrier

0 collisions 0

  device memory 0xf7200000-f72fffff

lo:
flags=73<UP,LOOPBACK,RUNNING> mtu 65536

  inet 127.0.0.1  netmask 255.0.0.0


  inet6 ::1  prefixlen 128  scopeid

0x10

  loop  txqueuelen 1000  (Local Loopback)


  RX packets 341  bytes 29531 (29.5 KB)


  RX errors 0  dropped 0  overruns 0  frame 0


  TX packets 341  bytes 29531 (29.5 KB)

    TX errors 0

dropped 0 overruns 0 carrier 0 collisions 0

From host terminal: ping 192.168.55.1 yields:

pleopard:~
% ping 192.168.55.1

PING
192.168.55.1 (192.168.55.1) 56(84) bytes of data.

From
140.165.100.10 icmp_seq=1 Time to live exceeded

From
140.165.100.10 icmp_seq=2 Time to live exceeded

From
140.165.100.10 icmp_seq=3 Time to live exceeded

From
140.165.100.10 icmp_seq=4 Time to live exceeded

From
140.165.100.10 icmp_seq=5 Time to live exceeded

I have a UART cable, will this help? If so I need to know how to connect the pins. All the links to devtalk.nvidia.com that Google reports are not reachable

Please advise

Thanks,

Paul

carolyuu · March 20, 2020, 7:10am

Hi pleopard,

For your steps 7~9, that is put device into recovery mode. On this time, you can use ‘lsusb’ to check on your host machine, then you can see the NVIDIA device as below:
Bus <bbb> Device <ddd>: ID 0955: 7019 Nvidia Corp.

Now please run sdkmanager on your Ubuntu host machine (support 16.04 or 18.04) to start flash image and install sdk compoents.

pleopard · March 20, 2020, 11:50am

How can I type lsusb when I I cannot get the Xavier to boot at all? I have a black screen, no terminal, no text, nothing

pleopard · March 20, 2020, 1:31pm

I left the Xavier overnight and it finally booted. So I did the following:

FROM THE HOST COMPUTER:

pleopard:~
% lsusb

Bus
002 Device 002: ID 8087:8002 Intel Corp.

Bus
002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus
001 Device 002: ID 8087:800a Intel Corp.

Bus
001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus
004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus
003 Device 003: ID 413c:301a Dell Computer Corp.

Bus
003 Device 004: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard

Bus
003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pleopard:~
%

NOTE THAT I CANNOT SEE Bus Device : ID 0955: 7f21 Nvidia Corp. as you wrote

HERE IS A SCREENSHOT OF THE XAVIER CONSOLE:

XAVIER IS CONNECTED TO HOST AS IN THIS PIC, USB-C

pleopard · March 20, 2020, 1:33pm

Another update:

FROM HOST:

pleopard:~ % ifconfig 192.168.55.1

192.168.55.1: error fetching interface information: Device not found

pleopard:~ % ifconfig eth0

eth0: error fetching interface information: Device not found

pleopard:~ %

carolyuu · March 23, 2020, 1:18am

Hi pleopard,

The ‘lsusb’ is type on your host machine (like Ubuntu 16.04 or 18.04), that is check the host machine can detect your Xavier board, then you can start flash image.
After flash completed, please connect HDMI cable to your Xavier board, for first time boot-up, it need do desktop setup process (like username, password, timezone…)
Then you can start install sdk components from your host machine. If you are using 192.168.55.1 usb IP address, please connect USB-C cable. If you are using eth0, please connect ethernet cable.

pleopard · March 23, 2020, 1:22am

With all due respect, you do not seem to understand what I am writing. Can I get someone else to help me with this? This problem has been going on for weeks and we are not getting anywhere. I followed all of your instructions and replied back with the results. I know what lsusb is for and tried that without detecting the Xavier, as I wrote in my last email. Please elevate this case to your supervisor

WayneWWW · March 23, 2020, 3:11am

Hi pleopard,

I think you need to understand why we need to check each step.

First, “lsusb” command is used on your host (x86 pc) when you try to use SDKmanager to flash the xavier. When you put device into recovery mode, use command “lsusb” on your host should show “Bus Device : ID 0955: 7019 Nvidia Corp.”

If you don’t see this line, then you have to check either the usb cable or if device is in recover mode or not.

Above is the procedure for flashing the OS to xavier.

Second, after flashing, xavier would start running and now you need to connect usb keyboard and HDMI monitor to xaiver to configure the user account.

Also, lsusb would only be used when flashing, after xavier boots up, host side would not see xaiver in lsusb.

What we really need to check is

Did you flash the board successfully?
We don’t see any positive comment from you. Only saw you say “xavier finally booted”. It sounds like it is flashed, but even a fresh out-of-box xavier may be able to boot up with some unknown image. So we need to make sure “your board is really flashing with jetpack”

Actually, there is a quick way to flash w/o using sdkmanager. Please go to the download folder of sdkmanager and search a folder name “Linux_for_Tegra” and use command
“sudo ./flash.sh jetson-xavier mmcblk0p1”.

The flash procedure would start if device is in RCM (recovery mode)

Did you see anything from HDMI after xaiver boot up?

BTW, all the commands we are talking about before flash is on host. Your tegra is a brick when under recovery mode so of course it cannot use any command.

pleopard · March 23, 2020, 3:19am

I wrote the following above …

FROM THE HOST COMPUTER:

pleopard:~ % lsusb

Bus 002 Device 002: ID 8087:8002 Intel Corp.

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002: ID 8087:800a Intel Corp.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 003 Device 003: ID 413c:301a Dell Computer Corp.

Bus 003 Device 004: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

pleopard:~ %

NOTE THAT I CANNOT SEE Bus Device : ID 0955: 7f21 Nvidia Corp. as you wrote

HERE IS A SCREENSHOT OF THE XAVIER CONSOLE:

XAVIER IS CONNECTED TO HOST AS IN THIS PIC, USB-C

WayneWWW · March 23, 2020, 3:24am

NOTE THAT I CANNOT SEE Bus Device : ID 0955: 7f21 Nvidia Corp. as you wrote

As I told you, lsusb would not show device after xavier boots up. The screenshot in your post indicated the xavier boots up.

and also as I said, we don’t know whether your xavier is correctly flashed or not. Please put device into recovery mode and see if your host is able to see Nvidia Corp…

If it can, then flash the board and wait for it finish and auto-reboot.

After tegra boots up, you must connect a HDMI monitor to it to configure the user account with the GUI.