Jetson NX booting problem

I’ve encountered a very strange bug, if I connect USB port devices before powering up (I connect a camera and a Pixhawk 6C flight controller), then I can’t start my NX properly, and the monitor shows “no signal”.
However, if I unplug the USB devices and start the NX, it boots up and goes to the desktop without any problems. Plugging in my USB device after booting up doesn’t show any problems either.
What is the reason for this? Plugging and unplugging USB devices is a pain in the ass and is causing me a lot of problems, is there anything I can do to fix it?

Is there a chance that your USB is connected to the micro-OTG USB port which has serial console? If so, then seeing a keystroke within the boot chain at the correct moment is used to drop into serial console kernel or boot command prompt. If you have several USB devices, and one of them goes to the micro-OTG port, try unplugging just that port and see if it still boots.

If that is not the case, then it is probably a power consumption issue.

I’ve tried unplugging the USB ports one by one and trying to boot it, but it seems not work. I guess my camera and flight controller don’t have serial console or other similar functions.

My power adapter is a 19V3A. It should be able to provide adequate power.

Is there any other way I can try to fix this?
Much appreciated!

Serial console is separate from other software, and runs even during boot stages. If something is connected to that particular USB port, then it is possible boot stopped because it thinks someone hit a key on the keyboard and is telling boot to pause. If it really is one of the other USB devices going to some other port (one port is device mode only and is the only port used with serial console), then perhaps it is a power consumption issue.

Can you boot with monitor and keyboard/mouse working? If not, does ssh work? What I’m trying to do is to get you to monitor “dmesg --follow” with the system booted, and then look to see what log lines are appended as a result of plugging in each device which fails one at a time. If it boots with keyboard and mouse, that’s good, you could leave them connected. I just want to see the logs of the plug-in event for the devices which cause failure.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.