keyboard/teensy_lc_onekey/instructions.md

   1 # Teensy LC, 3.0, 3.1, 3.2 support
   2
   3 These ARM Teensies are now supported through [ChibiOS](http://chibios.org).
   4
   5 You'll need to install an ARM toolchain, for instance from [gcc ARM embedded](https://launchpad.net/gcc-arm-embedded) website, or using your favourite package manager. After installing, you should be able to run `arm-none-eabi-gcc -v` in the command prompt and get sensible output. This toolchain is used instead of `avr-gcc`, which is only for AVR chips. Naturally you'll also need the usual development tools (e.g. `make`), just as in the AVR setting.
   6
   7 Next, you'll need ChibiOS. For Teensies, you'll need code from two repositories: [chibios-main](https://github.com/ChibiOS/ChibiOS) and [chibios-contrib](https://github.com/ChibiOS/ChibiOS). If you're not using git, you can just download a [zip of chibios from here](https://github.com/ChibiOS/ChibiOS/archive/a7df9a891067621e8e1a5c2a2c0ceada82403afe.zip), unpack the zip, and rename/move the unpacked directory (named `ChibiOS-<long_hash_here>`) to `tmk_core/tool/chibios/chibios` (so that the file `tmk_core/tool/chibios/chibios/license.txt` exists). Now the same procedure with a [zip of chibios-contrib from here](https://github.com/ChibiOS/ChibiOS-Contrib/archive/e1311c4db6cd366cf760673f769e925741ac0ad3.zip): unpack and move `ChibiOS-Contrib-<long_hash_here>` to `tmk_core/tool/chibios/chibios-contrib`.
   8
   9 (If you're using git, you can just clone the two repos: [chibios](https://github.com/ChibiOS/ChibiOS) and [chibios-contrib](https://github.com/ChibiOS/ChibiOS-Contrib). However - be warned that things may be somewhat out-of-sync (updates at different rates), so you may need to hunt a bit for the right commits.)
  10
  11 (Why do we need chibios-contrib? Well, the main repo focuses on STM32 chips, and Freescale/NXP Kinetis chips are supported via the Contrib repository.)
  12
  13 This should be it. Running `make` in `keyboard/teensy_lc_onekey` should create a working firmware in `build/`, called `ch.hex`.
  14
  15 For more notes about the ChibiOS backend in TMK, see `tmk_core/protocol/chibios/README.md`.
  16
  17 ## About this onekey example
  18
  19 It's set up for Teensy LC. To use 3.x, you'll need to edit the `Makefile` (and comment out one line in `mcuconf.h`). A sample makefile for Teensy 3.0 is provided as `Makefile.3.0`, can be used without renaming with `make -f Makefile.3.0`. Similarly for Teensy 3.2, there's `Makefile.3.2`.
  20
  21 ## Credits
  22
  23 TMK itself is written by hasu, original sources [here](https://github.com/tmk/tmk_keyboard).
  24
  25 The USB support for Kinetis MCUs is due to RedoX. His ChibiOS fork is also [on github](https://github.com/RedoXyde/ChibiOS); but it doesn't include Teensy LC definitions.
  26
  27 ## Features that are not implemented yet
  28
  29 Currently only the more fancy suspend features are not there (power saving during suspend). The rest should work fine (reports either way are welcome).
  30
  31 # Matrix programming notes
  32
  33 The notes below explain what commands can be used to examine and set the status of Teensy pins.
  34
  35 ## ChibiOS pin manipulation basics
  36
  37 ### Pins
  38
  39 Each pin sits on a "port", each of which comprises at most 32 individual pins.
  40 So for instance "PTC5" from Kinetis manual/datasheet refers to port C (or GPIOA), pin 5. Most functions dealing with pins take 2 parameters which specify the pin -- the first being the port, the second being the pin number.
  41
  42 Within ChibiOS, there are definitions which simplify this a bit for the Teensies. `TEENSY_PINn_IOPORT` represents the port of the MCU's pin connected Teensy's PIN `n`, and `TEENSY_PINn` represents its MCU's pin number.
  43
  44 ### Mode
  45
  46 A MCU pin can be in several modes. The basic command to set a pin mode is
  47
  48         palSetPadMode(TEENSY_PINn_IOPORT, TEENSY_PINn, PAL_MODE_INPUT_PULLUP);
  49
  50 The last parameter is the mode. For keyboards, the usual ones that are used are `PAL_MODE_INPUT_PULLUP` (input with a pullup), `PAL_MODE_INPUT_PULLDOWN` (input with a pulldown), `PAL_MODE_INPUT` (input floating, a.k.a. Hi-Z), `PAL_MODE_OUTPUT_PUSHPULL` (output in the Arduino sense -- can be then set HIGH or LOW).
  51
  52 ### Setting
  53
  54 Pins are set HIGH (after they've been put into `OUTPUT_PUSHPULL` mode) by
  55
  56         palSetPad(TEENSY_PINn_IOPORT, TEENSY_PINn);
  57
  58 or set LOW by
  59
  60         palClearPad(TEENSY_PINn_IOPORT, TEENSY_PINn);
  61
  62 Toggling can be done with
  63
  64         palTogglePad(TEENSY_PINn_IOPORT, TEENSY_PINn);
  65
  66 Alternatively, you can use
  67
  68         palWritePad(TEENSY_PINn_IOPORT, TEENSY_PINn, bit);
  69
  70 where `bit` is either `PAL_LOW` or `PAL_HIGH` (i.e. `0` or `1`).
  71
  72 ### Reading
  73
  74 Reading pin status is done with
  75
  76         palReadPad(TEENSY_PINn_IOPORT, TEENSY_PINn);
  77
  78 The function returns either `PAL_HIGH` (actually `1`) or `PAL_LOW` (actually `0`).
  79
  80 ### Further docs
  81
  82 All the commands that are available for pin manipulation through ChibiOS HAL are documented in [ChibiOS PAL driver docs](http://chibios.sourceforge.net/docs3/hal/group___p_a_l.html).