You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pico and mouse are both stuck, and can only be restored by restarting Pico. After a while, they are stuck again
What happened ?
Pico and mouse are both stuck, and can only be restored by restarting Pico. After a while, they are stuck again. But if you use a receiver connection, there won't be any problem
How to reproduce ?
Connect a wired connection to Logitech G903 on the USB host of RP2040
Debug Log
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered:
[1] Claimed EP 0x81
Queue EP 81 with 8 bytes ...
OK
HID set config: itf = 1
HID Set Idle
[1:1] Class Request: 21 0A 00 00 01 00 00 00
on EP 81 with 0 bytes: FAILED
HID xfer callback
Get Report callback (1, 0)
[1] Claimed EP 0x81
Queue EP 81 with 8 bytes ...
OK
on EP 00 with 8 bytes: FAILED
[1:1] Control FAILED, xferred_bytes = 8
21 0A 00 00 01 00 00 00
HID Get Report Descriptor
[1:1] Get Descriptor: 81 06 00 22 01 00 97 00
on EP 81 with 0 bytes: FAILED
HID xfer callback
Get Report callback (1, 0)
[1] Claimed EP 0x81
Queue EP 81 with 8 bytes ...
OK
on EP 00 with 8 bytes: FAILED
[1:1] Control FAILED, xferred_bytes = 8
81 06 00 22 01 00 97 00
Operating System
Windows 10
Arduino IDE version
2.33
Board
Raspberry pico
ArduinoCore version
4.11
TinyUSB Library version
3.40
Sketch as ATTACHED TXT
examples/DualRole/HID
/hid_device_report
Compiled Log as ATTACHED TXT
Pico and mouse are both stuck, and can only be restored by restarting Pico. After a while, they are stuck again
What happened ?
Pico and mouse are both stuck, and can only be restored by restarting Pico. After a while, they are stuck again. But if you use a receiver connection, there won't be any problem
How to reproduce ?
Connect a wired connection to Logitech G903 on the USB host of RP2040
Debug Log
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: