Yes, the above was just for knowledge as @nvl1109 mentions. For reference, any time you use “
lsusb” and want to look at just this device, use “
lsusb -d 054c:094e” (there can be other options, for example, fully verbose using sudo, “
sudo lsusb -d 054c:094e -vvv”). Note that when you paste logs or code into the forum you preserve formatting if you mark it as “code”. Either highlight your content and click on the code icon (looks like “
</>”), or else add a blank line above and below the log, then type in three back quotes (next to the number bar “
1” key, shift has tilde). That line above and below the log would have:
(I escaped that so it will show properly in the forums)
On to the actual device, the USB has done its job and is working correctly. It detected what was there, communicated with it, and announced what was present. At that point no driver took over (this would be because no driver knows how to handle this device…a new driver has to be added, but it isn’t what you would truly call a “USB” driver…it is just a camera driver the USB would pipe to/from).
The logs would have shown which driver loaded if that were loaded, but if you go into the verbose
lsusb (looks like you might have missed using “
sudo”, and thus the logs might be shortened since you need root authority to see all of the USB details, but please mention if the verbose
sudo) you will find “
bInterfaceClass”. Or other mentions of device class or driver requirements. None of those showed any of the “universal” (generic) interface classes (e.g., USB Video Class is a generic camera class and the same driver is used by many cameras). I do see this:
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
The above suggests the camera must have a non-generic driver. There could be one provided simply by adding a kernel module, but if the camera is not part of the kernel source, then you’d need to get it from the vendor. If the vendor makes it available only binary format, then it would need to support
aarch64 architecture. If the vendor provides this as source code, then you’d compile against the current kernel’s configuration. Regardless, your Jetson does see the camera, but the camera does not list because there is no driver.
I looked up some information on the camera, and found this URL:
I see MAC and Windows firmware, but nothing for Linux. Quite possibly the firmware is not needed. If firmware is needed, then it might either be flashed directly to the camera (in which case the firmware would “just work” on any computer it runs from), or it might load at run time (in which case you’d need the firmware on any computer you use with the camera, but an old firmware might still be in place and it might not be fatal even in the latter case to not have the firmware).
What I don’t see is a driver download under Linux. So I saw this URL:
There is mention of other URLs there which might help with getting this working in Linux. I don’t know anything about those other projects, but they are worth examining.