Re: Touchscreen "TSTP MTouch"
On 5/7/21 7:29 PM, Oliver Fromme wrote: Hi, I'm not sure if this is the right place to ask ... This is the first time I'm trying to get this sort of device to work, so please be gentle. :-) I've bought a 7" touchscreen. It's intended for an RPi, but it can also be connected to a standard PC via HDMI + USB, which is what I do. Vendor & product ID is 0x0416 & 0xc168. The actual display works fine with Xorg as usual. But I'm having problems getting the touch feature to work. According to the vendor, it's a standard USB HID interface that works without additional driver in Windows, and is also supported by Linux (apparently for several years already). It's supposed to work out of the box with typical Linux distributions on the RPi. Hi, Webcamd may need to be compiled with a special option to attach to your device. See "make config" in the port. Should create an evdev which you should be able to reach via X11. System: FreeBSD 13.0-STABLE-20210418 amd64 CUSE: Cuse v0.1.36 @ /dev/cuse webcamd port: webcamd-5.10.6.1_2 I've created a small devd snipped that starts the webcamd service when the vendor ID and product ID are matched. These are the log messages when I insert the USB plug: Does "webcamd -l" list the device? If you start it from the command line, does it attach? You may also want to trace the USB traffic: usbdump -i usbus0 -f 2 -s 65536 -vvv To see why "error reading report description" fails. --HPS 16:43:17 kernel: ugen0.2: at usbus0 16:43:17 kernel: ums1 on uhub2 16:43:17 kernel: ums1: on usbus0 16:43:17 kernel: ums1: error reading report description 16:43:17 kernel: device_attach: ums1 attach returned 12 16:43:17 kernel: ums1 on uhub2 16:43:17 kernel: ums1: on usbus0 16:43:17 kernel: ums1: error reading report description 16:43:17 kernel: device_attach: ums1 attach returned 12 16:43:19 webcamd[75654]: webcamd: Cannot find USB device 16:43:20 webcamd[75646]: webcamd: Cannot find USB device I tried both USB3 and USB2 ports; same result. The output from ``usbconfig dump_all_desc'' is attached below. At this point I'm not sure how to proceed. Is there anything I can do? Or is this a lost case? On a related note, are there any touchscreens that are *known* to work with FreeBSD? I tried searching the web, but wasn't able to find anything useful. Regards - Olli ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0416 idProduct = 0xc168 bcdDevice = 0x iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0049 bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00a0 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0xdf, 0x08 | 0x02 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0005 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0008 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x8e, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0008 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0004
[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 Bjoern A. Zeeb changed: What|Removed |Added Assignee|u...@freebsd.org |b...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Flickering connection to UPS (again, but now I'm sure it is Ok under Windows)
On 07.05.2021 17:14, Hans Petter Selasky wrote: ster kernel: xhci_roothub_exec: port status=0x000202a0 May 7 14:39:08 hamster kernel: xhci_roothub_exec: type=0x23 request=0x01 wLen=0x wValue=0x0010 wIndex=0x0002 May 7 14:39:08 hamster kernel: xhci_roothub_exec: UR_CLEAR_PORT_FEATURE May 7 14:39:08 hamster kernel: xhci_device_state_change: May 7 14:39:08 hamster kernel: ugen0.6: at usbus0 (disconnected) The value reported by XHCI PORTSC, 0x000202a0, indicates: BIT5-8 : 5) Link is in the RxDetect State BIT9 : Port Power (PP) – RWS. Default = ‘1’ BIT17 : Connect Status Change (CSC) It is clear that the XHCI controller has received a disconnect event from the UPS. Can you check the other OS'es where this supposedly does not happen, if the UPS device attaches to the XHCI or EHCI controller? Windows 10 Device Manager shows it under "Intel(R) USB 3.1 eXtensible Host Controller". This laptop (with Windows 10) has only USB-C ports... I've captured sessions on Windows with "Device Monitoring Studio" and WireShark (it was two sessions, not one) and uploaded them at http://lev.serebryakov.spb.ru/_sklad/ups/ ups-windows-dms.dump - dump from "Device Monitoring Studio" ups-windows-dms.log - log from "Device Monitoring Studio" ups-windows-wireshark.pcapng - dump from WireShark ups-windows-wireshark.txt- dissection export from WireShark. My FreeBSD laptop (Lenovo T540p) has both USB 2.0 an USB 3.0 ports, and UPS flickers in both. Did you start any driver for the UPS? On FreeBSD — I'm not (`nut` supports this UPS, but it detects device slower than UPS stay connected). Windows 10, Windows installs something generic and not very useful (it shows battery level as 0%), but "provided" software (very crude one) works and shows plausible information. Windows 10 shows it as "HID UPS Battery" in device manager. -- // Lev Serebryakov ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Touchscreen "TSTP MTouch"
Hi, I'm not sure if this is the right place to ask ... This is the first time I'm trying to get this sort of device to work, so please be gentle. :-) I've bought a 7" touchscreen. It's intended for an RPi, but it can also be connected to a standard PC via HDMI + USB, which is what I do. Vendor & product ID is 0x0416 & 0xc168. The actual display works fine with Xorg as usual. But I'm having problems getting the touch feature to work. According to the vendor, it's a standard USB HID interface that works without additional driver in Windows, and is also supported by Linux (apparently for several years already). It's supposed to work out of the box with typical Linux distributions on the RPi. System: FreeBSD 13.0-STABLE-20210418 amd64 CUSE: Cuse v0.1.36 @ /dev/cuse webcamd port: webcamd-5.10.6.1_2 I've created a small devd snipped that starts the webcamd service when the vendor ID and product ID are matched. These are the log messages when I insert the USB plug: 16:43:17 kernel: ugen0.2: at usbus0 16:43:17 kernel: ums1 on uhub2 16:43:17 kernel: ums1: on usbus0 16:43:17 kernel: ums1: error reading report description 16:43:17 kernel: device_attach: ums1 attach returned 12 16:43:17 kernel: ums1 on uhub2 16:43:17 kernel: ums1: on usbus0 16:43:17 kernel: ums1: error reading report description 16:43:17 kernel: device_attach: ums1 attach returned 12 16:43:19 webcamd[75654]: webcamd: Cannot find USB device 16:43:20 webcamd[75646]: webcamd: Cannot find USB device I tried both USB3 and USB2 ports; same result. The output from ``usbconfig dump_all_desc'' is attached below. At this point I'm not sure how to proceed. Is there anything I can do? Or is this a lost case? On a related note, are there any touchscreens that are *known* to work with FreeBSD? I tried searching the web, but wasn't able to find anything useful. Regards - Olli ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0416 idProduct = 0xc168 bcdDevice = 0x iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0049 bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00a0 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0xdf, 0x08 | 0x02 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0005 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0008 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x8e, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0008 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0004 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0008 bRefresh = 0x bSynchAddress = 0x -- Oliver Fromme, Munich ``We are all but compressed light'' - Albert Einstein ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Flickering connection to UPS (again, but now I'm sure it is Ok under Windows)
On 5/7/21 1:55 PM, Lev Serebryakov wrote: On 06.05.2021 21:07, Hans Petter Selasky wrote: What does usbconfig say? Ok, now I have laptop with fresh CURRENT. Its usbconfig says (without/with UPS): ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (50mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (50mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen0.6: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) Can you enable host controller debugging: hw.usb.xhci.debug=17 hw.usb.ehci.debug=17 hw.usb.uhci.debug=17 hw.usb.ohci.debug=17 900Kb of dump from first connect to last disconnect is here: http://lev.serebryakov.spb.ru/_sklad/ups-flickr-one-cycle.txt Hi Lev, ster kernel: xhci_roothub_exec: port status=0x000202a0 May 7 14:39:08 hamster kernel: xhci_roothub_exec: type=0x23 request=0x01 wLen=0x wValue=0x0010 wIndex=0x0002 May 7 14:39:08 hamster kernel: xhci_roothub_exec: UR_CLEAR_PORT_FEATURE May 7 14:39:08 hamster kernel: xhci_device_state_change: May 7 14:39:08 hamster kernel: ugen0.6: at usbus0 (disconnected) The value reported by XHCI PORTSC, 0x000202a0, indicates: BIT5-8 : 5) Link is in the RxDetect State BIT9 : Port Power (PP) – RWS. Default = ‘1’ BIT17 : Connect Status Change (CSC) It is clear that the XHCI controller has received a disconnect event from the UPS. Can you check the other OS'es where this supposedly does not happen, if the UPS device attaches to the XHCI or EHCI controller? Did you start any driver for the UPS? --HPS ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: Flickering connection to UPS (again, but now I'm sure it is Ok under Windows)
On 06.05.2021 21:07, Hans Petter Selasky wrote: What does usbconfig say? Ok, now I have laptop with fresh CURRENT. Its usbconfig says (without/with UPS): ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (50mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (50mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen0.5: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) ugen0.6: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) Can you enable host controller debugging: hw.usb.xhci.debug=17 hw.usb.ehci.debug=17 hw.usb.uhci.debug=17 hw.usb.ohci.debug=17 900Kb of dump from first connect to last disconnect is here: http://lev.serebryakov.spb.ru/_sklad/ups-flickr-one-cycle.txt -- // Lev Serebryakov ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
