Qmk_firmware: F12 - 24 Keys not working on Massdrop CTRL

Created on 4 Dec 2018  路  7Comments  路  Source: qmk/qmk_firmware

When assigning any keycode between F13-F24, nothing happens when they key is pressed. This happens with both the online configurator when manually building the firmware. register_code() and unregister_code() are also non-functional with these keycodes.

Most helpful comment

This is probably because the ATSAM HID report descriptor only declares usages up to 0x65, and the F13-F24 keys are 0x68 through 0x73. If you change the Usage Maximum and Logical Maximum to 0xFF it should work.

All 7 comments

I think this may actually be an OS issue, and not keyboard/QMK related.

Are you using something to keep track of the outputs and seeing if the OS is receiving anything, at all?

Yep, and the OS isn't receiving anything. Strangely enough if I use another qmk keyboard, the additional f keys work fine. This issue also persists across multiples machines

Are the boards that are having this issue using VUSB, as well?
Eg, do you know what controllers they're using?

The keyboards where the f keys work fine are using a AT90USB646 and a 32u4, whilst the problematic keyboard is using a ATSAMD51J18A.

This is probably because the ATSAM HID report descriptor only declares usages up to 0x65, and the F13-F24 keys are 0x68 through 0x73. If you change the Usage Maximum and Logical Maximum to 0xFF it should work.

That fixed it, thanks!

@M1K8 just to be clear, did you increase both Usage Maximum and Logical Maximum to 0xFF as suggested by @fauxpark for the correct functionality?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

michaeldauria picture michaeldauria  路  3Comments

helluvamatt picture helluvamatt  路  4Comments

drashna picture drashna  路  3Comments

ghost picture ghost  路  3Comments

jetpacktuxedo picture jetpacktuxedo  路  3Comments