1
0
This repo is archived. You can view files and clone it, but cannot push or open issues or pull requests.
tmk_keyboard_custom/protocol/chibios
tmk 71381457fa Squashed 'tmk_core/' changes from ee8c5ba..d5c5ac6
d5c5ac6 Merge branch 'develop'
5957682 Merge branch 'hotfix-mediakey'
a478c62 Merge branch 'hotfix-vusb'
cccebfe Merge branch 'njbair-docfix'
0aaab57 Clean up wording in keymap example
dc8bbc3 Clarify layer precedence
9e0b4c1 clarify layer documentation
915eb48 core: Fix media/consumer keys
88f90f3 Fix for VUSB configuration
3e290cd Fix including board.mk in chibios.mk
32c69e0 Merge branch 'newapi' into develop
c9a56f9 Merge remote-tracking branch 'flabbergast/chibios' into develop
01e33ea Fix chibios and mbed common.mk for hook.c
bea79d9 hook: Change func name of usb events
3e97536 hook: Change file and func names(*_hook -> hook_*)
c286d8c Merge pull request #10 from fredizzimo/chibios-contrib2
062d74e Update ChibiOS instructions
d47150f Add support for new version of ChibiOS and Contrib
62b5401 Chibios: disable LTO (link-time optimisation).
c64e9aa hooks: Fix for LUFA
54e68b0 hooks: Remove led_restore_hook
325c09d Chibios: make the default bootloader_jump redefinable (weak).
078c722 Chibios: fix STM32_BOOTLOADER_ADDRESS name.
e73cfe5 hooks: Fix for keyboard LED update
e6120c5 Implement basic hooks.
7c370e9 Chibios: Update the main chibios README.
7f0198d Chibios: implement sleep LED for STM32.
afef9b4 Fix hard-coded path of CHIBIOS
95c5b19 Merge pull request #7 from fredizzimo/sysvsize
27128a8 Sysv format for ChibiOS arm-none-eabi-size
d4b8e68 core: Fix chibios user compile options
b85d462 Merge branch 'chibios' of https://github.com/flabbergast/tmk_keyboard into flabbergast_chibios
de41aa1 core: Fix ps2_mouse.c debug print
d79d925 Removed duplicate debug message code and surrounded it with IFDEF as needed
8f28589 Chibios: Revert common.mk change (fix AVR linking problem).
ec9eff2 Chibios: cleanup usb_main code.
28c4665 Chibios: Fix a HardFault bug (wait after start).

git-subtree-dir: tmk_core
git-subtree-split: d5c5ac63e60dfc6da6661a21bd968b4d577a27d5
2016-04-21 14:35:48 +09:00
..
main.c Squashed 'tmk_core/' changes from ee8c5ba..d5c5ac6 2016-04-21 14:35:48 +09:00
README.md Squashed 'tmk_core/' changes from ee8c5ba..d5c5ac6 2016-04-21 14:35:48 +09:00
usb_main.c Squashed 'tmk_core/' changes from ee8c5ba..d5c5ac6 2016-04-21 14:35:48 +09:00
usb_main.h Squashed 'tmk_core/' changes from ee8c5ba..d5c5ac6 2016-04-21 14:35:48 +09:00

TMK running on top of ChibiOS

This code can be used to run TMK keyboard logic on top of ChibiOS, meaning that you can run TMK on whatever ChibiOS supports. The notable examples are ARM-based Teensies (3.x and LC) and on the boards with STM32 MCUs.

Usage

  • To use, unpack or symlink ChibiOS to tmk_core/tool/chibios/chibios. For Kinetis support (this means Teensies, Infinity keyboard, WhiteFox keyboard), you'll need a fork which implements the USB driver, e.g. this one.
  • You will also need to install an ARM toolchain, for instance from here. On linux, this is usually also present as a package for your distribution (as gcc-arm or something similar). On OS X, you can use homebrew with an appropriate tap.

Notes

  • Some comments about ChibiOS syntax and the most commonly used GPIO functions are, as well as an example for ARM Teensies, is here.
  • For gcc options, inspect tmk_core/tool/chibios/chibios.mk. For instance, I enabled -Wno-missing-field-initializers, because TMK common bits generated a lot of warnings on that. Also pay attention to -O0 (enabled for debugging); for deployment use -O2.
  • USB string descriptors are messy. I did not find a way to cleanly generate the right structures from actual strings, so the definitions in individual keyboards' config.h are ugly as heck.
  • It is easy to add some code for testing (e.g. blink LED, do stuff on button press, etc...) - just create another thread in main.c, it will run independently of the keyboard business.
  • Jumping to (the built-in) bootloaders on STM32 works, but it is not entirely pleasant, since it is very much MCU dependent. So, one needs to dig out the right address to jump to, and either pass it to the compiler in the Makefile, or better, define it in <your_kb>/bootloader_defs.h. An additional startup code is also needed; the best way to deal with this is to define custom board files. (Example forthcoming.)

Experimental pre-ChibiOS 4 support

  • As an alternative to the mentioned flabbergast branch above, you can use the master branch of ChibiOS.
  • Note that the Kinetis support has moved to the ChibiOS-Contrib repository, so you need to put that into your repository in the same way as you did for the main ChibiOS repository.
  • You also need to define CHIBIOS_CONTRIB in your makefile and point it to the right directory.
  • You need to add some new options to chconf.h, or you will get compiler errors. Just copy the new options from samples provided by the ChibiOS-Contrib repository.

Immediate todo

  • power saving for suspend

Not tested, but possibly working

  • backlight

Missing / not working (TMK vs ChibiOS bits)

  • eeprom / bootmagic for STM32 (will be chip dependent; eeprom needs to be emulated in flash, which means less writes; wear-levelling?) There is a semi-official ST "driver" for eeprom, with wear-levelling, but I think it consumes a lot of RAM (like 2 pages, i.e. 1kB or so).

Tried with

  • Infinity, WhiteFox keyboards
  • all ARM-based Teensies
  • some STM32-based boards (e.g. ST-F072RB-DISCOVERY board, STM32F042 breakout board, Maple Mini (STM32F103-based))

ChibiOS-supported MCUs

  • Pretty much all STM32 chips.
  • There is some support for K20x and KL2x Freescale chips (i.e. Teensy 3.x/LC, mchck, FRDM-KL2{5,6}Z, FRDM-K20D50M), but again, no official USB stack yet. However the kinetis branch of flabbergast's ChibiOS fork. With this fork, TMK work normally on all the ARM Teensies.
  • There is also support for AVR8, but the USB stack is not implemented for them yet, and also the kernel itself takes about 1k of RAM. I think people managed to get ChibiOS running on atmega32[8p/u4] though.
  • I've seen community support for Nordic NRF51822 (the chip in Adafruit's Bluefruit bluetooth-low-energy boards), but not sure about the extent.

STM32-based keyboard design considerations

  • STM32F0x2 chips can do crystal-less USB, but they still need a 3.3V voltage regulator.
  • The BOOT0 pin should be tied to GND.
  • For a hardware way of accessing the in-built DFU bootloader, in addition to the reset button, put another button between the BOOT0 pin and 3V3.