Toggle between HID_PROTOCOL_BOOT and HID_PROTOCOL_REPORT

[moc32]

Operating System

Linux

Board

PIC0 RP2040

Firmware

ex_host_bare_api.zip

What happened ?

Toggling between report and boot mode on mouse interface will block the keyboard interface on logitech wireless keyboard
Tested: K270/M185 and K220/M150

How to reproduce ?

Connect one of these wireless logitech K270/M185 and K220/M150.

Press R to set report mode on mouse interface
Or B to set boot mode

Keyboard will stop responding. You can see on the Ellysis recording that keyboard endpoint is still replying but the host will not process it replies and continues to ask the same request.

Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)

No debug needed

Device attached, address = 1
Device 1: ID 046d:c534
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 0200
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d
idProduct 0xc534
bcdDevice 2900
iManufacturer 1 Logitech
iProduct 2 USB Receiver
iSerialNumber 0
bNumConfigurations 1
Listen to [dev 1: ep 81, wmx 08]
Listen to [dev 1: ep 82, wmx 14]

Screenshots

ellisys record.zip

I have checked existing issues, dicussion and documentation

• I confirm I have checked existing issues, dicussion and documentation.

[moc32]

I have tested the example app and it works with other combo devices and single keyboard and mouse connected over a hub. The only difference with logitech wireless devices is the wMaxPacketSize which is 20 for the mouse endpoint and 8 for the keyboard.
For the other tested devices wMaxPacketSize is less than or equal to 8 bytes.

[moc32]

This issue might look trivial but It looks like an issue with the hardware controller. After toggling the report protocol, the keyboard endpoint get blocked. The host sends request to the keyboard endpoint and the keyboard is replying the IN request but the host is not sending the ACK and restart the IN transfer without firing any interrupt.