You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

247 lines
8.6 KiB

  1. # Documents You Need To Read
  2. Read these yet?
  3. 1. First **README** under top directory : https://github.com/tmk/tmk_keyboard/blob/master/README.md
  4. 2. For **Build**: https://github.com/tmk/tmk_keyboard/blob/master/doc/build.md
  5. 3. And **README** under each project(keyboard/converter) directory. Note that you should read two **README**.
  6. 4. And then, FAQ.
  7. - [[FAQ/Keymap]]
  8. # Build
  9. ## How to Build
  10. See this first!
  11. https://github.com/tmk/tmk_keyboard/blob/master/doc/build.md
  12. In short,
  13. $ make clean
  14. $ make [KEYMAP=...]
  15. ## Do 'make clean' before 'make'
  16. You'll need `make clean` after you edit **config.h** or change options like `KEYMAP`.
  17. Frist remove all files made in previous build,
  18. $ make clean
  19. then build new frimware.
  20. $ make [KEYMAP=...]
  21. Also you can always try `make clean` when you get other strange result during build.
  22. ## WINAVR is obsolete
  23. It is no longer recommended and may cause some problem.
  24. See [Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
  25. ## USB stack: LUFA or PJRC?
  26. Use **LUFA**.
  27. **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.
  28. See also [Issue #50](https://github.com/tmk/tmk_keyboard/issues/50) and [Issue #58](https://github.com/tmk/tmk_keyboard/issues/58).
  29. ## Edit configuration but not change
  30. Try these.
  31. ### 1. make clean
  32. This will be needed when you edit **config.h**.
  33. ### 2. Remove Drivers from Device Manager(Windows)
  34. 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**.
  35. You will need this after editing `CONSOLE_ENABLE`, `NKRO_ENABLE`, `EXTRAKEY_ENABLE` or `MOUSEKEY_ENABLE` option in **Makefile**.
  36. ## USB VID and PID
  37. 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.
  38. For example TMK uses following numbers by default.
  39. ```
  40. keyboard:
  41. hhkb: FEED:CAFE
  42. gh60: FEED:6060
  43. converter:
  44. x68k: FEED:6800
  45. ps2: FEED:6512
  46. adb: FEED:0ADB
  47. ibm4704: FEED:4704
  48. pc98: FEED:9898
  49. ```
  50. Also see this.
  51. https://github.com/tmk/tmk_keyboard/issues/150
  52. You can buy a really unique VID:PID here. I don't think you need this for personal use.
  53. - http://www.obdev.at/products/vusb/license.html
  54. - http://www.mcselec.com/index.php?page=shop.product_details&flypage=shop.flypage&product_id=92&option=com_phpshop&Itemid=1
  55. # Degug Console
  56. ## hid_listen can't recognize device
  57. When debug console of your device is not ready you will see like this:
  58. Waiting for device:.........
  59. once the device is pluged in then *hid_listen* finds it you will get this message:
  60. Waiting for new device:.........................
  61. Listening:
  62. Check if you can't get this 'Listening:' message:
  63. - build with `CONSOLE_ENABLE=yes` in **Makefile**.
  64. ## Can't get message on console
  65. Check:
  66. - *hid_listen* finds your device. See above.
  67. - Enable debug with pressing **Magic**+d. See [Magic Commands](https://github.com/tmk/tmk_keyboard#magic-commands).
  68. - set `debug_enable=yes` usually in `matrix_init()` in **matrix.c**.
  69. - try using 'print' function instead of debug print. See **common/print.h**.
  70. - disconnect other devices with console function. See [Issue #97](https://github.com/tmk/tmk_keyboard/issues/97).
  71. ## Linux or UNIX like system requires Super User privilege
  72. Just use 'sudo' to execute *hid_listen* with privilege.
  73. ```
  74. $ sudo hid_listen
  75. ```
  76. Or add an *udev rule* for TMK devices with placing a file in rules directory. The directory may vary on each system.
  77. File: /etc/udev/rules.d/52-tmk-keyboard.rules(in case of Ubuntu)
  78. ```
  79. # tmk keyboard products https://github.com/tmk/tmk_keyboard
  80. SUBSYSTEMS=="usb", ATTRS{idVendor}=="feed", MODE:="0666"
  81. ```
  82. ***
  83. # Miscellaneous
  84. ## NKRO Doesn't work
  85. 1. Build with this option of Makefile
  86. NKRO_ENABLE = yes
  87. 2. After boot keyboard may be in **boot mode**(6KRO), you will need to replug keyboard to enable NKRO.
  88. 3. Or use `Magic` **N** command to toggle NKRO function.(`LShift+RShift+N` by default)
  89. ## TrackPoint needs reset circuit(PS/2 mouse support)
  90. Without reset circuit you will have inconsistent reuslt due to improper initialize of the hardware. See circuit schematic of TPM754.
  91. - http://geekhack.org/index.php?topic=50176.msg1127447#msg1127447
  92. - http://www.mikrocontroller.net/attachment/52583/tpm754.pdf
  93. ## Can't read comlumn of matrix beyond 16
  94. Use `1UL<<16` intead of `1<<16` in `read_cols()` in **matrix.h** when your columns goes beyond 16.
  95. 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`.
  96. http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279
  97. ## Pull-up Resistor
  98. In some case converters needed to have pull-up resistors to work correctly. Place the resistor between VCC and signal line in parallel.
  99. For example:
  100. ```
  101. Keyboard Conveter
  102. ,------.
  103. 5V------+------|VCC |
  104. | | |
  105. R | |
  106. | | |
  107. Signal--+------|PD0 |
  108. | |
  109. GND------------|GND |
  110. `------'
  111. R: 1K Ohm resistor
  112. ```
  113. https://github.com/tmk/tmk_keyboard/issues/71
  114. ## Arduino Micro's pin naming is confusing
  115. 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.
  116. http://arduino.cc/en/uploads/Main/arduino-micro-schematic.pdf
  117. ## Bootloader jump doesn't work
  118. Properly configure boot section size in Makefile. With wrong section size bootloader won't probably start with **Magic command** and **Boot Magic**.
  119. - https://github.com/tmk/tmk_keyboard#magic-commands
  120. - https://github.com/tmk/tmk_keyboard#bootloader
  121. ```
  122. # Boot Section Size in *bytes*
  123. # Teensy halfKay 512
  124. # Teensy++ halfKay 1024
  125. # Atmel DFU loader 4096 (TMK Alt Controller)
  126. # LUFA bootloader 4096
  127. # USBaspLoader 2048
  128. OPT_DEFS += -DBOOTLOADER_SIZE=4096
  129. ```
  130. http://geekhack.org/index.php?topic=12047.msg1292018#msg1292018
  131. ## Special Extra key doesn't work(System, Audio control keys)
  132. You need to define `EXTRAKEY_ENABLE` in **makefile** to use them in TMK.
  133. ```
  134. EXTRAKEY_ENABLE = yes # Audio control and System control
  135. ```
  136. http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-60.html#p157919
  137. ## Wakeup from sleep doesn't work
  138. In Windows check `Allow this device to wake the computer` setting in Power **Management property** tab of **Device Manager**. Also check BIOS setting.
  139. Pressing any key during sleep should wake host.
  140. ## Using Arduino?
  141. **Note that Arduino pin naming is different from actual chip.** For example, Arduino pin `D0` is not `PD0`. Check circuit with its schematics yourself.
  142. - http://arduino.cc/en/uploads/Main/arduino-leonardo-schematic_3b.pdf
  143. - http://arduino.cc/en/uploads/Main/arduino-micro-schematic.pdf
  144. Arduino leonardo and micro have **ATMega32U4** and can be used for TMK, though Arduino bootloader may be a problem.
  145. ## Using PF4-7 pins of USB AVR?
  146. 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.
  147. If you are using Teensy this isn't needed. Teensy is shipped with JTAGEN fuse bit unprogrammed to disable the function.
  148. See this code.
  149. ```
  150. // JTAG disable for PORT F. write JTD bit twice within four cycles.
  151. MCUCR |= (1<<JTD);
  152. MCUCR |= (1<<JTD);
  153. ```
  154. https://github.com/tmk/tmk_keyboard/blob/master/keyboard/hbkb/matrix.c#L67
  155. And read **26.5.1 MCU Control Register – MCUCR** of ATMega32U4 datasheet.
  156. ## Adding LED indicators of Lock keys
  157. You need your own LED indicators for CapsLock, ScrollLock and NumLock? See this post.
  158. http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p191560
  159. ## Program Arduino Micro/Leonardo
  160. Push reset button and then run command like this within 8 seconds.
  161. ```
  162. avrdude -patmega32u4 -cavr109 -b57600 -Uflash:w:adb_usb.hex -P/dev/ttyACM0
  163. ```
  164. Device name will vary depending on your system.
  165. http://arduino.cc/en/Main/ArduinoBoardMicro
  166. https://geekhack.org/index.php?topic=14290.msg1563867#msg1563867