- Install WinAVR Tools for AVR GCC compiler.
- Install DFU-Programmer (the -win one).
- Start DFU bootloader on the chip first time you will see 'Found New Hardware Wizard' to install driver. If you install device driver properly you can find chip name like 'ATmega32U4' under 'LibUSB-Win32 Devices' tree on 'Device Manager'. If not you will need to update its driver on 'Device Manager' to the
dfu-programmer
driver.
- Install CrossPack or install Xcode from the App Store and install the Command Line Tools from
Xcode->Preferences->Downloads
. - Install DFU-Programmer.
- Install AVR GCC with your favorite package manager.
- Install DFU-Programmer.
##Verify Your Installation
- Clone the following repository: https://github.com/jackhumbert/tmk_keyboard
- Open a Terminal and
cd
intotmk_keyboard/keyboard/planck
- Run
make
. This should output a lot of information about the build process.
Here is a list of some of the functions available from the command line:
make clean
: clean the environment - may be required in-between buildsmake
: compile the codemake KEYMAP=<keymap>
: compile with the extended keymap fileextended_keymaps/extended_keymap_<keymap>.c
make dfu
: build and flash the layout to the PCBmake dfu-force
: build and force-flash the layout to the PCB (may be require for first flash)
Generally, the instructions to flash the PCB are as follows:
- Make changes to the appropriate keymap file
- Save the file
make clean
- Press the reset button on the PCB/press the key with the
RESET
keycode make <arguments> dfu
- use the necessaryKEYMAP=<keymap>
and/orCOMMON=true
arguments here.
Unlike the other keymaps, prefixing the keycodes with KC_
is required. A full list of the keycodes is available here. For the keycodes available only in the extended keymap, see this header file.
You can use modifiers with keycodes like this:
LCTL(KC_C)
Which will generate Ctrl+c. These are daisy-chainable, meaning you can do things like:
LCTL(LALT(KC_C))
That will generate Ctrl+Alt+c. The entire list of these functions is here:
LCTL()
: Left controlLSFT()
/S()
: Left shiftLALT()
: Left alt/optLGUI()
: Left win/cmdRCTL()
: Right controlRSFT()
: Right shiftRALT()
: Right alt/optRGUI()
: Right win/cmd
S(KC_1)
-like entries are useful in writing keymaps for the Planck.
A number of other keycodes have been added that you may find useful:
CM_<key>
: the Colemak equivalent of a key (in place ofKC_<key>
), when using Colemak in software (CM_O
generatesKC_SCLN
)RESET
: jump to bootloader for flashing (same as press the reset button)BL_STEP
: step through the backlight brightnessesBL_<0-15>
: set backlight brightness to 0-15BL_DEC
: lower the backlight brightnessBL_INC
: raise the backlight brightnessBL_TOGG
: toggle the backlight on/off
The extended keymap extends the number of function layers from 32 to the near-infinite value of 256. Rather than using FN<num>
notation (still available, but limited to FN0
-FN31
), you can use the FUNC(<num>)
notation. F(<num>)
is a shortcut for this.
The function actions are unchanged, and you can see the full list of them here. They are explained in detail here.
Macros have been setup in the keymaps/keymap_default.c
file so that you can use M(<num>)
to access a macro in the action_get_macro
section on your keymap. The switch/case structure you see here is required, and is setup for M(0)
- you'll need to copy and paste the code to look like this (e.g. to support M(3)
):
switch(id) {
case 0:
return MACRODOWN(TYPE(KC_A), END);
break;
case 1:
return MACRODOWN(TYPE(KC_B), END);
break;
case 2:
return MACRODOWN(TYPE(KC_C), END);
break;
case 3:
return MACRODOWN(TYPE(KC_D), END);
break;
}
return MACRO_NONE;
MACRODOWN()
is a shortcut for (record->event.pressed ? MACRO(__VA_ARGS__) : MACRO_NONE)
which tells the macro to execute when the key is pressed. Without this, the macro will be executed on both the down and up stroke.