You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
53 lines
2.4 KiB
53 lines
2.4 KiB
Planck keyboard firmware
|
|
======================
|
|
DIY/Assembled compact ortholinear 40% keyboard by [Ortholinear Keyboards](http://ortholinearkeyboards.com).
|
|
|
|
## Quantum MK Firmware
|
|
|
|
|
|
|
|
## Building
|
|
|
|
Download or clone the whole firmware and navigate to the keyboard/planck folder. Once your dev env is setup, you'll be able to type `make` to generate your .hex - you can then use `make dfu` to program your PCB once you hit the reset button.
|
|
|
|
Depending on which keymap you would like to use, you will have to compile slightly differently.
|
|
|
|
### Default
|
|
To build with the default keymap, simply run `make`.
|
|
|
|
## Safety Considerations
|
|
|
|
You probably don't want to "brick" your keyboard, making it impossible
|
|
to rewrite firmware onto it. Here are some of the parameters to show
|
|
what things are (and likely aren't) too risky.
|
|
|
|
- If a keyboard map does not include RESET, then, to get into DFU
|
|
mode, you will need to press the reset button on the PCB, which
|
|
requires unscrewing some bits.
|
|
- Messing with tmk_core / common files might make the keyboard
|
|
inoperable
|
|
- Too large a .hex file is trouble; `make dfu` will erase the block,
|
|
test the size (oops, wrong order!), which errors out, failing to
|
|
flash the keyboard
|
|
- DFU tools do /not/ allow you to write into the bootloader (unless
|
|
you throw in extra fruitsalad of options), so there is little risk
|
|
there.
|
|
- EEPROM has around a 100000 write cycle. You shouldn't rewrite the
|
|
firmware repeatedly and continually; that'll burn the EEPROM
|
|
eventually.
|
|
|
|
### Other Keymaps
|
|
Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create file named `<name>.c` and see keymap document (you can find in top README.md) and existent keymap files.
|
|
|
|
To build the firmware binary hex file with a keymap just do `make` with `KEYMAP` option like:
|
|
```
|
|
$ make KEYMAP=[default|jack|<name>]
|
|
```
|
|
Keymaps follow the format **__<name\>.c__** and are stored in the `keymaps` folder.
|
|
|
|
### Notable forks (which some of the keymap files are from)
|
|
- [Shane's Fork](https://github.com/shanecelis/tmk_keyboard/tree/master/keyboard/planck)
|
|
- [Pierre's Fork](https://github.com/pcarrier/tmk_keyboard/blob/pcarrier/planck/keyboard/gh60/keymap_planck.c)
|
|
- [Nathan's Fork](https://github.com/nathanrosspowell/tmk_keyboard/tree/planck-jack/keyboard/planck)
|
|
- [Matthew's Fork](https://github.com/pepers/tmk_keyboard/tree/master/keyboard/planck_grid)
|