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
What was your steps to flash tx2?
Is this custom carrier board or nv devkit?
Hi there,
Sorry for the delay in my response. We are using Leopard Imaging Carrier Board from this link: LI-JETSON-CB-IMX185M12-H | Leopard Imaging Inc.
The steps taken were:
0. Power off the board but leave it connected to AC power supply
- Hold down reset button
- Press the power button
- Release reset button
- type lsusb into the host machine terminal to ensure that there was a USB connection and it was in reset mode from the address
I mean did you use sdkmanager or some image provided by Leopard?
I used the latest version of the sdkmanager :)
Could you remove the driver package installed by sdkm and let it download again?
Hi Wayne,
I have tried reflashing with several versions of the Jetson OS and uninstalled and reinstalled and I still get the same issue.
I also have removed other peripherals (HDMI cable, ethernet, usb) and I get the same result. The hardware is okay because it worked with the native OS.
Kind regards
This also included deleting the files and redownloading it. Still the same issue. Any help would be greatly appreciated.
Could you contact with Leopard and confirm if their board can work with sdkmanager? Or need their driver?
We have contacted them and are awaiting their reply.
In the mean time is it possible to do a headless start (using peripherals on host machine and using ssh to login)?
I have been trying the script from this post: Jetson Nano all USB ports suddenly stopped working - #36 by Trumany
and
because if I can get past the EULA sign up and login stage, I can hopefully enable bluetooth or at least provide error logs through the ssh connection. Currently I cannot even log in.
Would this work?
Kind regards,
If that tool still works, dump the dmesg for me.
I don’t know whether that tool would still work or not. That was a debug tool on rel32.1.
The tool works to successfully create a user.
However I cannot ssh as when i type in ssh user@192.168.55.1 I get the following error:
ssh: connect to host 192.168.55.1 port 22: Connection refused
I have tried with other ports 2222 and 24 but neither work. Is there a requirement to login at least once on the board first before ssh is allowed?
Is ethernet available on your side?
192.168.55.1 is based on usb port device mode, since that is dead on your side, that won’t work.
1 Like
I have an ethernet cable which I used to connect my host PC to the target board. But I’m not sure if that is the correct configuration
when I type ifconfig I get:
enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.55.1 netmask 255.255.255.0 broadcast 192.168.55.255
inet6 fe80::dc7:d333:e863:a065 prefixlen 64 scopeid 0x20
ether b4:2e:99:a1:dc:3c txqueuelen 1000 (Ethernet)
RX packets 1183 bytes 307554 (307.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3011 bytes 551991 (551.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device memory 0xf7600000-f761ffff
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 66881 bytes 7234877 (7.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 66881 bytes 7234877 (7.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> 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 7886764 bytes 11713003680 (11.7 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2034951 bytes 179950333 (179.9 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Where do you type this command? Host machine?
Hm that is interesting. When I ping that address i get packets received… Does that indicate partial functionality?
yes, everything so far is on host machine as I cannot login or get past the EULA page on the target machine
