Made Readme much more detailed
This commit is contained in:
parent
bf4c2b2dd6
commit
3a5c73a8ca
|
|
@ -1,25 +0,0 @@
|
||||||
#include QMK_KEYBOARD_H
|
|
||||||
#include "keymap_german.h"
|
|
||||||
|
|
||||||
const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
|
|
||||||
/*
|
|
||||||
* ┌───┬───┬───┬───┐
|
|
||||||
* │ 7 │ 8 │ 9 │ + │
|
|
||||||
* ├───┼───┼───┼───┤
|
|
||||||
* │ 4 │ 5 │ 6 │ - │
|
|
||||||
* ├───┼───┼───┼───┤
|
|
||||||
* │ 1 │ 2 │ 3 │ * │
|
|
||||||
* ├───┼───┼───┼───┤
|
|
||||||
* │ 0 │ . │Ent│ / │
|
|
||||||
* └───┴───┴───┴───┘
|
|
||||||
*/
|
|
||||||
[0] = LAYOUT_numpad_4x4(XXXXXXX, XXXXXXX, XXXXXXX, DE_U, RGB_TOG, RGB_M_R, RGB_M_B, RGB_M_SW, RGB_M_T, RGB_M_X, RGB_M_G, RGB_M_SN, KC_1, KC_2, KC_3, DE_ASTR, KC_0, KC_DOT, KC_ENT, DE_SLSH)};
|
|
||||||
|
|
||||||
bool encoder_update_user(uint8_t index, bool clockwise) {
|
|
||||||
if (clockwise) {
|
|
||||||
tap_code_delay(KC_VOLU, 10);
|
|
||||||
} else {
|
|
||||||
tap_code_delay(KC_VOLD, 10);
|
|
||||||
}
|
|
||||||
return false;
|
|
||||||
}
|
|
||||||
32
readme.md
32
readme.md
|
|
@ -1,8 +1,38 @@
|
||||||
# Hackpad
|
# Hackpad
|
||||||
|
## Overview
|
||||||
The `Hackpad` is a 4x4 numpad/macropad designed for the Arduino Day 2023 in cooperation with the hackspace [Imaginärraum e.V.](imaginaerraum.de) and [Fablab-Bayreuth e.V.](fablab-bayreuth.de).
|
The `Hackpad` is a 4x4 numpad/macropad designed for the Arduino Day 2023 in cooperation with the hackspace [Imaginärraum e.V.](imaginaerraum.de) and [Fablab-Bayreuth e.V.](fablab-bayreuth.de).
|
||||||
It supports 16 MX-style switches, an EC-11 rotary encoder, and per key RGB LEDs based on SK6812.
|
It supports 16 MX-style switches, an EC-11 rotary encoder, and per key RGB LEDs based on SK6812.
|
||||||
|
## Hardware Revisions
|
||||||
In v0.2 all necessary components are through hole components (except for an optional reset switch and RGB-LEDs), but the ProMicro protrudes out of the case.
|
In v0.2 all necessary components are through hole components (except for an optional reset switch and RGB-LEDs), but the ProMicro protrudes out of the case.
|
||||||
In v0.3 this is fixed by moving some diodes to the bottom side. The bottom diodes however are SMD only.
|
In v0.3 this is fixed by moving some diodes to the bottom side. The bottom diodes however are SMD only.
|
||||||
|
## Installing Firmware
|
||||||
|
We support two kinds of firmware: low level [Arduino firmware](firmware_arduino), and the higher level [QMK firmware](firmware_qmk).
|
||||||
|
### Arduino Firmware
|
||||||
|
This firmware is mostly for educational purposes.
|
||||||
|
Its low level code shows how keyboard firmware works on the electronical/physical level. There is a very [basic version](firmware_arduino/hackpad_simple/hackpad_simple.ino) that only includes the bare minimum to understand the keyboard matrix. The more [advanced version](firmware_arduino/hackpad/hackpad.ino) also includes functionality like debouncing.
|
||||||
|
### QMK Firmware
|
||||||
|
#### Installing and locating QMK on your Computer
|
||||||
|
With QMK it is simple to define custom layouts and up to 32 layers.
|
||||||
|
Follow the instructions to [install](https://docs.qmk.fm/#/newbs_getting_started) QMK on your computer.
|
||||||
|
After you've installed QMK there exists a directory `qmk_firmware` in your home directory.
|
||||||
|
Under Linux, the path is `~/qmk_firmware`, while under Windows should be `C:\\users\your_username\qmk_firmware`.
|
||||||
|
|
||||||
|
#### Adding support for the hackpad
|
||||||
|
The QMK version from the official website, does not yet include the software definitions for the `hackpad`-keyboard, so we need to add it manually.
|
||||||
|
For this you need to copy the directory `hackpad` found at [firmware_qmk/hackpad](firmware_qmk) into the `keyboards` directory in the `qmk_firmware` you have downloaded earlier.
|
||||||
|
You can get a copy of the `hackpad` directory by downloading this repository and extracting it.
|
||||||
|
Keep in mind that there are multiple directorys called `hackpad` in this repository, i.e. the repository itself, one in the subdirectory `firmware_arduino` and one in the subdirectory `firmware_qmk`.
|
||||||
|
You need to copy the `hackpad` directory of the subdirectory `firmware_qmk` into the `keyboards` directory of your `qmk_firmware` directory, to enable support for the hackpad keyboard in QMK.
|
||||||
|
Notice the difference between the directories `qmk_firmware` and `firmware_qmk`.
|
||||||
|
|
||||||
|
Once you have completed the previous steps, you should be able to compile your first firmware by typing `qmk compile -kb hackpad -km default` into the command line interface provided by QMK.
|
||||||
|
#### Editing the layout
|
||||||
|
You can find instructions on how to change you keymap in the [QMK documentation](https://docs.qmk.fm/#/newbs_building_firmware).
|
||||||
|
You can find an exhaustive list of keycodes in the [Keycodes overview of QMK](https://docs.qmk.fm/#/keycodes).
|
||||||
|
#### Flashing the firmware
|
||||||
|
After you have made your changes to the keymap you need to upload the firmware othe keyboard.
|
||||||
|
This is done by running `qmk flash -kb hackpad -km "your keymap name"`, where `"your keymap name"` is the name of the subdirectory in the `keymaps` directory which you want to upload to the keyboard.
|
||||||
|
|
||||||
|
# Support
|
||||||
|
If you have any questions regarding this keyboard feel free to contact me via [matrix](https://matrix.org/) in the [hackpad support room](#hackpad:ncxy.de), via [e-mail](mailto:n-hackpad@ncxy.de), or visit me at the hackspace [Imaginärraum e.V.](imaginaerraum.de)
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue
Block a user