mirrors/keychron_qmk_firmware
mirrors/keychron_qmk_firmware
0
0
Fork 0
mirror of https://github.com/Keychron/qmk_firmware.git synced 2024-11-27 19:16:40 +06:00
Code Issues Packages Projects Releases Wiki Activity
ee9da1fcf3
keychron_qmk_firmware/keyboards/splitkb/kyria/keymaps/john-ezra
History
john-ezra 79ad30a9d5
[Keymap] Updates to Personal Kyria Keymap (#14669) 
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
2021-10-02 07:50:55 -07:00
..
config.h [Keymap] Updates to Personal Kyria Keymap (#14669) 2021-10-02 07:50:55 -07:00
glcdfont.c [Keymap] Updates to Personal Kyria Keymap (#14669) 2021-10-02 07:50:55 -07:00
keymap.c [Keymap] Updates to Personal Kyria Keymap (#14669) 2021-10-02 07:50:55 -07:00
oled.c [Keymap] Updates to Personal Kyria Keymap (#14669) 2021-10-02 07:50:55 -07:00
readme.md [Keymap] Updates to Personal Kyria Keymap (#14669) 2021-10-02 07:50:55 -07:00
rules.mk [Keymap] Updates to Personal Kyria Keymap (#14669) 2021-10-02 07:50:55 -07:00

readme.md

This Keymap uses the nanoBoot bootloader to maximize available firmware space.

As is, the firmware will be too large if using the standard bootloader. Removing DEBOUNCE_TYPE = sym_eager_pk from the rules.mk should get the size under the limit.

If nanoBoot is not going to be used, delete or comment out the following from your rules.mk:

BOOTLOADER = hid
BOOTLOADER_SIZE = 512
PROGRAM_CMD = 	$(HID_BOOTLOADER_CLI) -mmcu=$(MCU) -w -v $(BUILD_DIR)/$(TARGET).hex

nanoBoot can be found here: nanoBoot I used the string-descriptors branch as it was the latest update.

To ISP Flash nanoBoot: avrdude -p atmega32u4 -c avrisp -U flash:w:/Users/DempseyTech/nanoBoot/nanoBoot.hex:i -P /dev/cu.usbmodem123451 -U lfuse:w:0x7F:m -U hfuse:w:0xD6:m -U efuse:w:0xC7:m

You will need to change the path in the CLI command to match your file structure.

QMK Toolbox will not recognize controllers using nanoBoot, instead use the CLI to flash.

To Flash: qmk flash -kb splitkb/kyria/rev1 -km john-ezra -bl hid_bootloader