Hi,
Do you use Xavier NX developer kit? If it worked and then fails, probably hardware is broken. We would suggest do re-flash and check if it works. If not, may need to do RMA: Jetson FAQ | NVIDIA Developer
@DaneLLL - I thought it was the hardware too so I used my spare Aetina AN810. The USB does not work on either of the AN810. I can SSH into the Jetson, but no USB devices work. I had installed JetPack 4.4 and it worked till now somehow USB got busted. I find it really odd that USB isnt working??
/a
A device tree problem could in theory make USB fail, and this could be related to some sort of update or mismatch in software. However, that’s very unlikely under the circumstances. The reason you should try flashing (and you could use a different SD card), is that it will guarantee that the image and other software within the NX have a matching version. If the SD still fails, then it is extremely likely it is hardware failure.
I am using Aetina AN810 board and Production Module (SOM) so there is no SD Card. After flashing it, we usually move it to use NVME to boot.
I will try to reflash and see if it works.
/a
…ahh, the above is quite important! This implies the device tree must be quite different than what you’d get from the generic NVIDIA dev kit flash software. The hardware might be ok after all!
When you are using a third party carrier board you must use the board support package they provide. The device tree (and possibly kernel) cannot be predicted by NVIDIA, and thus the company producing the board will provide their own customized version of what NVIDIA supplies. The third party flash software will just be a customization of what is published by NVIDIA, but without this, I’d expect some or all of USB to fail.
I usually flash the SOM with the JetPack4.4.1 using the NVIDIA SDK as some applications are not supported in the latest jetpack. I will test it default NVIDIA JetPack to make sure everything is working before I apply the vendors patch and let you know how it works out.
Thanks
/a
If this is a third party carrier board, then using JetPack will fail to work correctly except for those parts of the custom carrier board which are an exact match to the dev kit carrier board. Does the manufacturer of your carrier board provide a board support package for flashing? Use that instead.
@linuxdev - when I purchase the SOM, I just flash it with JetPack 4.4.1 to make sure all is good. Then I usually reflash with the vendor’s patch. Usually the default jetpack will let me configure the make sure the USB etc is all working. Prsently I cannot even reflash it will NVIDIA JetPack 4.4.1 with our without vendor’s patch.
NVIDIA SDK gives the following error:
I can’t answer what the third party carrier board does differently. This is something you should directly ask the manufacturer about. However, I can give some “maybe” advice.
When in recovery mode the Jetsons tend to not care about third party carrier boards versus dev kit boards. Technically, I think “most” Jetsons could be flashed with either third party or dev kit flash software when mounted to any carrier board, but most debugging to know about a true recovery mode failure requires the dev kit carrier board.
The eMMC version of module will differ versus the SD card model. I don’t know if you could expect the eMMC model to function (fully) on the dev kit carrier board, but probably it would work if given the correct device tree. Almost certainly there would be issues in using the eMMC module with the wrong device tree on any of the carrier boards, and USB would be a prime candidate for “wrong device tree”.
Do you have a dev kit carrier board you can test flash on? I would say that if the module has problems flashing with the dev kit software on the dev kit carrier board, then it might be time to RMA (though it would also require seeing flash logs in case it is something simple going on in software and not a hardware issue). Certainly it is possible that the carrier board itself is at issue, and if it is a third party carrier board, then the module would be ok and you’d need a new carrier board.
You are in a tough situation because I think you need a second (dev kit) carrier board to really confirm. Or you need the company with that carrier board to confirm. Without the right combination of carrier board and module to test with there will always be some guessing.
Do note that seeing the Jetson with lsusb while in recovery mode is a sign the module is probably good, and perhaps at least part of the carrier board is also good.