1 # Documents You Need To Read
\r
4 1. First **README** under top directory : https://github.com/tmk/tmk_keyboard/blob/master/README.md
\r
5 2. For **Build**: https://github.com/tmk/tmk_keyboard/blob/master/doc/build.md
\r
6 3. And **README** under each project(keyboard/converter) directory. Note that you should read two **README**.
\r
15 https://github.com/tmk/tmk_keyboard/blob/master/doc/build.md
\r
23 ## Do 'make clean' before 'make'
\r
24 You'll need `make clean` after you edit **config.h** or change options like `KEYMAP`.
\r
26 Frist remove all files made in previous build,
\r
30 then build new frimware.
\r
34 Also you can always try `make clean` when you get other strange result during build.
\r
37 ## WINAVR is obsolete
\r
38 It is no longer recommended and may cause some problem.
\r
39 See [Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
\r
41 ## USB stack: LUFA or PJRC?
\r
44 **PJRC** stack won't be supported actively anymore. There is no reason to hesitate to use LUFA except for binary size(about 1KB lager?). But **PJRC** is still very useful for debug and development purpose.
\r
45 See also [Issue #50](https://github.com/tmk/tmk_keyboard/issues/50) and [Issue #58](https://github.com/tmk/tmk_keyboard/issues/58).
\r
48 ## Edit configuration but not change
\r
51 This will be needed when you edit **config.h**.
\r
53 ### 2. Remove Drivers from Device Manager(Windows)
\r
54 Windows only. Linux, OSX and other OS's doesn't require this. It looks like Windows keeps using driver installed when device was connected first time even after the device changes its configuration. To load proper drivers for new configuration you need to remove existent drivers from **Drvice Manager**.
\r
56 You will need this after editing `CONSOLE_ENABLE`, `NKRO_ENABLE`, `EXTRAKEY_ENABLE` or `MOUSEKEY_ENABLE` option in **Makefile**.
\r
60 You can use any ID you want with editing `config.h`. Using any presumably unused ID will be no problem in fact except for very least chance of collision with other product.
\r
62 For example TMK uses following numbers by default.
\r
77 https://github.com/tmk/tmk_keyboard/issues/150
\r
79 You can buy a really unique VID:PID here. I don't think you need this for personal use.
\r
80 - http://www.obdev.at/products/vusb/license.html
\r
81 - http://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=92&option=com_phpshop&Itemid=1
\r
85 ## hid_listen can't recognize device
\r
86 When debug console of your device is not ready you will see like this:
\r
88 Waiting for device:.........
\r
90 once the device is pluged in then *hid_listen* finds it you will get this message:
\r
92 Waiting for new device:.........................
\r
95 Check if you can't get this 'Listening:' message:
\r
96 - build with `CONSOLE_ENABLE=yes` in **Makefile**.
\r
98 ## Can't get message on console
\r
100 - *hid_listen* finds your device. See above.
\r
101 - Enable debug with pressing **Magic**+d. See [Magic Commands](https://github.com/tmk/tmk_keyboard#magic-commands).
\r
102 - set `debug_enable=yes` usually in `matrix_init()` in **matrix.c**.
\r
103 - try using 'print' function instead of debug print. See **common/print.h**.
\r
104 - disconnect other devices with console function. See [Issue #97](https://github.com/tmk/tmk_keyboard/issues/97).
\r
106 ## Linux or UNIX like system requires Super User privilege
\r
107 Just use 'sudo' to execute *hid_listen* with privilege.
\r
112 Or add an *udev rule* for TMK devices with placing a file in rules directory. The directory may vary on each system.
\r
114 File: /etc/udev/rules.d/52-tmk-keyboard.rules(in case of Ubuntu)
\r
116 # tmk keyboard products https://github.com/tmk/tmk_keyboard
\r
117 SUBSYSTEMS=="usb", ATTRS{idVendor}=="feed", MODE:="0666"
\r
123 ## NKRO Doesn't work
\r
124 1. Build with this option of Makefile
\r
128 2. After boot keyboard may be in **boot mode**(6KRO), you will need to replug keyboard to enable NKRO.
\r
130 3. Or use `Magic` **N** command to toggle NKRO function.(`LShift+RShift+N` by default)
\r
134 ## TrackPoint needs reset circuit(PS/2 mouse support)
\r
135 Without reset circuit you will have inconsistent reuslt due to improper initialize of the hardware. See circuit schematic of TPM754.
\r
137 - http://geekhack.org/index.php?topic=50176.msg1127447#msg1127447
\r
138 - http://www.mikrocontroller.net/attachment/52583/tpm754.pdf
\r
141 ## Can't read comlumn of matrix beyond 16
\r
142 Use `1UL<<16` intead of `1<<16` in `read_cols()` in **matrix.h** when your columns goes beyond 16.
\r
144 In C `1` means one of **int** type which is **16bit** in case of AVR so you can't shift left more than 15. You will get unexpected zero when you say `1<<16`. You have to use **unsigned long** type with `1UL`.
\r
146 http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279
\r
150 ## Pull-up Resistor
\r
151 In some case converters needed to have pull-up resistors to work correctly. Place the resistor between VCC and signal line in parallel.
\r
157 5V------+------|VCC |
\r
161 Signal--+------|PD0 |
\r
163 GND------------|GND |
\r
168 https://github.com/tmk/tmk_keyboard/issues/71
\r
171 ## Arduino Micro's pin naming is confusing
\r
172 Note that Arduino Micro PCB marking is different from real AVR port name. D0 of Arduino Micro is not PD0, PD0 is D3. Check schematic yourself.
\r
173 http://arduino.cc/en/uploads/Main/arduino-micro-schematic.pdf
\r
177 ## Bootloader jump doesn't work
\r
178 Properly configure boot section size in Makefile. With wrong section size bootloader won't probably start with **Magic command** and **Boot Magic**.
\r
179 - https://github.com/tmk/tmk_keyboard#magic-commands
\r
180 - https://github.com/tmk/tmk_keyboard#bootloader
\r
183 # Boot Section Size in *bytes*
\r
184 # Teensy halfKay 512
\r
185 # Teensy++ halfKay 1024
\r
186 # Atmel DFU loader 4096 (TMK Alt Controller)
\r
187 # LUFA bootloader 4096
\r
188 # USBaspLoader 2048
\r
189 OPT_DEFS += -DBOOTLOADER_SIZE=4096
\r
191 http://geekhack.org/index.php?topic=12047.msg1292018#msg1292018
\r
194 ## Special Extra key doesn't work(System, Audio control keys)
\r
195 You need to define `EXTRAKEY_ENABLE` in **makefile** to use them in TMK.
\r
197 EXTRAKEY_ENABLE = yes # Audio control and System control
\r
199 http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-60.html#p157919
\r
202 ## Wakeup from sleep doesn't work
\r
203 In Windows check `Allow this device to wake the computer` setting in Power **Management property** tab of **Device Manager**. Also check BIOS setting.
\r
205 Pressing any key during sleep should wake host.
\r
209 **Note that Arduino pin naming is different from actual chip.** For example, Arduino pin `D0` is not `PD0`. Check circuit with its schematics yourself.
\r
211 - http://arduino.cc/en/uploads/Main/arduino-leonardo-schematic_3b.pdf
\r
212 - http://arduino.cc/en/uploads/Main/arduino-micro-schematic.pdf
\r
214 Arduino leonardo and micro have **ATMega32U4** and can be used for TMK, though Arduino bootloader may be a problem.
\r
217 ## Using PF4-7 pins of USB AVR?
\r
218 You need to set JTD bit of MCUCR yourself to use PF4-7 as GPIO. Those pins are configured to serve JTAG function by default. MCUs like ATMega*U* or AT90USB* are affeteced with this.
\r
220 If you are using Teensy this isn't needed. Teensy is shipped with JTAGEN fuse bit unprogrammed to disable the function.
\r
224 // JTAG disable for PORT F. write JTD bit twice within four cycles.
\r
228 https://github.com/tmk/tmk_keyboard/blob/master/keyboard/hbkb/matrix.c#L67
\r
230 And read **26.5.1 MCU Control Register – MCUCR** of ATMega32U4 datasheet.
\r
233 ## Adding LED indicators of Lock keys
\r
234 You need your own LED indicators for CapsLock, ScrollLock and NumLock? See this post.
\r
236 http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p191560