Mindvision camera problem in tx2

I have a problem when trying to plug Mindvision camera to tx2 , the syslog show the message as below

new high-speed USB device number 8 using xhci-tegra
[ 2149.256576] usb 1-2.3: language id specifier not provided by device, defaulting to English
[ 2149.268470] usb 1-2.3: New USB device found, idVendor=f622, idProduct=1500
[ 2149.275458] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0

and can’t find any video device created as /dev/video*

how can i solve this problem?

Run “dmesg --follow”. See what shows up on plugin and unplug.

Also, what do you see from “sudo lsusb -d f622:1500 -vvv”?

Thanks linuxdev for reply . I follow the steps you mentioned

been running “dmesg --follow” after unplug the Mindvision and got the message below

[ 128.196533] usb 1-2.3: USB disconnect, device number 5
[ 128.203296] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6

and then plugin again and got the message

[ 390.540895] usb 1-2.3: new high-speed USB device number 6 using xhci-tegra
[ 390.999001] usb 1-2.3: language id specifier not provided by device, defaulting to English
[ 391.011352] usb 1-2.3: New USB device found, idVendor=f622, idProduct=1500
[ 391.018433] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 391.028886] xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6

and from the command “sudo lsusb -d f622:1500 -vvv” shows the message as below

Bus 001 Device 006: ID f622:1500
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0xf622
idProduct 0x1500
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

could you tell me the way to drive the camera well? thanks very much.

This shows the device uses a custom driver:

bInterfaceClass       255 Vendor Specific Class

The dmesg shows USB was working correctly, and if a driver were present, then it would have taken ownership upon plugin…but dmesg did not show a driver taking ownership.

Do you have any information on what driver might be used, e.g., is there an arm64/aarch64 downloadable driver in either binary or source format?

the supplier says the arm64 is not supported, however arm32 is. shall it be very difficult to port arm32 sources to arm64 architecture?

Hard to say. Some arm32 sources work directly as arm64 by simply compiling them in the arm64 environment. Others might have architecture-dependent code. What I suggest is to get to where you can build a kernel which is an exact match of the running system. Then research how to build a module out of tree as a modification of that. Use a module which already is known to work for figuring it out. Then try the arm32 source…you can ask questions on this forum about build errors with the arm32 source, but you’ll probably need to know first that your procedure is valid. Here is a starting URL on basic kernel build:
[url]https://devtalk.nvidia.com/default/topic/1038175/jetson-tx2/tx2i-wifi-support/post/5274619/#5274619[/url]