New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB-USB: Ducky One 2 Mini #697
Comments
|
This relaxes driver loading conditions in hidboot.h of UHS2. With this patch above the converter recognizes interface 0 as a keyboard now, but I think this is a bug of the keyboard, not intended design. But ... not sure. |
|
Descriptors extracted by usb_desc_dump and parsed by USB Descriptor and Request Parser: https://gist.github.com/tmk/6c9b88c117725446dd768a4270847019 The keyboard doesn't have Boot keyboard interface, it seems Interface0 should be that. |
|
Ducky fixed the issue in new firmware seemingly. TODO: New firmware 1.0.10 is available and should be tested again. |
|
Updated a brand new Ducky One 2 Mini (DKON2061ST) to firmware 1.0.10. |
|
Is there some older firmware version I can downgrade to and get it to work? |
|
Can you share its USB Descriptor here? Please check 'Troubleshoot' in the first post to get USB Descriptor. |
|
I got this using USB Tree Viewer (didn't want to reflash my TMK). Connection Status : 0x01 (Device is connected) Vendor ID : 0x3233 (DuckyChannel International Co., Ltd.) Device Description : USB Composite Device Connection Index : 0x01 (Port 1) bLength : 0x12 (18 bytes) bLength : 0x09 (9 bytes) bLength : 0x09 (9 bytes) bLength : 0x09 (9 bytes) bLength : 0x07 (7 bytes) bLength : 0x09 (9 bytes) bLength : 0x09 (9 bytes) bLength : 0x07 (7 bytes) bLength : 0x09 (9 bytes) bLength : 0x09 (9 bytes) bLength : 0x07 (7 bytes) bLength : 0x09 (9 bytes) bLength : 0x09 (9 bytes) bLength : 0x07 (7 bytes) bLength : 0x04 (4 bytes) |
|
Thank you for the descriptor. They didn't fix the descriptor to mark a interface as boot device. I still have an idea on converter firmware fix to support this keyboard. |
|
Thanks for your reply. |
|
I'm happy to flash improved firmware for testing when the converter is shipped, of course. |
|
Just sent you a direct email with a request for a paypal invoice. |
|
The keyboard doesn't support SET_PROTOCOL request, which ends with STALL. |
The keyboard has no boot keybaord interface and SET_PROTOCOL fails with STALL. Use non-boot interface if there is no boot one. Skip SET_PROTOCOL for non-boot keyboard. tmk/tmk_keyboard#697
|
Fixed at tmk/USB_Host_Shield_2.0@204bc5d and available on repo and keymap editor now. |
Ducky One 2 Mini RGB(DKON2061ST
DKON1861ST) with 1.10/1.09(1.08) firmware doesn't have 'boot protocol' interface, so the converter can't recognize the keyboard.https://gist.github.com/tmk/6c9b88c117725446dd768a4270847019
I believe that this is not their intended desgin, but a glitch.
Interface 0 looks like a boot keyboard interface(6KRO) compatible but it doesn't have boot protocol configuration in descriptor.
Seems that Interface 1 is used for mouse, Interface 2 for report keyboard(NKRO) and Interace 3 for
vendor specific purposeMedia keys.TODO:
The keyboard has DIP switch configuration to enable 6KRO/NKRO mode.
2023-02-01
Ducky One 2 Mini(DKON2061ST) had two issue for USB-USB converter.
(while DKON1861ST model with V1.22 firmware should work without problem. )
https://www.duckychannel.com.tw/en/Ducky-One2-Mini-RGB
Ducky One 2 Mini(DKON2061ST):
Fixed with this commit: tmk/USB_Host_Shield_2.0@204bc5d
The text was updated successfully, but these errors were encountered: