Custom keyboard firmware based on FW16-Bisect

Creators & Developers Input Module
1

Get my new firmware here:

Main problem:

  • Keypad:
    • Right now, when Numlock is on, all keys work as normal.
    • When Numlock is off, + become “backlight breathing toggle”, and Enter become “backlight level toggle”.
    • This is super annoying, sometimes I want to use my Enter key when numlock is off.

My modifications:

  • On ALL keyboards:

    • Disable via support. You can no longer use web interface. Easier reflashing, since via offer limited usefulness.

  • On Numpad

    • Backlight breathing toggle become “esc” + “=”
      • Planning to have breathing be tied in to state of numlock as a indicator.
    • backlight brightness toggle become “esc” + “⟵”.

  • Technicals:

    • All keyboards:
      • Disable Via now removes writes to EEPROM. Easier reflashing of firmware.
    • Numpad:
      • Use LT() on ESC button
    • Remove void keyboard_post_init_user(void) (now does nothing)
    • Re-naming of keyboard layers to 0 and 1 (LT currently support only numeric layers)

This should equal to version 0.3.2.

Now that Version 0.3.2 came out, and enabled “disable keyboard while lid is down”. The closest I can find is FW16-bisect

Known Issues:

xavier@LAPTOP-3010014:/mnt/Volume_A1/qmk_firmware$ gmake SKIP_GIT=yes framework/numpad:default

...
Generating: .build/obj_framework_iso_default/src/info_deps.d                                        [OK]
arm-none-eabi-gcc (15:13.2.rel1-2) 13.2.1 20231009
Copyright (C) 2023 Free Software Foundation, Inc.
...
Linking: .build/framework_numpad_default.elf                                                        [OK]
Creating UF2 file for deployment: .build/framework_numpad_default.uf2                               [OK]
Copying framework_numpad_default.uf2 to qmk_firmware folder                                         [OK]
(Firmware size check does not yet support RP2040; skipping)

So. It’s this.

Not 100% sure if it is my problem, Framework’s problem, or QMK’s problem. My setup indeed use a mismash of versions. However Not 100% sure how it would lead to “multiple target patterns”.

But the pre-compiled binary is up! Just follow simple instructions in Github’s Readme, and you should be all set.

1 Like
Custom QMK firmware?
3

Upcoming changes:

Apparently that is a thing. I do not know this!

4

If you merge that change, you should include a disclaimer that that key will not work properly in Windows. It’s explained in the issue linked from that pull request.

1 Like
5

You could just remove the backlight breathing toggle. I can not understand why it was even on the default keymap which ships on the keyboards.

It’s nothing more than a novelty. I have trouble believing any significant number of people would want it after the novelty wears off. That key really felt like it was left on the keymap by accident. I remember it not even being listed on Framework’s page showing the hotkeys. Which caused a good number of people to not know how to turn it off after accidentally enabling it, and come asking for help. A few thought their keyboard was malfunctioning! It just never belonged / doesn’t belong on the default keymap. Anyone who actually desired it could have added it with Via.

1 Like
6

Wasnt the breathing toggle for the main keyboard Fn + B?
I cant seem to trigger it Its Fn + C.
Yeah not too sure. I still think mapping it to say for example numlock indication is a good idea, though.

Right, its the same thing with that equal key on Mac keyboards.
Idk; seems like a worthwhile tradeoff because your normal keyboard will have … ooh. yeah. Mmm.
Time to test if Windows does anything at all. In theory you can have a calculator program read direct keyboard codes and do stuff.