Hi there, I am in the process of flashing my Jetson TX2 and get to the stage of installing the Jetson OS onto the board. However when it runs for the first time it encounters a USB configuration error as seen in the image attached. The error goes: [FAILED] Failed to start Configure USB flashing port for device mode See ‘systemctl status nv-14t-usb-device-mode.service’ for details. 71.769891] Please complete system configuration setup on desktop to proceed… As such I cannot use my keyboard or mouse to do the system configuration/setup wizard and thus cannot complete flashing the packages to Jetson TX2. I am very new to Jetson TX2 and so any help would be greatly appreciated. My version of Ubuntu is 18.04 LTS and I’m running it as a dual boot with windows on my host machine if that helps. Kind regards, Josiah [1] [2]

Hi there, So it turns out that Leopard Imaging use an entirely different OS image (based on Jetpack 4.2.2) with a dtb file that once installed enables the USB mode. I am glad I reached out to them as without that file I don’t think the USB would’ve worked. Thanks for all your help with this anyway, I’ve learnt a lot about the board itself and how the machines communicate through ssh and micro USB that I didn’t know before. This thread can be closed :)

[3] I made some progress and can get to this screen (before it was the EULA screen). The change i made was flashing from the terminal after creating a user instead of sdkmanager. If only there is a way to ssh into it to log in. Is this not possible through ethernet? I thought it was but I am just too noob to figure it out.

Is only micro usb dead or every usb port are dead?

only USB A is dead. Micro USB is functional HDMI is functional Ethernet I believe is functional I think I have a very similar problem to this person, which I read a while ago but didn’t understand but now it makes more sense. [image] Directly connect to Jetson TX2 over Ethernet Jetson TX2 From the surface pinging 192.168.2.2 I get: connect: Network is unreachable ***Note:This surface has been connected to a RasPi through Ethernet. From the TX2 pinging 192.168.2.1 I get: tx2@tx2:ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. From 192.168.2.2 icmp_seq=1 Destination Host Unreachable From 192.168.2.2 icmp_seq=2 Destination Host Unreachable From 192.168.2.2 icmp_seq=3 Destination Host Unreachable From 192.168.2.2 icmp_seq=4 Destination Host Unreachable … Do I need a crossover cable?

[image] Directly connect to Jetson TX2 over Ethernet Jetson TX2 Been looking at some tutorials online, but they haven’t been very helpful or worked. All I’m trying to do is access the Jetson from a laptop directly through an ethernet cable. But so far the farthest I can get is the ability to ping the Jetson IP, but then the SSH connection is refused. If I connect the Jetson to a network, then I can SSH into it fine; it’s just that the eventual use case will be in the field where it will not have an existing internet connection we can use to connect to it, s… Meant to link entire thread, not just that one reply ^

[image] jjag4724: 192.168.55.1 Is the “ifconfig” showing address 192.168.55.1 on the host PC side? If so, that’s wrong…that should be the Jetson’s IP address. ifconfig on the host PC should show 192.168.55.100. So I’m guessing that ifconfig is from the Jetson, not host. FYI, if address 192.168.55.1 can be pinged from the host PC, and if that address is the one the Jetson has, then this message indicates the ssh server on the Jetson is probably not running: [image] jjag4724: ssh: connect to host 192.168.55.1 port 22: Connection refused (but do verify 192.168.55.1 as being Jetson side, not host PC side) On the Jetson side, if your login name is “user”, what happens if you try to log in from a console and then locally over ssh? ssh user@localhost …does it say connection refused?

Hey there~! I actually may have modified it in my attempt to solve the issue/assign IP addresses. I was attempting to follow a guide (will look it up in a sec) which said to modify the IPv4 addresses and assign a host and a target machine with the respective IP addresses. All that to say, I would not trust exactly what ifconfig shows… It definitely is the host PC side. I cannot login to the the Jetson OS because of the broken USB mode. I can accept it’s wrong as I probably stuffed it up. I can try revert the changes and send the ifconfig again. Thanks for your help!

In response to the second part, I believe it says connection refused but most likely because of the incorrect assignment of IP addresses. Let me resolve that ASAP.

[image] JetPack 4.2 Flashing Issues and how to resolve Jetson TX2 I’ve also been having problems installing Jetpack 4.2 on the TX2. I had two major problems that I’ve finally been able to resolve: Flashing Post flash install of SDK components. Flashing Required me to install python and xterm first. sudo apt-get install python sudo apt-get install xterm Flashing worked after I figured out how to get the TX2 into recovery mode. As stated elsewhere, use lsusb to check that there’s an NVIDIA device connect to the host before trying to flash. It only app… I was following this guide and trying to do step 2.b I researched and added some profiles in “Network Settings”. I have now deleted those profiles

ifconfig enp5s0: flags=4163 mtu 1500 inet6 fe80::fb2c:6977:cb19:4527 prefixlen 64 scopeid 0x20 ether b4:2e:99:a1:dc:3c txqueuelen 1000 (Ethernet) RX packets 1360 bytes 353493 (353.4 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3132 bytes 571303 (571.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xf7600000-f761ffff lo: flags=73 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 77660 bytes 8448255 (8.4 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 77660 bytes 8448255 (8.4 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp4s0: flags=4163 mtu 1500 inet 192.168.0.122 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::fef:1984:2307:183b prefixlen 64 scopeid 0x20 ether 50:e0:85:8a:d5:5e txqueuelen 1000 (Ethernet) RX packets 7919715 bytes 11738935689 (11.7 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2055339 bytes 184280455 (184.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

arp -a ? (192.168.0.55) at on wlp4s0 dlinkrouter (192.168.0.1) at a0:ab:1b:97:4d:f0 [ether] on wlp4s0 This command shows an interesting result. However none of these are the 192.168.55.1 or 192.168.55.100 which we are looking for. Any ideas why?

[FAILED] Failed to start Configure USB flashing port for device mode

Robotics & Edge Computing Jetson Systems Jetson TX2

jjag4724 April 1, 2021, 2:19pm 35

I was following this guide and trying to do step 2.b

I researched and added some profiles in “Network Settings”. I have now deleted those profiles

Topic		Replies	Views
Jetson TX2 Freezes at System Configuration Screen Jetson TX2 boot	25	1962	June 25, 2020
Unable to install SDK components post flashing my Jetson TX2 module Jetson TX2	46	14029	July 23, 2021
My TX2 is turned on, there is no original UNBUNTU system. Jetson TX2	13	1715	July 4, 2019
Jetson TX2 usb port not working after flashing Jetson TX2 reflash	7	301	August 9, 2024
unable install any JetPacks Jetson TX2 Jetson TX2	31	6477	October 28, 2020
JetPack 4.2 Flashing Issues and how to resolve Jetson TX2	67	36757	November 1, 2021
Can't flash the TX2 with SDK manager Jetson TX2 sdkm	13	3694	March 17, 2021
[Jetpack 3.2] Problems flashing TX2 using native Ubuntu host machine Jetson TX2	25	3376	May 13, 2020
Flash issue - Flashing JETSON TX2 using sdk manager-jetpack 4.4 onto target OS HW Jetson TX2 sdkm	28	2334	January 17, 2021
Jetson TX-2 fail to flash; Ubuntu 16; Jetpack 3.1, 3.2 Jetson TX2	32	6649	August 11, 2020

[FAILED] Failed to start Configure USB flashing port for device mode

Related topics