I want to check logs of Jetson nano on host PC

I followed steps on above site.
Screenshot from 2023-12-08 17-49-09

I can find my Jetson nano on PC. Any more steps to check on recovery mode? Also I want to see its system log, what do I need to do?

I want to see my logs, becuz my Jetson nano got stuck on nvidia logo page. After I executed reboot, it shows only NVIDIA logo and then turn back to black screen.( This repeats) To fix this problem I want to check the logs.

Hi there @pd1025 and welcome to the NVIDIA developer forums.

I think you might want to ask this in the Jetson Nano forums, not DLSS, so I took the liberty of moving your post.


Thank you for your kindness!

I see the NVIDIA device, which has manufacturer ID 0955 (hex). The problem is the product ID is 7f21 (also hex). I don’t know which product this is, but I don’t have an Orin Nano, so it might be an Orin Nano. Which exact device are you using? Basically, you found something with an NVIDIA SoC, but off the top of my head, I don’t know which one is 7f21.

Anyone else, which Jetson is 0955:7f21?

thank you for the comments. Currently I am using Jetson Nano developer kit.

That shows a regular Nano. This should be USB ID 0955:7020. It is possible you got a variant of the Nano. Which distributor did you purchase from?

Can someone from NVIDIA (maybe @WayneWWW) suggest which Nano is USB ID 0955:7f21?

Basically, that ID is used by the flash software to know what to flash. Figuring out what the ID belongs to will probably answer what flash requires, and that particular variant is not the older basic Nano developer kit (maybe it is an eMMC model on a third party carrier board; if you got this from the Seeed studio web site, then it is probably eMMC plus third party carrier board; the Amazon listing is for a regular dev kit).

7f21 is also for jetson nano too.

Thanks for the reply. my jetson nano is stuck on nvidia logo. what do I need to ?

If this is NV devkit, then you need to use usb-ttl cable to dump log.

I followed all the steps until connecting power jack. However unlike the video, I got an error. I attached my error.

Screenshot from 2023-12-10 22-12-55

After this error, I changed my USB port. But still the same error is bothering me:(

Minicom can log the entire session to the host PC. No need for screenshots. I prefer gtkterm, and if the device is ttyUSB0, then it would go like this (you would first “sudo apt-get install gtkterm”):
gtkterm -b 8 -t 1 -s 115200 -p /dev/ttyUSB0

Note that if your user is not a member of group “dialout”, then you need to use sudo with the above command. You can add your user to group dialout like this (I’m pretending your login name is “nvidia”, adjust for your actual login name):
sudo usermod -aG dialout nvidia

In gtkterm (and every serial console, although they vary on actual method) you go into the FILE to clear screen before starting, but in this case you would clear screen right before turning on the Jetson…you want to log everything. Then, start logging to file. You might want to create a file name ahead of time (kind of inconvenient, but otherwise I like gtkterm) like this:
touch ~/jetson_boot_log.txt

If cable is attached, start screen is cleared, and logging has begun, then turn on the Jetson. Let it go until it can’t continue. If you can log in, do so, and then:
cat /var/log/Xorg.0.log

Then you can stop logging, and the log will be on the host PC at ~/jetson_boot_log.txt. Attach that to the forum.

Result of executing $cat /var/log/Xorg.0.log
Xorg.0.log.txt (31.7 KB)


Just a reminder, linuxdev is talking about Xorg.0.log from your jetson. Not from your host.

You need to fix your usb-ttl issue first to proceed.

Please reset the jetson device after you open the minicom console in case it already stuck in some boot process.

When you use a serial console it displays on the host PC, but it is logged in to the Jetson itself. Any commands from login to the Jetson would be recorded. As @WayneWWW mentions though, the file we are interested in is not the one on the host PC.

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