aboutsummaryrefslogtreecommitdiff
path: root/docs/faq_debug.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/faq_debug.md')
-rw-r--r--docs/faq_debug.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/faq_debug.md b/docs/faq_debug.md
index 9dfec773f..25226102d 100644
--- a/docs/faq_debug.md
+++ b/docs/faq_debug.md
@@ -11,7 +11,7 @@ When debug console of your device is not ready you will see like this:
11Waiting for device:......... 11Waiting for device:.........
12``` 12```
13 13
14once the device is pluged in then *hid_listen* finds it you will get this message: 14once the device is plugged in then *hid_listen* finds it you will get this message:
15 15
16``` 16```
17Waiting for new device:......................... 17Waiting for new device:.........................
@@ -82,23 +82,23 @@ Size after:
82 consume extra memory; watch out for BOOTMAGIC_ENABLE, 82 consume extra memory; watch out for BOOTMAGIC_ENABLE,
83 MOUSEKEY_ENABLE, EXTRAKEY_ENABLE, CONSOLE_ENABLE, API_SYSEX_ENABLE 83 MOUSEKEY_ENABLE, EXTRAKEY_ENABLE, CONSOLE_ENABLE, API_SYSEX_ENABLE
84- DFU tools do /not/ allow you to write into the bootloader (unless 84- DFU tools do /not/ allow you to write into the bootloader (unless
85 you throw in extra fruitsalad of options), so there is little risk 85 you throw in extra fruit salad of options), so there is little risk
86 there. 86 there.
87- EEPROM has around a 100000 write cycle. You shouldn't rewrite the 87- EEPROM has around a 100000 write cycle. You shouldn't rewrite the
88 firmware repeatedly and continually; that'll burn the EEPROM 88 firmware repeatedly and continually; that'll burn the EEPROM
89 eventually. 89 eventually.
90## NKRO Doesn't work 90## NKRO Doesn't work
91First you have to compile frimware with this build option `NKRO_ENABLE` in **Makefile**. 91First you have to compile firmware with this build option `NKRO_ENABLE` in **Makefile**.
92 92
93Try `Magic` **N** command(`LShift+RShift+N` by default) when **NKRO** still doesn't work. You can use this command to toggle between **NKRO** and **6KRO** mode temporarily. In some situations **NKRO** doesn't work you need to switch to **6KRO** mode, in particular when you are in BIOS. 93Try `Magic` **N** command(`LShift+RShift+N` by default) when **NKRO** still doesn't work. You can use this command to toggle between **NKRO** and **6KRO** mode temporarily. In some situations **NKRO** doesn't work you need to switch to **6KRO** mode, in particular when you are in BIOS.
94 94
95If your firmware built with `BOOTMAGIC_ENABLE` you need to turn its switch on by `BootMagic` **N** command(`Space+N` by default). This setting is stored in EEPROM and keeped over power cycles. 95If your firmware built with `BOOTMAGIC_ENABLE` you need to turn its switch on by `BootMagic` **N** command(`Space+N` by default). This setting is stored in EEPROM and kept over power cycles.
96 96
97https://github.com/tmk/tmk_keyboard#boot-magic-configuration---virtual-dip-switch 97https://github.com/tmk/tmk_keyboard#boot-magic-configuration---virtual-dip-switch
98 98
99 99
100## TrackPoint Needs Reset Circuit (PS/2 Mouse Support) 100## TrackPoint Needs Reset Circuit (PS/2 Mouse Support)
101Without reset circuit you will have inconsistent reuslt due to improper initialize of the hardware. See circuit schematic of TPM754. 101Without reset circuit you will have inconsistent result due to improper initialize of the hardware. See circuit schematic of TPM754.
102 102
103- http://geekhack.org/index.php?topic=50176.msg1127447#msg1127447 103- http://geekhack.org/index.php?topic=50176.msg1127447#msg1127447
104- http://www.mikrocontroller.net/attachment/52583/tpm754.pdf 104- http://www.mikrocontroller.net/attachment/52583/tpm754.pdf
@@ -107,7 +107,7 @@ Without reset circuit you will have inconsistent reuslt due to improper initiali
107## Can't Read Column of Matrix Beyond 16 107## Can't Read Column of Matrix Beyond 16
108Use `1UL<<16` instead of `1<<16` in `read_cols()` in [matrix.h] when your columns goes beyond 16. 108Use `1UL<<16` instead of `1<<16` in `read_cols()` in [matrix.h] when your columns goes beyond 16.
109 109
110In 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`. 110In C `1` means one of [int] type which is [16 bit] 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`.
111 111
112http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279 112http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279
113 113
@@ -181,11 +181,11 @@ Pressing any key during sleep should wake host.
181- http://arduino.cc/en/uploads/Main/arduino-leonardo-schematic_3b.pdf 181- http://arduino.cc/en/uploads/Main/arduino-leonardo-schematic_3b.pdf
182- http://arduino.cc/en/uploads/Main/arduino-micro-schematic.pdf 182- http://arduino.cc/en/uploads/Main/arduino-micro-schematic.pdf
183 183
184Arduino leonardo and micro have **ATMega32U4** and can be used for TMK, though Arduino bootloader may be a problem. 184Arduino Leonardo and micro have **ATMega32U4** and can be used for TMK, though Arduino bootloader may be a problem.
185 185
186 186
187## Using PF4-7 Pins of USB AVR? 187## Using PF4-7 Pins of USB AVR?
188You 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. 188You 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 affected with this.
189 189
190If you are using Teensy this isn't needed. Teensy is shipped with JTAGEN fuse bit unprogrammed to disable the function. 190If you are using Teensy this isn't needed. Teensy is shipped with JTAGEN fuse bit unprogrammed to disable the function.
191 191