aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorfauxpark <fauxpark@gmail.com>2019-12-12 06:33:10 +1100
committerDrashna Jaelre <drashna@live.com>2019-12-11 11:33:09 -0800
commit770a4ee7291095aaa6548d3e988633bf2ae6e6c0 (patch)
tree77f927d380d9f3b356c4a96dfa789980a26b47d2 /docs
parentccda62616d422ae6df810b6fd68fc8e61002e278 (diff)
downloadqmk_firmware-770a4ee7291095aaa6548d3e988633bf2ae6e6c0.tar.gz
qmk_firmware-770a4ee7291095aaa6548d3e988633bf2ae6e6c0.zip
[Docs] Remove some outdated FAQ items (#7607)
Diffstat (limited to 'docs')
-rw-r--r--docs/faq_build.md4
-rw-r--r--docs/faq_debug.md68
-rw-r--r--docs/faq_keymap.md63
-rw-r--r--docs/fr-fr/faq_build.md4
-rw-r--r--docs/fr-fr/faq_debug.md71
-rw-r--r--docs/fr-fr/faq_keymap.md67
-rw-r--r--docs/zh-cn/faq_build.md5
-rw-r--r--docs/zh-cn/faq_debug.md68
-rw-r--r--docs/zh-cn/faq_keymap.md63
9 files changed, 3 insertions, 410 deletions
diff --git a/docs/faq_build.md b/docs/faq_build.md
index 4c91cb28b..b2e448306 100644
--- a/docs/faq_build.md
+++ b/docs/faq_build.md
@@ -87,10 +87,6 @@ Re-running the QMK installation script (`./util/qmk_install.sh` from the `qmk_fi
87 87
88If that doesn't work, then you may need to download and run Zadig. See [Bootloader Driver Installation with Zadig](driver_installation_zadig.md) for more detailed information. 88If that doesn't work, then you may need to download and run Zadig. See [Bootloader Driver Installation with Zadig](driver_installation_zadig.md) for more detailed information.
89 89
90## WINAVR is Obsolete
91It is no longer recommended and may cause some problem.
92See [TMK Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
93
94## USB VID and PID 90## USB VID and PID
95You can use any ID you want with editing `config.h`. Using any presumably unused ID will be no problem in fact except for very low chance of collision with other product. 91You can use any ID you want with editing `config.h`. Using any presumably unused ID will be no problem in fact except for very low chance of collision with other product.
96 92
diff --git a/docs/faq_debug.md b/docs/faq_debug.md
index 1e0cdc82b..6c66defbd 100644
--- a/docs/faq_debug.md
+++ b/docs/faq_debug.md
@@ -112,56 +112,6 @@ In C `1` means one of [int] type which is [16 bit] in case of AVR so you can't s
112 112
113http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279 113http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279
114 114
115
116## Bootloader Jump Doesn't Work
117Properly configure bootloader size in **Makefile**. With wrong section size bootloader won't probably start with **Magic command** and **Boot Magic**.
118```
119# Size of Bootloaders in bytes:
120# Atmel DFU loader(ATmega32U4) 4096
121# Atmel DFU loader(AT90USB128) 8192
122# LUFA bootloader(ATmega32U4) 4096
123# Arduino Caterina(ATmega32U4) 4096
124# USBaspLoader(ATmega***) 2048
125# Teensy halfKay(ATmega32U4) 512
126# Teensy++ halfKay(AT90USB128) 2048
127OPT_DEFS += -DBOOTLOADER_SIZE=4096
128```
129AVR Boot section size are defined by setting **BOOTSZ** fuse in fact. Consult with your MCU datasheet.
130Note that **Word**(2 bytes) size and address are used in datasheet while TMK uses **Byte**.
131
132AVR Boot section is located at end of Flash memory like the followings.
133```
134byte Atmel/LUFA(ATMega32u4) byte Atmel(AT90SUB1286)
1350x0000 +---------------+ 0x00000 +---------------+
136 | | | |
137 | | | |
138 | Application | | Application |
139 | | | |
140 = = = =
141 | | 32KB-4KB | | 128KB-8KB
1420x6000 +---------------+ 0x1E000 +---------------+
143 | Bootloader | 4KB | Bootloader | 8KB
1440x7FFF +---------------+ 0x1FFFF +---------------+
145
146
147byte Teensy(ATMega32u4) byte Teensy++(AT90SUB1286)
1480x0000 +---------------+ 0x00000 +---------------+
149 | | | |
150 | | | |
151 | Application | | Application |
152 | | | |
153 = = = =
154 | | 32KB-512B | | 128KB-2KB
1550x7E00 +---------------+ 0x1FC00 +---------------+
156 | Bootloader | 512B | Bootloader | 2KB
1570x7FFF +---------------+ 0x1FFFF +---------------+
158```
159
160And see this discussion for further reference.
161https://github.com/tmk/tmk_keyboard/issues/179
162
163If you are using a TeensyUSB, there is a [known bug](https://github.com/qmk/qmk_firmware/issues/164) in which the hardware reset button prevents the RESET key from working. Unplugging the keyboard and plugging it back in should resolve the problem.
164
165## Special Extra Key Doesn't Work (System, Audio Control Keys) 115## Special Extra Key Doesn't Work (System, Audio Control Keys)
166You need to define `EXTRAKEY_ENABLE` in `rules.mk` to use them in QMK. 116You need to define `EXTRAKEY_ENABLE` in `rules.mk` to use them in QMK.
167 117
@@ -194,24 +144,6 @@ If you would like to keep JTAG enabled, just add the following to your `config.h
194#define NO_JTAG_DISABLE 144#define NO_JTAG_DISABLE
195``` 145```
196 146
197## Adding LED Indicators of Lock Keys
198You need your own LED indicators for CapsLock, ScrollLock and NumLock? See this post.
199
200http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p191560
201
202## Program Arduino Micro/Leonardo
203Push reset button and then run command like this within 8 seconds.
204
205```
206avrdude -patmega32u4 -cavr109 -b57600 -Uflash:w:adb_usb.hex -P/dev/ttyACM0
207```
208
209Device name will vary depending on your system.
210
211http://arduino.cc/en/Main/ArduinoBoardMicro
212https://geekhack.org/index.php?topic=14290.msg1563867#msg1563867
213
214
215## USB 3 Compatibility 147## USB 3 Compatibility
216I heard some people have a problem with USB 3 port, try USB 2 port. 148I heard some people have a problem with USB 3 port, try USB 2 port.
217 149
diff --git a/docs/faq_keymap.md b/docs/faq_keymap.md
index 84d8548d4..2d00e8bef 100644
--- a/docs/faq_keymap.md
+++ b/docs/faq_keymap.md
@@ -67,24 +67,8 @@ After enabling this feature use keycodes `KC_LCAP`, `KC_LNUM` and `KC_LSCR` in y
67Old vintage mechanical keyboards occasionally have lock switches but modern ones don't have. ***You don't need this feature in most case and just use keycodes `KC_CAPS`, `KC_NLCK` and `KC_SLCK`.*** 67Old vintage mechanical keyboards occasionally have lock switches but modern ones don't have. ***You don't need this feature in most case and just use keycodes `KC_CAPS`, `KC_NLCK` and `KC_SLCK`.***
68 68
69## Input Special Characters Other Than ASCII like Cédille 'Ç' 69## Input Special Characters Other Than ASCII like Cédille 'Ç'
70NO UNIVERSAL METHOD TO INPUT THOSE WORKS OVER ALL SYSTEMS. You have to define **MACRO** in way specific to your OS or layout.
71 70
72See this post for example **MACRO** code. 71See the [Unicode](feature_unicode.md) feature.
73
74http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p195620
75
76On **Windows** you can use `AltGr` key or **Alt code**.
77* http://en.wikipedia.org/wiki/AltGr_key
78* http://en.wikipedia.org/wiki/Alt_code
79
80On **Mac** OS defines `Option` key combinations.
81* http://en.wikipedia.org/wiki/Option_key#Alternative_keyboard_input
82
83On **Xorg** you can use `compose` key, instead.
84* http://en.wikipedia.org/wiki/Compose_key
85
86And see this for **Unicode** input.
87* http://en.wikipedia.org/wiki/Unicode_input
88 72
89## `Fn` Key on macOS 73## `Fn` Key on macOS
90 74
@@ -130,51 +114,6 @@ https://github.com/tekezo/Karabiner/issues/403
130 114
131See the [Grave Escape](feature_grave_esc.md) feature. 115See the [Grave Escape](feature_grave_esc.md) feature.
132 116
133## Arrow on Right Modifier Keys with Dual-Role
134This turns right modifier keys into arrow keys when the keys are tapped while still modifiers when the keys are hold. In TMK the dual-role function is dubbed **TAP**.
135```
136
137#include "keymap_common.h"
138
139
140/* Arrow keys on right modifier keys with TMK dual role feature
141 *
142 * https://github.com/tmk/tmk_core/blob/master/doc/keymap.md#213-modifier-with-tap-keydual-role
143 * https://en.wikipedia.org/wiki/Modifier_key#Dual-role_keys
144 */
145const uint8_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
146 /* 0: qwerty */
147 [0] = LAYOUT( \
148 ESC, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, MINS,EQL, NUHS,BSPC, \
149 TAB, Q, W, E, R, T, Y, U, I, O, P, LBRC,RBRC,BSLS, \
150 LCTL,A, S, D, F, G, H, J, K, L, SCLN,QUOT,ENT, \
151 LSFT,NUBS,Z, X, C, V, B, N, M, COMM,DOT, SLSH,FN0, ESC, \
152 FN4, LGUI,LALT, SPC, APP, FN2, FN1, FN3),
153 [1] = LAYOUT( \
154 GRV, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, TRNS,TRNS, \
155 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,\
156 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS, \
157 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,FN5, TRNS, \
158 TRNS,TRNS,TRNS, TRNS, TRNS,FN7, FN6, FN8),
159};
160
161const uint16_t PROGMEM fn_actions[] = {
162 [0] = ACTION_MODS_TAP_KEY(MOD_RSFT, KC_UP),
163 [1] = ACTION_MODS_TAP_KEY(MOD_RGUI, KC_DOWN),
164 [2] = ACTION_MODS_TAP_KEY(MOD_RALT, KC_LEFT),
165 [3] = ACTION_MODS_TAP_KEY(MOD_RCTL, KC_RIGHT),
166 [4] = ACTION_LAYER_MOMENTARY(1),
167 [5] = ACTION_MODS_TAP_KEY(MOD_RSFT, KC_PGUP),
168 [6] = ACTION_MODS_TAP_KEY(MOD_RGUI, KC_PGDN),
169 [7] = ACTION_MODS_TAP_KEY(MOD_RALT, KC_HOME),
170 [8] = ACTION_MODS_TAP_KEY(MOD_RCTL, KC_END),
171};
172
173```
174
175Dual-role key: https://en.wikipedia.org/wiki/Modifier_key#Dual-role_keys
176
177
178## Eject on Mac OSX 117## Eject on Mac OSX
179`KC_EJCT` keycode works on OSX. https://github.com/tmk/tmk_keyboard/issues/250 118`KC_EJCT` keycode works on OSX. https://github.com/tmk/tmk_keyboard/issues/250
180It seems Windows 10 ignores the code and Linux/Xorg recognizes but has no mapping by default. 119It seems Windows 10 ignores the code and Linux/Xorg recognizes but has no mapping by default.
diff --git a/docs/fr-fr/faq_build.md b/docs/fr-fr/faq_build.md
index 6fba1e430..448ff01aa 100644
--- a/docs/fr-fr/faq_build.md
+++ b/docs/fr-fr/faq_build.md
@@ -86,10 +86,6 @@ Relancer le script d'installation de QMK (`./util/qmk_install.sh` situé dans r
86 86
87Si vous rencontrez toujours des problèmes, essayez de télécharger et lancer Zadig. Voir [Installation du driver du bootloader avec Zadig](driver_installation_zadig.md) pour plus d'informations. 87Si vous rencontrez toujours des problèmes, essayez de télécharger et lancer Zadig. Voir [Installation du driver du bootloader avec Zadig](driver_installation_zadig.md) pour plus d'informations.
88 88
89## WINAVR est obsolète
90
91Il n'est plus recommandé et peut causer des problèmes. Voir [TMK Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
92
93## USB VID et PID 89## USB VID et PID
94 90
95Vous pouvez utiliser l'ID de votre choix en modifier `config.h`. Il y a peu de chance de conflit avec d'autres produits. 91Vous pouvez utiliser l'ID de votre choix en modifier `config.h`. Il y a peu de chance de conflit avec d'autres produits.
diff --git a/docs/fr-fr/faq_debug.md b/docs/fr-fr/faq_debug.md
index 7a85fd1f2..754c79921 100644
--- a/docs/fr-fr/faq_debug.md
+++ b/docs/fr-fr/faq_debug.md
@@ -104,58 +104,6 @@ En C, `1` implique un type [int] qui est [16 bits] pour les AVR, ce qui implique
104 104
105http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279 105http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279
106 106
107## Bootloader Jump ne fonctionne pas
108
109Configurez correctement la taille du bootloader dans le **Makefile**. Une mauvaise taille de section du bootloader empêchera probablement le démarrage avec **Magic command** et **Boot Magic**.
110
111```
112# Size of Bootloaders in bytes:
113# Atmel DFU loader(ATmega32U4) 4096
114# Atmel DFU loader(AT90USB128) 8192
115# LUFA bootloader(ATmega32U4) 4096
116# Arduino Caterina(ATmega32U4) 4096
117# USBaspLoader(ATmega***) 2048
118# Teensy halfKay(ATmega32U4) 512
119# Teensy++ halfKay(AT90USB128) 2048
120OPT_DEFS += -DBOOTLOADER_SIZE=4096
121```
122
123La taille de la section de démarrage de AVR est définie par l'option **BOOTSZ** fuse. Vérifiez la fiche technique du MCU. Veuilez noter que les tailles et adresses sont définies en **Word** (2 octets) dans la fiche technique alors que TMK utilise des **Byte**.
124
125La section de boot AVR se trouve à la fin de la mémoire flash, comme suit.
126
127```
128byte Atmel/LUFA(ATMega32u4) byte Atmel(AT90SUB1286)
1290x0000 +---------------+ 0x00000 +---------------+
130 | | | |
131 | | | |
132 | Application | | Application |
133 | | | |
134 = = = =
135 | | 32KB-4KB | | 128KB-8KB
1360x6000 +---------------+ 0x1E000 +---------------+
137 | Bootloader | 4KB | Bootloader | 8KB
1380x7FFF +---------------+ 0x1FFFF +---------------+
139
140
141byte Teensy(ATMega32u4) byte Teensy++(AT90SUB1286)
1420x0000 +---------------+ 0x00000 +---------------+
143 | | | |
144 | | | |
145 | Application | | Application |
146 | | | |
147 = = = =
148 | | 32KB-512B | | 128KB-2KB
1490x7E00 +---------------+ 0x1FC00 +---------------+
150 | Bootloader | 512B | Bootloader | 2KB
1510x7FFF +---------------+ 0x1FFFF +---------------+
152```
153
154Référez-vous à cette discussion pour plus de référence.
155https://github.com/tmk/tmk_keyboard/issues/179
156
157Si vous utilisez un TeensyUSB, il y a un [bug connu](https://github.com/qmk/qmk_firmware/issues/164) qui fait que le bouton reset matériel empêche la touche RESET de fonctionner. Débrancher et rebrancher le clavier devrait résoudre le problème.
158
159## Les touches spéciales ne fonctionnent pas (Touche Système, Touches de contrôle du son) 107## Les touches spéciales ne fonctionnent pas (Touche Système, Touches de contrôle du son)
160 108
161Vous devez définir `EXTRAKEY_ENABLE` dans le fichier `rules.mk` pour les utiliser dans QMK. 109Vous devez définir `EXTRAKEY_ENABLE` dans le fichier `rules.mk` pour les utiliser dans QMK.
@@ -189,25 +137,6 @@ Si vous voulez garder JTAG activé, ajoutez la ligne suivante à votre fichier `
189#define NO_JTAG_DISABLE 137#define NO_JTAG_DISABLE
190``` 138```
191 139
192## Adding LED Indicators of Lock Keys
193
194Si vous souhaitez votre propre indicateur LED pour CapsLock, ScrollLock et NumLock alors lisez ce post.
195
196http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p191560
197
198## Programmer Arduino Micro/Leonardo
199
200Appuyez sur le bouton reset puis lancez la commande suivante dans les 8 secondes.
201
202```
203avrdude -patmega32u4 -cavr109 -b57600 -Uflash:w:adb_usb.hex -P/dev/ttyACM0
204```
205
206Le nom du périphérique peut varier en fonction de votre système.
207
208http://arduino.cc/en/Main/ArduinoBoardMicro
209https://geekhack.org/index.php?topic=14290.msg1563867#msg1563867
210
211## Compatibilité USB 3 140## Compatibilité USB 3
212 141
213Il semble que certaines personnes ont eu des problèmes avec les ports USB 3, essayez un port USB 2. 142Il semble que certaines personnes ont eu des problèmes avec les ports USB 3, essayez un port USB 2.
diff --git a/docs/fr-fr/faq_keymap.md b/docs/fr-fr/faq_keymap.md
index 8244d4225..2cbbe9308 100644
--- a/docs/fr-fr/faq_keymap.md
+++ b/docs/fr-fr/faq_keymap.md
@@ -72,24 +72,7 @@ Des vieux claviers mécaniques ont parfois des touches à verrouillage, mais les
72 72
73## Ajouter des caractères spéciaux autres que ASCII comme la cédille 'Ç' 73## Ajouter des caractères spéciaux autres que ASCII comme la cédille 'Ç'
74 74
75IL N'EXISTE AUCUNE METHODE UNIVERSELLE POUR LES AJOUTER QUI FONCTIONNE SUR TOUS LES SYSTEMES. Vous devez définir une **MACRO** d'une manière spécifique à votre OS ou layout. 75Voir la fonctionnalité [Unicode](feature_unicode.md).
76
77Voir ce post pour un exemple de code **MACRO**.
78
79http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p195620
80
81Sous **Windows** vous pouvez utiliser la touche `AltGr` ou **Alt code**.
82* http://en.wikipedia.org/wiki/AltGr_key
83* http://en.wikipedia.org/wiki/Alt_code
84
85Sous **Mac OS** définissez une combinaison de touche `Option`.
86* http://en.wikipedia.org/wiki/Option_key#Alternative_keyboard_input
87
88Sous **Xorg** vous pouvez utiliser une touche `compose` à la place.
89* http://en.wikipedia.org/wiki/Compose_key
90
91Et voir ceci pour une entrée **Unicode**.
92* http://en.wikipedia.org/wiki/Unicode_input
93 76
94## Touche `Fn` sur macOS 77## Touche `Fn` sur macOS
95 78
@@ -144,54 +127,6 @@ Cette fonctionnalité permet d'utiliser une touche à la fois comme touche Écha
144 127
145Voir la fonctionnalité [Grave Escape](feature_grave_esc.md). 128Voir la fonctionnalité [Grave Escape](feature_grave_esc.md).
146 129
147## Avoir les touches modificatrices qui ont double usage en flèches directionnelles.
148
149Ceci transforme les touches "modificateur droit" en touches fléchées lorsque les touches sont seulement "tapées" tout en restant des modificateurs lorsqu'elles sont maintenues.
150
151Dans TMK la fonction double rôle s'appelle **TAP**.
152
153```C
154
155#include "keymap_common.h"
156
157
158/* Arrow keys on right modifier keys with TMK dual role feature
159 *
160 * https://github.com/tmk/tmk_core/blob/master/doc/keymap.md#213-modifier-with-tap-keydual-role
161 * https://en.wikipedia.org/wiki/Modifier_key#Dual-role_keys
162 */
163const uint8_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
164 /* 0: qwerty */
165 [0] = LAYOUT( \
166 ESC, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, MINS,EQL, NUHS,BSPC, \
167 TAB, Q, W, E, R, T, Y, U, I, O, P, LBRC,RBRC,BSLS, \
168 LCTL,A, S, D, F, G, H, J, K, L, SCLN,QUOT,ENT, \
169 LSFT,NUBS,Z, X, C, V, B, N, M, COMM,DOT, SLSH,FN0, ESC, \
170 FN4, LGUI,LALT, SPC, APP, FN2, FN1, FN3),
171 [1] = LAYOUT( \
172 GRV, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, TRNS,TRNS, \
173 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,\
174 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS, \
175 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,FN5, TRNS, \
176 TRNS,TRNS,TRNS, TRNS, TRNS,FN7, FN6, FN8),
177};
178
179const uint16_t PROGMEM fn_actions[] = {
180 [0] = ACTION_MODS_TAP_KEY(MOD_RSFT, KC_UP),
181 [1] = ACTION_MODS_TAP_KEY(MOD_RGUI, KC_DOWN),
182 [2] = ACTION_MODS_TAP_KEY(MOD_RALT, KC_LEFT),
183 [3] = ACTION_MODS_TAP_KEY(MOD_RCTL, KC_RIGHT),
184 [4] = ACTION_LAYER_MOMENTARY(1),
185 [5] = ACTION_MODS_TAP_KEY(MOD_RSFT, KC_PGUP),
186 [6] = ACTION_MODS_TAP_KEY(MOD_RGUI, KC_PGDN),
187 [7] = ACTION_MODS_TAP_KEY(MOD_RALT, KC_HOME),
188 [8] = ACTION_MODS_TAP_KEY(MOD_RCTL, KC_END),
189};
190
191```
192
193Touches double rôle : https://en.wikipedia.org/wiki/Modifier_key#Dual-role_keys
194
195## Eject sur Mac OSX 130## Eject sur Mac OSX
196 131
197Le keycode`KC_EJCT` fonctionne sous OSX. https://github.com/tmk/tmk_keyboard/issues/250 132Le keycode`KC_EJCT` fonctionne sous OSX. https://github.com/tmk/tmk_keyboard/issues/250
diff --git a/docs/zh-cn/faq_build.md b/docs/zh-cn/faq_build.md
index 2f33fbca9..82d0697a8 100644
--- a/docs/zh-cn/faq_build.md
+++ b/docs/zh-cn/faq_build.md
@@ -56,11 +56,6 @@ SUBSYSTEMS=="usb", ATTRS{idVendor}=="1c11", MODE:="0666"
56?> 事实上没有一个驱动的最佳选择，有些选项就是和某些系统相辅相成。但libUSB和WinUSB似乎也算是这里的最佳选择了。 56?> 事实上没有一个驱动的最佳选择，有些选项就是和某些系统相辅相成。但libUSB和WinUSB似乎也算是这里的最佳选择了。
57如果bootloader在设备列表中没有显示，你可能要使能 "List all devices"选项在选项菜单中`Options`，然后找到有问题的bootloader设备。(译者注：在win10中可能为 查看-显示隐藏的设备) 57如果bootloader在设备列表中没有显示，你可能要使能 "List all devices"选项在选项菜单中`Options`，然后找到有问题的bootloader设备。(译者注：在win10中可能为 查看-显示隐藏的设备)
58 58
59
60## WINAVR已淘汰
61不再推荐使用WINAVR，使用可能会导致问题
62详情请见[TMK Issue #99](https://github.com/tmk/tmk_keyboard/issues/99).
63
64## USB VID 和 PID 59## USB VID 和 PID
65你可以在编辑`config.h`时使用任何你想用的ID值。实际上，使用任何可能未使用的ID都没有问题，除了有极低的与其他产品发生冲突的可能性。 60你可以在编辑`config.h`时使用任何你想用的ID值。实际上，使用任何可能未使用的ID都没有问题，除了有极低的与其他产品发生冲突的可能性。
66 61
diff --git a/docs/zh-cn/faq_debug.md b/docs/zh-cn/faq_debug.md
index a3cc7c510..7eff7f265 100644
--- a/docs/zh-cn/faq_debug.md
+++ b/docs/zh-cn/faq_debug.md
@@ -101,56 +101,6 @@ https://github.com/tmk/tmk_keyboard#boot-magic-configuration---virtual-dip-switc
101 101
102http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279 102http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad-keyboard-t6181-60.html#p146279
103 103
104
105## Bootloader跳转不好用
106在**Makefile**中正确配置**Makefile**大小。如果分区大小不正确，引导加载程序可能无法从**Magic command**和**Boot Magic**加载。
107```
108# bootloader字节数：
109# Atmel DFU loader(ATmega32U4) 4096
110# Atmel DFU loader(AT90USB128) 8192
111# LUFA bootloader(ATmega32U4) 4096
112# Arduino Caterina(ATmega32U4) 4096
113# USBaspLoader(ATmega***) 2048
114# Teensy halfKay(ATmega32U4) 512
115# Teensy++ halfKay(AT90USB128) 2048
116OPT_DEFS += -DBOOTLOADER_SIZE=4096
117```
118AVR引导大小是通过**BOOTSZ**熔丝位来设置的。查阅你单片机的datasheet。
119记住，datasheet用的是**Word**(2字节)表示大小和地址，TMK用的是**Byte**。
120
121AVR引导部分位于闪存的末尾，如下所示（Application是应用区，Bootloader是引导区）。
122```
123byte Atmel/LUFA(ATMega32u4) byte Atmel(AT90SUB1286)
1240x0000 +---------------+ 0x00000 +---------------+
125 | | | |
126 | | | |
127 | Application | | Application |
128 | | | |
129 = = = =
130 | | 32KB-4KB | | 128KB-8KB
1310x6000 +---------------+ 0x1E000 +---------------+
132 | Bootloader | 4KB | Bootloader | 8KB
1330x7FFF +---------------+ 0x1FFFF +---------------+
134
135
136byte Teensy(ATMega32u4) byte Teensy++(AT90SUB1286)
1370x0000 +---------------+ 0x00000 +---------------+
138 | | | |
139 | | | |
140 | Application | | Application |
141 | | | |
142 = = = =
143 | | 32KB-512B | | 128KB-2KB
1440x7E00 +---------------+ 0x1FC00 +---------------+
145 | Bootloader | 512B | Bootloader | 2KB
1460x7FFF +---------------+ 0x1FFFF +---------------+
147```
148
149详情请见下方issue。
150https://github.com/tmk/tmk_keyboard/issues/179
151
152如果你使用TeensyUSB, 有一个[已知bug](https://github.com/qmk/qmk_firmware/issues/164)硬件重置按钮阻止软件定义重置键工作。重新插拔键盘就好了。
153
154## 特殊额外键不起作用(系统，音频控制键) 104## 特殊额外键不起作用(系统，音频控制键)
155你要在`rules.mk`定义`EXTRAKEY_ENABLE`在QMK中使用它们。 105你要在`rules.mk`定义`EXTRAKEY_ENABLE`在QMK中使用它们。
156 106
@@ -173,24 +123,6 @@ EXTRAKEY_ENABLE = yes # 音频控制和系统控制
173 123
174Arduino Leonardo和micro使用**ATMega32U4**，该芯片TMK可用，但Arduino的bootloader会导致问题。 124Arduino Leonardo和micro使用**ATMega32U4**，该芯片TMK可用，但Arduino的bootloader会导致问题。
175 125
176## 为锁定键添加指示灯
177你要自制CapsLock, ScrollLock 和 NumLock指示灯？见下文。
178
179http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p191560
180
181## 为Arduino Micro/Leonardo编程
182按下重置键然后在8秒内运行下方这样的命令。
183
184```
185avrdude -patmega32u4 -cavr109 -b57600 -Uflash:w:adb_usb.hex -P/dev/ttyACM0
186```
187
188设备名称因系统而异。
189
190http://arduino.cc/en/Main/ArduinoBoardMicro
191https://geekhack.org/index.php?topic=14290.msg1563867#msg1563867
192
193
194## USB 3 兼容性 126## USB 3 兼容性
195据传说有些人用USB3接口会有问题，用USB2的试试。 127据传说有些人用USB3接口会有问题，用USB2的试试。
196 128
diff --git a/docs/zh-cn/faq_keymap.md b/docs/zh-cn/faq_keymap.md
index ee8e3c06b..7fb434b4c 100644
--- a/docs/zh-cn/faq_keymap.md
+++ b/docs/zh-cn/faq_keymap.md
@@ -66,24 +66,8 @@ https://github.com/tmk/tmk_keyboard/issues/67
66远古机械键盘偶尔会有自锁机械开关，现在几乎没有了。***大多数情况下你不需要使用该功能，且要使用`KC_CAPS`, `KC_NLCK`和`KC_SLCK`这三个键码。*** 66远古机械键盘偶尔会有自锁机械开关，现在几乎没有了。***大多数情况下你不需要使用该功能，且要使用`KC_CAPS`, `KC_NLCK`和`KC_SLCK`这三个键码。***
67 67
68## 输入ASCII之外的特殊字符比如Cédille 'Ç' 68## 输入ASCII之外的特殊字符比如Cédille 'Ç'
69没有在所有系统中输入这个的通用方法。你要定义针对你的特定操作系统或布局的**宏**。
70 69
71比如看这个**宏**代码的文章。 70请见[Unicode](feature_unicode.md)功能。
72
73http://deskthority.net/workshop-f7/tmk-keyboard-firmware-collection-t4478-120.html#p195620
74<!--翻译问题：下方维基百科链接应全部替换为中文链接，暂未找到全部-->
75在**Windows**上，可以用`AltGr`键或**Alt码**。
76* http://en.wikipedia.org/wiki/AltGr_key
77* https://zh.wikipedia.org/wiki/Alt%E7%A0%81
78
79在**Mac OS**定义`Option`键组合。
80* https://zh.wikipedia.org/wiki/Option%E9%94%AE#%E6%9B%BF%E4%BB%A3%E9%94%AE%E7%9B%98%E8%BE%93%E5%85%A5
81
82在**Xorg**可以改用`compose`键。
83* http://en.wikipedia.org/wiki/Compose_key
84
85下方链接查看**Unicode**输入。
86* http://en.wikipedia.org/wiki/Unicode_input
87 71
88## macOS上的`Fn` 72## macOS上的`Fn`
89 73
@@ -136,51 +120,6 @@ https://github.com/tekezo/Karabiner/issues/403
136 120
137请见[Grave Escape](feature_grave_esc.md)功能。 121请见[Grave Escape](feature_grave_esc.md)功能。
138 122
139## 右侧双角色修改键(诸如Shift、Alt等有修改其他键作用的键)变箭头键
140右侧修改键单击时会变为箭头键，长按就还是修改键。在TMK中双角色键称之为**TAP**.
141```
142
143#include "keymap_common.h"
144
145
146/* 用TMK双角色键功能实现右侧修改键改箭头键
147 *
148 * https://github.com/tmk/tmk_core/blob/master/doc/keymap.md#213-modifier-with-tap-keydual-role
149 * https://en.wikipedia.org/wiki/Modifier_key#Dual-role_keys
150 */
151const uint8_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
152 /* 0: qwerty */
153 [0] = LAYOUT( \
154 ESC, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, MINS,EQL, NUHS,BSPC, \
155 TAB, Q, W, E, R, T, Y, U, I, O, P, LBRC,RBRC,BSLS, \
156 LCTL,A, S, D, F, G, H, J, K, L, SCLN,QUOT,ENT, \
157 LSFT,NUBS,Z, X, C, V, B, N, M, COMM,DOT, SLSH,FN0, ESC, \
158 FN4, LGUI,LALT, SPC, APP, FN2, FN1, FN3),
159 [1] = LAYOUT( \
160 GRV, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12, TRNS,TRNS, \
161 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,\
162 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS, \
163 TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,TRNS,FN5, TRNS, \
164 TRNS,TRNS,TRNS, TRNS, TRNS,FN7, FN6, FN8),
165};
166
167const uint16_t PROGMEM fn_actions[] = {
168 [0] = ACTION_MODS_TAP_KEY(MOD_RSFT, KC_UP),
169 [1] = ACTION_MODS_TAP_KEY(MOD_RGUI, KC_DOWN),
170 [2] = ACTION_MODS_TAP_KEY(MOD_RALT, KC_LEFT),
171 [3] = ACTION_MODS_TAP_KEY(MOD_RCTL, KC_RIGHT),
172 [4] = ACTION_LAYER_MOMENTARY(1),
173 [5] = ACTION_MODS_TAP_KEY(MOD_RSFT, KC_PGUP),
174 [6] = ACTION_MODS_TAP_KEY(MOD_RGUI, KC_PGDN),
175 [7] = ACTION_MODS_TAP_KEY(MOD_RALT, KC_HOME),
176 [8] = ACTION_MODS_TAP_KEY(MOD_RCTL, KC_END),
177};
178
179```
180
181双角色键说明: https://en.wikipedia.org/wiki/Modifier_key#Dual-role_keys
182
183
184## Mac OSX的弹出键 123## Mac OSX的弹出键
185`KC_EJCT` 键码在OSX可以使用 https://github.com/tmk/tmk_keyboard/issues/250 124`KC_EJCT` 键码在OSX可以使用 https://github.com/tmk/tmk_keyboard/issues/250
186似乎Windows10会忽略该键码，Linux/Xorg可以识别该键码但默认不映射。 125似乎Windows10会忽略该键码，Linux/Xorg可以识别该键码但默认不映射。
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-02 06:28:18 +0000