Tried to install OS using SDK Manager at AGX Xavier.
My SDK Manager is latest.
To flash into the device, the error came out as “Default IP is not available”.
The screenshot is attached. What could be wrong?
Do you have type C connect to the board’s flash port?
Is your board already booting up? This IP is only ready after the OS is ready.
You can skip it first.
I think you can choose to flash the Image first but not install the SDK.
After the image is flashed, then choose to install SDK only.
An additional test if you think the Jetson is fully booted and should show an IP address: Monitor “dmesg --follow” on the host PC, and then replug the USB-C connector. See what the logs show. If the Jetson really is booting, then the virtual network device is quite reliable, but it is also common that a host PC might ignore such a device due to security (in which case the end user would have to tell the host PC that it is ok to use that network device…the dmesg should show clues on that).
I just did what you described.
Before OS & SDK are about to flash, took out USB C connector.
Then type “dmesg --follow” on host PC.
Plugin the USB-C connector back. The message shows on Host PC is as follows
When I take out USB C connector, the message came out, and put back it is detected.
[ 529.449722] usb 3-14: USB disconnect, device number 8
[ 532.689230] usb 3-14: new high-speed USB device number 9 using xhci_hcd
[ 532.837935] usb 3-14: New USB device found, idVendor=0955, idProduct=7019
[ 532.837939] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 532.837942] usb 3-14: Product: APX
[ 532.837943] usb 3-14: Manufacturer: NVIDIA Corp.
The full dmesg messages are as follows.
[ 11.903030] nvidia-uvm: Loaded the UVM driver, major device number 236.
[ 12.154842] Adding 1000444k swap on /dev/sda3. Priority:-2 extents:1 across:1000444k FS
[ 12.419668] audit: type=1400 audit(1645836997.438:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=757 comm="apparmor_parser"
[ 12.420696] audit: type=1400 audit(1645836997.442:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=759 comm="apparmor_parser"
[ 12.420859] audit: type=1400 audit(1645836997.442:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=752 comm="apparmor_parser"
[ 12.420861] audit: type=1400 audit(1645836997.442:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=752 comm="apparmor_parser"
[ 12.420863] audit: type=1400 audit(1645836997.442:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=752 comm="apparmor_parser"
[ 12.420865] audit: type=1400 audit(1645836997.442:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=752 comm="apparmor_parser"
[ 12.421386] audit: type=1400 audit(1645836997.442:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=751 comm="apparmor_parser"
[ 12.421389] audit: type=1400 audit(1645836997.442:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=751 comm="apparmor_parser"
[ 12.421402] audit: type=1400 audit(1645836997.442:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=761 comm="apparmor_parser"
[ 12.421688] audit: type=1400 audit(1645836997.442:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=758 comm="apparmor_parser"
[ 13.832140] snd_hda_intel 0000:03:00.1: azx_get_response timeout, switching to polling mode: last cmd=0x000f0001
[ 13.832154] snd_hda_intel 0000:02:00.1: azx_get_response timeout, switching to polling mode: last cmd=0x000f0001
[ 14.847445] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 15.064710] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/0000:03:00.1/sound/card2/input14
[ 15.064761] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/0000:03:00.1/sound/card2/input15
[ 15.064804] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/0000:03:00.1/sound/card2/input16
[ 15.064847] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/0000:03:00.1/sound/card2/input17
[ 15.064871] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:02:00.1/sound/card1/input18
[ 15.064917] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:02:00.1/sound/card1/input19
[ 15.064947] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:02.0/0000:02:00.1/sound/card1/input20
[ 15.064981] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:02.0/0000:02:00.1/sound/card1/input21
[ 15.082634] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 15.085356] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 15.340192] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 15.543114] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 19.390286] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 19.390317] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 89.768627] usb 3-14: new high-speed USB device number 5 using xhci_hcd
[ 89.917320] usb 3-14: New USB device found, idVendor=0955, idProduct=7019
[ 89.917324] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 89.917326] usb 3-14: Product: APX
[ 89.917328] usb 3-14: Manufacturer: NVIDIA Corp.
[ 309.941478] usb 3-14: USB disconnect, device number 5
[ 343.895751] usb 3-14: new high-speed USB device number 6 using xhci_hcd
[ 344.044478] usb 3-14: New USB device found, idVendor=0955, idProduct=7019
[ 344.044482] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 344.044484] usb 3-14: Product: APX
[ 344.044486] usb 3-14: Manufacturer: NVIDIA Corp.
[ 387.414195] usb 3-14: USB disconnect, device number 6
[ 393.652170] usb 3-14: new high-speed USB device number 7 using xhci_hcd
[ 393.800819] usb 3-14: New USB device found, idVendor=0955, idProduct=7019
[ 393.800823] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 393.800826] usb 3-14: Product: APX
[ 393.800827] usb 3-14: Manufacturer: NVIDIA Corp.
[ 399.948331] usb 3-14: USB disconnect, device number 7
[ 404.572262] usb 3-14: new high-speed USB device number 8 using xhci_hcd
[ 404.720855] usb 3-14: New USB device found, idVendor=0955, idProduct=7019
[ 404.720859] usb 3-14: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 404.720861] usb 3-14: Product: APX
[ 404.720863] usb 3-14: Manufacturer: NVIDIA Corp.
if the automated setup which is selected as per the screenshot doesn’t work
an option maybe to try [manual setup]
The latter, however,
will require to put the device into the recovery mode manually by pressing buttons
Moreover, the recovery usb-C port of the AGX Xavier that is at the side of 40 pin header, will still need to be connected to Host PC.
1 Like
Yes it worked with manual installation.
So auto mode, I don’t need to put Xavier in recovery mod?
yes and no
it is not entirely true neither it works all the time
it is supposed that selecting auto mode for Jetson unit with Running OS will put it to recovery mode automatically
if that doesn’t happen then manual mode is the way to go
It is useful to keep in mind that the recovery mode Jetson does not have network connectivity, but if flash completes, then the unit reboots and it is self-changed to no longer be in recovery mode. The trick of “dmesg --follow” log monitoring has two cases:
- Recovery mode log messages.
- Fully booted mode log messages.
It is the latter you want to try the dmesg trick with to see what the host says about networking.
1 Like
Ip address of AGX Jetson can be requested by sdkmanager only in the two cases below:
- if “Automatic mode” is chosen for putting the unit into recovery mode that will require Jetson OS reacheable over LAN via the specified ip address in order to put the device into the recovery mode via ssh which doesn’t exclude the requirement to get USB-C recovery port connectivity for flashing.
- after flashing is completed, at the “flashing components” momentum.
However, given there is USB cable connectivity while flashing, the second case will most definitely default to 192.168.55.1 for USB-LAN interface of the Jetson.
Moreover, given the “manual mode” is chosen in the first case , the ip address of Jetson will not be required for flashing at all or otherwise up to the momentum of “flashing sdk components” step which is optional. So, the latter can be skipped at all or postponed on after the Jetson is fully booted/operational.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.