Hello,
I am currently using a Jetson AGX Orin 64GB because I needed an indoor version. I tried to reflash the Jetson with SDK Manager, so I started the download without any issues. The Jetson was properly connected, detected, and recognized by my PC. I started flashing the Jetson, then I got a message saying the Jetson was no longer connected. So I tried unplugging it, plugging it back in, etc.
Since then, no PC recognizes the Jetson. I’ve tried with several PCs, on different versions of Ubuntu. Several cables, but nothing works, the Jetson no longer connects to any host.
And before, when I connected the board to a PC, it would open a window displaying LT4-README; now, that no longer happens.
It is interesting to note that all other USB, USB-C, Display ports still work, and when I connect a mouse, for example, to the USB-C port used to flash the board, the mouse works, so the USB port seems to still be functional.
Could you please help me?
Looks like the board is still alive. Are you able to dump dmesg?
Yes, I think that’s it:
dmesg_log.txt (40.3 KB)
Here are the dmesg logs from the Jetson. I must admit that I’m not entirely sure what I’m communicating, as my issue occurred yesterday evening, so I don’t know if the logs have reset.
Actually you should try to reproduce the issue first and then dump out the dmesg log.
You cannot just give me something which you don’t even know. Please be aware that I am just a stranger on the other side of this planet. I won’t know what you really did on your side. I only accept what you shared and analyze that
Yes, you are absolutely right, I apologize for that.
dmesg_log.txt (41.8 KB)
So, here are the logs again with the procedure I followed:
I turned on the Jetson with a keyboard and mouse connected to USB ports 7.
I connected a USB cable between the Jetson and an Ubuntu PC using port 10 (the one for flashing) (the PC does not recognize it).
I tried the same thing with a different cable.
Then I connected a mouse to port 10 to demonstrate.
(The mouse is a device named ROCCAT Burst Pro Air, which works.)
When I mention ports 7 and 10, I am referring to this documentation:
Thanks for the log.
I notice one problem here that below xudc driver log only appears once.
[ 12.236890] tegra-xudc 3550000.usb: Adding to iommu group 8
If the usb device mode is working properly, then it shall have more prints than just this line.
Is this a NV devkit or custom board? or you are uncertain?
If this is NV devkit, then
sudo i2cdump -f -y 0 0x57 (or 0x56) should give out the info of this board.
Yes, here they are:
sudo i2cdump -f -y 0 0x56
No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 02 00 fe 00 00 00 00 00 00 00 00 00 00 00 00 00 ?.?..
10: 00 00 00 0a 36 39 39 2d 31 33 37 33 37 2d 30 30 …?699-13737-00
20: 30 30 2d 35 30 30 20 4b 2e 30 00 00 00 00 00 00 00-500 K.0…
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
40: 00 00 00 00 00 00 00 00 00 00 31 34 32 35 30 32 …142502
50: 33 32 34 34 31 30 30 00 00 00 00 00 00 00 00 00 3244100…
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
90: 00 00 00 00 00 00 4e 56 43 42 00 00 4d 31 00 00 …NVCB..M1..
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
c0: 00 00 00 00 00 00 00 00 36 37 35 2d 31 33 37 33 …675-1373
d0: 30 2d 30 30 35 30 2d 30 30 30 00 00 00 31 34 32 0-0050-000…142
e0: 35 30 32 33 30 30 31 33 30 37 00 00 00 00 00 00 5023001307…
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ce …?
it will be like this:
sudo i2cdump -f -y 0 0x56.txt (1.3 KB)
and normally it’s a development kit
Are you able to do some cross check here?
For example, if you have more than just this device, could you use same host PC + cable on other Jetson to see if they can detect it with same version flashed by sdkm?
Yes, it works. I have already checked this, I’ am sorry. I forgot to tell you this before, but when I check with a Jetson Nano Orin, it works.
(i check again now and it work again.)
Is it possible to do full software reflash on this board? And even some cross version check?
For example, flash it with Jetpack5.1.5 and see if this would give the usb device mode back.
Sorry, I don’t understand. Do you want me to reflash which board? The board with USB issues? If you are talking about this board, how is it possible to reflash without port 10, because according to the documentation, you need USB port number 10. But I have an issue with this port.
Because even SDK Manager on my PC does not recognize and detect the board.
Oh, I think I understand. I didn’t know it was possible to flash the board like an ordinary PC using an ISO file. Actually, do you want me to do it like in this post ? :
This requires some background knowledge here. Let me explain.
-
Yes, I am talking about reflash the board with USB issues.
-
This flash attempt will help clarify something
→ The board detection in recovery mode and kernel stage are different.
On the one hand, when you saw that “L4T-README”, it is usb device mode triggered by Linux kernel driver running on Jetson (that xudc driver I mentioned in previous post). This mode is triggered by type C controller + Jetson USB driver to make it work. Thus, some software are involved here.
On the other hand, when you put the board into recovery mode, you are triggering it by pressing the button on the board itself to make that happened. And if the board is in recovery mode, you host will detect it and you could start to do the flash. In this situation, there is no Linux kernel running on Jetson board. So it is a pure hardware triggered event.
For example, if someone accidentally removed the Jetson USB driver, he/she can still reflash it by using recovery mode. This thing will not be out of function just because USB driver got removed on the board. It does not care about what is the previous state on the Jetson. No matter your Jetson is corrupted or cannot boot. If it is not a hardware problem, then recovery mode can always bring it back to life.
I don’t know whether you ever using recovery mode to flash the board before or you just let sdkmanger do the work for that.
Sdkmanager actually follow this method to flash your board
-
If the usb device mode can still work (that L4T-README thing is still working), then it will use software method to put the board into recovery mode directly and flash.
-
If usb device mode is dead, then you need to manually press the button on the board to trigger recovery mode.
So, I tried the recovery mode like this:
- Press and hold down the Force Recovery button (2).
- Plug in a DC power supply’s USB Type-C plug into the USB Type-C port (4) above the DC jack,
- Or plug a DC plug of a power supply into the DC jack (5).
- If the white LED (0) is not lit, press the Power button (1).
- Release both buttons.
After that, I used the SDK Manager ?
Generally I will release power button first and then release FR button. And rest of steps you said are correct.
Thank you very much for your help! Thanks to your instructions, everything is working perfectly now. I also want to thank you for your patience and for bearing with my incompetence. Your help has been invaluable.
Hi,
Actually this does not mean the issue has been done.
What version of Jetpack did you flash and make the USB able to work again?
Just to clarify. Your attempt to make it alive only showed that this issue could be software bug that we should do some further check.
Hi,
Yes, I understand, but I think the issue occurred only during my first attempt to flash the board. Now, I can use the card without encountering that software issue. I notice several differences:
- The background is not blue (it was blue when I had the issue).
- I can plug in a USB key (before, the board would detect the key but not open it).
- The Wi-Fi card works.
So I think the issue is only with the first flashing of the board, which is not happening correctly.
But I have another question: Can you tell me if there is documentation about the hardware architecture and the various software layers of the AGX Orin Jetson?