Replies: 2 comments 1 reply
-
Hm maybe that's not it. I just tried a logitech unifying receiver with a paired keyboard; I have to believe this supports the report protocol. Same error with the assertion failure in |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ah. I should not be calling |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a device (random no-name 2.4ghz keyboard/mouse combo receiver) which seems to only support the BOOT protocol. The initial protocol shows up as BOOT. If I try to switch to HID_REPORT_PROTOCOL, the usb stack hangs somewhere. Turning on debugging, I get assertion failures on the tuh_control_xfer call.
This is with somewhat hacked logging (I'm running both device and host; device on rp2040 main usb, and host on Pico-PIO-USB port on core 2); so I attempted to enable logging for the host-side stack only.
Note that if I don't try to set_protocol, I get device instance 1 right after this (my log below). I need to set up a picoprobe/SWD debugger to see what's actually happening above. At the very least I don't get another
tuh_hid_mount_cb
.Is there some way of detecting that the device doesn't support the report protocol, if that's what's actually happening here?
Beta Was this translation helpful? Give feedback.
All reactions