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.
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?
Most helpful comment
This is probably because the ATSAM HID report descriptor only declares usages up to
0x65, and the F13-F24 keys are0x68through0x73. If you change the Usage Maximum and Logical Maximum to0xFFit should work.