Got it. It's a core bug.
In usb_hid.c:hidUSBDataSetup(), there's this code:
usb_generic_control_rx_setup(buffer->buffer, buffer->bufferSize, &(buffer->state));
buffer->state = HID_BUFFER_UNREAD;
That assignment to buffer->state shouldn't be there. usb_generic_control_rx_setup() will set the ...
Search found 3 matches
- Fri Feb 17, 2023 9:33 pm
- Forum: General discussion
- Topic: HID output reports being received twice?
- Replies: 1
- Views: 6664
- Thu Feb 16, 2023 11:14 pm
- Forum: General discussion
- Topic: HID output reports being received twice?
- Replies: 1
- Views: 6664
HID output reports being received twice?
I'm trying to send data _to_ a HID device (it's an LCD and I'm trying to make it work with the Auxiliary Display HID protocol). I'm finding that each incoming report is reported twice, which is really strange. I've checked with Wireshark and the USB packet is sent once, so whatever's going on is ...
- Wed Feb 15, 2023 10:10 pm
- Forum: General discussion
- Topic: Serial half-duplex support, like in the stock STM32 core?
- Replies: 0
- Views: 7659
Serial half-duplex support, like in the stock STM32 core?
As title...
I have a project which requires USB HID stuff _and_ half-duplex serial. It seems much easier to port the stock core's serial driver to the libmaple-based core than porting the USB stack to the stock core! But before I do that, is there an easy way to make this work?
I have a project which requires USB HID stuff _and_ half-duplex serial. It seems much easier to port the stock core's serial driver to the libmaple-based core than porting the USB stack to the stock core! But before I do that, is there an easy way to make this work?