|
|
10 years ago | |
|---|---|---|
| converter | 10 years ago | |
| keyboard | 10 years ago | |
| quantum | 10 years ago | |
| teensy-sdk | 10 years ago | |
| tmk_core | 10 years ago | |
| .gitignore | 11 years ago | |
| .gitmodules | 10 years ago | |
| README.md | 10 years ago | |
| new_project.sh | 10 years ago |
This is a keyboard firmware based on the tmk_keyboard firmware with some useful features for Atmel AVR controller, and more specifically, the OLKB product line.
You can create your own Quantum-based project by using ./new_project.sh <project_name>, which will create /keyboard/<project_name> with all the necessary components for a Quantum project.
You have access to a bunch of goodies! Check out the Makefile to enable/disable some of the features. Uncomment the # to enable them. Setting them to no does nothing and will only confuse future you.
BACKLIGHT_ENABLE = yes # Enable keyboard backlight functionality
MIDI_ENABLE = yes # MIDI controls
# UNICODE_ENABLE = yes # Unicode support
BLUETOOTH_ENABLE = yes # Enable Bluetooth with the Adafruit EZ-Key HID
LSFT(kc) - applies left shift to kc - S(kc) is an aliasRSFT(kc) - applies right shift to kcLCTL(kc) - applies left control to kcRCTL(kc) - applies right control to kcLALT(kc) - applies left alt to kcRALT(kc) - applies right alt to kcLGUI(kc) - applies left gui (command/win) to kcRGUI(kc) - applies right gui (command/win) to kcYou can also use more than one, like this:
LALT(LGUI(KC_ESC))
The following shortcuts automatically add LSFT() to keycodes to get commonly used symbols. Their long names (see quantum/keymap_common.h) are also availble.
KC_TILD ~
KC_EXLM !
KC_AT @
KC_HASH #
KC_DLR $
KC_PERC %
KC_CIRC ^
KC_AMPR &
KC_ASTR *
KC_LPRN (
KC_RPRN )
KC_UNDS _
KC_PLUS +
KC_LCBR {
KC_RCBR }
KC_PIPE |
KC_COLN :
Instead of using FNx, you can use F(x) - the benefit here is being able to use more than 32 function layers (up to 4096), if you happen to need them.
There are also keycode shortcuts for common actions:
MO(layer) - momentary switch to layerDF(layer) - sets default layer to layerTG(layer) - toggle between the current layer and layerMT(mod, kc) - is mod when held, and kc when tapped
CTL_T(kc) - is LCTL when held and kc when tappedSFT_T(kc) - is LSFT when held and kc when tappedALT_T(kc) - is LALT when held and kc when tappedGUI_T(kc) - is LGUI when held and kc when tappedALL_T(kc) - is Hyper (all mods) when held and kc when tappedLT(layer, kc) - momentary switch to layer when held, and kc when tappedThese functions work the same way that their ACTION_* functions do, and will require KC_TRNS on the layer being switched to - check out the default keymap for an example.
Everything is assuming you're in Qwerty (in software) by default, but there is built-in support for using a Colemak or Dvorak layout by including this at the top of your keymap:
#include "keymap_<layout>.h"
Where is "colemak" or "dvorak". After including this line, you will get access to:
CM_* for all of the Colemak-equivalent charactersDV_* for all of the Dvorak-equivalent charactersThese implementations assume you're using Colemak or Dvorak on your OS, not on your keyboard - this is referred to as a software-implemented layout. If your computer is in Qwerty and your keymap is in Colemak or Dvorak, this is referred to as a firmware-implemented layout, and you won't need these features.
To give an example, if you're using software-implemented Colemak, and want to get an F, you would use CM_F - KC_F under these same circumstances would result in T.
In quantum/keymap_extras/, you'll see various language files - these work the same way as the alternative layout ones do. Most are defined by their two letter country/language code followed by an underscore and a 4-letter abbrivation of its name. FR_UGRV which will result in a ù when using a software-implemented AZERTY layout. It's currently difficult to send such characters in just the firmware (but it's being worked on - see Unicode support).
You can currently send 4 hex digits with your OS-specific modifier key (RALT for OSX with the "Unicode Hex Input" layout) - this is currently limited to supporting one OS at a time, and requires a recompile for switching. 8 digit hex codes are being worked on. The keycode function is UC(n), where n is a 4 digit hexidecimal. Enable from the Makefile.
Instead of using the ACTION_MACRO function, you can simply use M(n) to access macro n - n will get passed into the action_get_macro as the id, and you can use a switch statement to filter them. This gets called on the keydown and keyup, so you'll need to use an if statement testing record->event.pressed (see keymap_default.c).
RESET - puts the MCU in DFU mode for flashing new firmware (with make dfu)DEBUG - the firmware into debug mode - you'll need hid_listen to see thingsBL_ON - turns the backlight onBL_OFF - turns the backlight offBL_<n> - sets the backlight to level nBL_INC - increments the backlight level by oneBL_DEC - decrements the backlight level by oneBL_TOGG - toggles the backlightBL_STEP - steps through the backlight levelsEnable the backlight from the Makefile.
This is still a WIP, but check out quantum/keymap_midi.c to see what's happening. Enable from the Makefile.
This requires some hardware changes, but can be enabled via the Makefile. The firmware will still output characters via USB, so be aware of this when charging via a computer. It would make sense to have a switch on the Bluefruit to turn it off at will.
These features can be used in your keyboard.
You can find some keyboard specific projects under converter and keyboard directory.
GPLv2 or later. Some protocol files are under Modified BSD License.
Third party libraries like LUFA, PJRC and V-USB have their own license respectively.
See doc/build.md, or the README in the particular keyboard/* folder.
See doc/keymap.md.
To see help press Magic + H.
Magic key combination is LShift + RShift in many project, but Power key on ADB converter.
Magic keybind can be vary on each project, check config.h in project directory.
Following commands can be also executed with Magic + key. In console mode Magic keybind is not needed.
----- Command Help -----
c: enter console mode
d: toggle debug enable
x: toggle matrix debug
k: toggle keyboard debug
m: toggle mouse debug
v: print device version & info
t: print timer count
s: print status
e: print eeprom config
n: toggle NKRO
0/F10: switch to Layer0
1/F1: switch to Layer1
2/F2: switch to Layer2
3/F3: switch to Layer3
4/F4: switch to Layer4
PScr: power down/remote wake-up
Caps: Lock Keyboard(Child Proof)
Paus: jump to bootloader
Boot Magic are executed during boot up time. Press Magic key below then plug in keyboard cable. Note that you must use keys of Layer 0 as Magic keys. These settings are stored in EEPROM so that retain your configure over power cycles.
To avoid configuring accidentally additive salt key KC_SPACE also needs to be pressed along with the following configuration keys. The salt key is configurable in config.h. See tmk_core/common/bootmagic.h.
ESC)Backspace)B)D)D+X)D+K)D+M)Left Control)Caps Lock)Left Alt)Right Alt)Left Gui)Grave)Back Slash)N)0)1)2)3)4)5)6)7)This feature makes it possible for you to use mechanical locking switch for CapsLock, NumLock
or ScrollLock. To enable this feature define these macros in config.h and use KC_LCAP, KC_LN
UM or KC_LSCR in keymap for locking key instead of normal KC_CAPS, KC_NLCK or KC_SLCK. Res
ync option tries to keep switch state consistent with keyboard LED state.
#define LOCKING_SUPPORT_ENABLE
#define LOCKING_RESYNC_ENABLE
TBD
Use PJRC's hid_listen to see debug messages. You can use the tool for debug even if firmware use LUFA stack.
You can use xprintf() to display debug info on hid_listen, see tmk_core/common/xprintf.h.
You can learn a lot about keyboard firmware from these. See doc/other_projects.md.