With the display attached instructions, it shows up the nvidia’s logo screen and then goes black after showing no video input. According to instructions, on first time boot, its mean to take you through a setup but it did not prompt me to do that after countless attempts. I am not sure what i am doing wrong? The screen mentions below the big nvidia text “Press escape for boot options” which when does not seem to do anything (i dont think the keyboard even turns on at that point).
So then I tried the instructions for the headless configuration to try to get it running. It mentions “On your computer, use a serial terminal application to connect via host serial port to the developer kit.” I have tried to google alot but I can’t find how to do that (I am new to this). On windows, nothing new would show up in device manager after plugging in the usb to usbc cable (usb on computer side). Then I found out that I need to do something in a software called PuTTY? but I dont know what the Serial Line COM port should be (which I was trying to find in device manager). I tried on linux as well but nothing new would should up after doing “dmesg | grep --color ‘tty’” before and after plugging in the usb.
The display attached version of setup seems simpler to do, but If that does not work, the other option would have to do I suppose. I havnt really dealt with alot of manual serial communication in the past, so I would really appreciate if the replies keep that in mind and provide detailed instructions!
I am not sure what I am doing wrong. I’d appreciate any help with this issue! I am open to getting in contact and maybe even going on a call or something similar for faster resolution. Thank you in advance!
What’s your Linux distribution?
Do you have standalone Ubuntu 18.04 as your host PC?
It is recommended host OS to develop Jetson and also flash the board.
You could refer to the following instruction to setup serial console for Orin devkit. NVIDIA Jetson Orin - Serial Console
For Orin devkit, it uses Micro-USB port for serial console. (/dev/ttyACM0)
In Windows, just re-plug and check which COM port showed up in device manager.
In Linux, you could use the following command to check all tty peripherals.
I am on a Ubuntu 20.04 work laptop, so changing versions for it isn’t feasible.
I did try on both the ubuntu machine and my windows machine, but neither of them showed that it as plugged in (no com ports showed up in device manager, and no additional tty showed up in ubuntu). When I plug it into ubuntu, a message shows up saying “Connection failed: activation of network connection failed.” (not sure if thats just a random error or related to this).
Ubuntu 20.04 will work on the JetPack/SDKM 5.x+ releases (L4T R34.x+). Earlier releases would use 18.04, which also works with newer releases.
If you connected the Jetson to another system, and that other system noticed a virtual network device on the USB, then the implication is that the Jetson is fully booted. You wouldn’t see a network device on a recovery mode Jetson, and on a regular boot this won’t exist unless Linux loaded and reached at least the multi-user.target stage (command line console). You might have nothing more than a GUI problem.
On the Jetson, can you reach a text console with CTRL-ALT-F3 or ALT-F3?
That network connection failed might actually just be a random unrelated error because it has shown up even when the jetson is not connected.
I am not able to reach a text console. On bootup, it shows a screen with the Nvidia logo and then no video output. Keyboard does not seem to work during this period either. I will try to upload a video if it lets me.
Ahh, I was using the type C port since that was what the guide specified. As for the UEFI, I am not sure how to fix that. By the way, was there something to be flashed onto the Orin beforehand?
After using the micro usb port, and running sudo dmesg --follow, and connecting the usb to the laptop, the new text on the terminal was:
[ 7518.103505] usb 1-3: new full-speed USB device number 21 using xhci_hcd
[ 7518.231517] usb 1-3: device descriptor read/64, error -71
[ 7518.467514] usb 1-3: device descriptor read/64, error -71
[ 7518.703503] usb 1-3: new full-speed USB device number 22 using xhci_hcd
[ 7518.831516] usb 1-3: device descriptor read/64, error -71
[ 7519.067515] usb 1-3: device descriptor read/64, error -71
[ 7519.175578] usb usb1-port3: attempt power cycle
[ 7519.587505] usb 1-3: new full-speed USB device number 23 using xhci_hcd
[ 7519.587629] usb 1-3: Device not responding to setup address.
[ 7519.795630] usb 1-3: Device not responding to setup address.
[ 7520.003505] usb 1-3: device not accepting address 23, error -71
[ 7520.131513] usb 1-3: new full-speed USB device number 24 using xhci_hcd
[ 7520.131630] usb 1-3: Device not responding to setup address.
[ 7520.339630] usb 1-3: Device not responding to setup address.
[ 7520.547503] usb 1-3: device not accepting address 24, error -71
[ 7520.547586] usb usb1-port3: unable to enumerate USB device
On windows, a notification pops up saying USB device not recognized and in device manager, it shows up as unknown usb device (device descriptor request failed).
I tried the sudo dmesg --follow again after a reboot, but the same story. I have attached a screenshot below (usb was connected after the red line)
I was unable to get the serial console to show up.
On ubuntu, after plugging in usb to micro usb (usb on laptop side), /dev/ttyACM0, /dev/ttyACM1, /dev/ttyACM2, /dev/ttyACM3 show up. None of them seemed to work on minicom. Also, the 4 mentioned ACMs, were a little finicky with sometimes not showing up, so I had to replug things a bunch of times.
Since this is my first time dealing with minicom and serial com like this, I’ll put screenshots incase I am making a dumb mistake.
The image below shows the result of what all the ACM ports show. It stays on this screen and nothing shows up. At the bottom, it shows offline. (I dont know why it shows the year as 2019 lol)
You could try to set “Hardware Flow Control” to “No” to interact in the console.
There’s no significant error from the serial console log.
Is it still black on your monitor at this moment?
It seems no oem-config setup at this moment, you might set username and password before.
Please use SDKM with Ubuntu PC to re-flash the board and reset them.
Following the guide mentioned above, I am encountering issues. It gives an error when I try to flash it. I am also not sure what they mean by connect the power type C cable but powered off, the pc would just not detect it then? I tried powering it off by holding the power button. and then did steps 4, 5 and 6 which turned it back again. What does step 3 mean exactly? Edit: I have also tried keeping the usbc plugged in but the outlet not being plugged in to the wall on the other end but that did not work either, incase that is what the guide meant.
Also, the guide says to “Ignore 7, OEM configuration” and to do it after flashing. Is there a reason for that, or can i just do it in this step like shown in the screenshot, since the guide’s OEM config link also doesnt work.
On Step 2, it says “Target HW image location can not be changed since it is already installed at {location}. To change the location, please uninstall the target image first.”
I had previously installed at that location, however that location no longer holds anything so I am not sure why it wont let me change it. The “change” is greyed out.
Also, to confirm, once the jetson is in force recovery mode, flashing can simply happen instead of anything to do with power like the guide is saying? The step 5 from the guide you shared, in manual setup, the instructions on the screenshot say “make sure the device is connected to the power adapter, but powered off.” I am not too sure what that means like I described in my previous message.
I have been successfully able to flash it, and GUI on the monitor seems to be working well too. Thank you for the support provided! The above question is still a mystery tho since it seems like it worked but Im not sure if selecting the wrong option leads to something else or not.
