In the first and second step works just fine. however, in the third step; when I have to install SDK components to my jetson; my host pc cannot detect the jetson board even after my jetson is flashed and currently running.
When my jetson board is running (in normal mode, not recovery mode) , my host pc cannot detect it (I used command lsusb to check and no Nvidia corp shown), But when my board is in recovery mode, my host pc can detect it using lsusb.
This problem makes me unable to install SDK components on my board, since it need to detect the board or else error occurs. (and when I try to install while the board is in recovery mode, the problem with IP occurs, it said “Default IP is not available”)
Please help me. I am a beginner to jetson and have no idea how to solve this.
If you just want to install the sdk and don’t want to care about why the usb device mode cannot work, then my suggestion is you can directly try ethernet to do the ssh.
For example, connect jetson and your host into same router. If they got IP assigned and can ping each other, then you can use the IP in sdkmanager to install sdk.
If you want to check why usb device mode cannot work, then it is a quite large topic.
To check that, firstly we need to know are you using custom board or devkit.
During a flash the Jetson is in recovery mode, and this turns it into a custom USB device. When the flash completes it automatically reboots, and is no longer in recovery mode. For the moment, the Jetson is no longer any kind of USB device. Once it is fully booted though, the default is to run a service which makes just one of the USB connectors go into device mode if a suitable cable is plugged in (on older models the socket is micro-OTG, which accepts either micro-A or micro-B, which in turn tells the Jetson which type it is via an ID pin; I’m thinking that it is possible the Orin has a USB-C instead of micro-OTG, but I don’t have an Orin Nano, I’m not sure). Using the wrong connector implies it’ll never show up as a USB device. Having the service not start also implies that if Linux is running (not recovery mode anymore), then an emulated standard network router device appears on that port and that port looks like a device instead of looking like a host.
If the end user first account setup is not complete, then adding those optional packages would fail, but that’s different from not seeing the network device on USB (assuming you use the correct USB port). Using the wrong port guarantees failure of the virtual network device. The default of an Ubuntu host PC is that it would allow the virtual network device, but if security is enabled, then this too would cause the host PC to reject that network device. Maybe it is an actual USB error, but most of the time it is something else.
Have you completed first boot account setup? Either locally at the Jetson, or via serial console? If this is working, then on the host PC, run the command “dmesg --follow”. This will continuously monitor the logs. Then plug in the fully booted Jetson’s correct USB cable to the host PC, and post in this thread what log lines show up. Mention which USB port on the Orin Nano you are using.
Hello, Thank you so much for quick reply.
I’ve tried connecting my host pc (ubuntu, dual boost) with jetson directly through crossover ethernet cable. After that, I manually set the ipv4 of the jetson and host to be 10.0.0.1 and 10.0.0.2.
