libusb backend issue with Teensy HID device #443
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi#443
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From here.
https://github.com/avrdudes/avrdude/blob/main/src/teensy.c#L126-L131
This seems to happen to the libusb backend but not hidraw backend.
You can see from the following results that HID usage reporting is not good for the libusb backend.
@mcuee Could you try, what usbhid-dump returns for this device?
This is a known and documented issue:
github.com/libusb/hidapi@c3ae3d0b58/libusb/hid.c (L729)As I mentioned here - now there is a workaround (ask for USAGE after the device is open).
@Youw
In this case, should I close this issue as this is a known limitation and there is a workaround now?
For avrdude, I am suggesting to use the hidraw backend.
https://github.com/avrdudes/avrdude/issues/1065#issuecomment-1214373729
Lets close it after #438 is resolved - that's another related improvement.
Yes I can confirm that #444 is good for #438 which can serve as the workaround for this issue (to ask for USAGE after the device is open).
When I change the test device to Teensy 2.0.
When I changed the device to the Logitech USB receiver:
A workaround is possible, based on current master.
Oh yes. Thanks for pointing that out. #432 makes the workaround possible, not #444.
avrdude probably will only use the workaround after 0.13 is released.