The default keymap is laid out on the assumption that it will be used in the MacOS/US keyboard environment. Feel free to get creative and experiment with keymaps that match your preferences.
This self-made keyboard use the QMK firmware, described above. The QMK firmware is highly customizable, and you can unlock a lot functionality simply by editing the keymap.
When customizing a keymap, start by making a copy of the qmk_firmware/keyboards/keycapsss/kimiko/keymaps/default folder and modifying that directory's internal keymap.c file.
Please refer to the official QMK documentation for the key codes and programming specifics.
After changing the keymap,
make keycapsss/kimiko:default:flashIf you get an error, please double-check the board, connection and command.
Pro Micro and Puchi-C/Elite-C have different bootloader. Edit the rule.mk file in your keymap folder and add the following line to it.
BOOTLOADER = atmel-dfuBOOTLOADER = caterinaIf you use the command make keycapsss/...:flash, it read the bootloader settings from the rule.mk and uses the right flashing software.
If you don't have set the BOOTLOADER setting, you can change the command to make keycapsss/...:caterina for Pro Micro, or make keycapsss/...:dfu for Puchi-C/Elite-C
More information on the official QMK site.
You can tell each side of the Keyboard, whether it's left or right, by writing it into it's eeprom.
In order to do so, first put #define EE_HANDS into your config.h.
Then flash the keymap with
make keycapsss/kimiko:(yourkeymap):avrdude-split-left and
make keycapsss/kimiko:(yourkeymap):avrdude-split-rightrespectively.
If you're using DFU bootloader (in case of the Puchi-C), replace the avrdude with dfu
From then on, your keyboard will know, which side they are, no matter which side you plug in. You won't have to use the flags again when flashing an update of your keymap.
If you have any problems that aren't answered here, consider joining our discord server at: (https://discord.gg/5Vfa9azMUr)