diff options
| author |  skullY <skullydazed@gmail.com> | 2020-02-27 20:53:50 -0800 |
|---|---|---|
| committer |  skullydazed <skullydazed@users.noreply.github.com> | 2020-03-05 16:00:10 -0800 |
| commit | 54c58ea6de61a0f1fefa06e8271e2e11f9027940 (patch) | |
| tree | 2ce4163cda8164edccd6f06f6e384861a205006c /docs/newbs_testing_debugging.md | |
| parent | a95a314f78fd96aca7cc496b10bd310e28b1b66e (diff) | |
| download | qmk_firmware-54c58ea6de61a0f1fefa06e8271e2e11f9027940.tar.gz | |
Add explicit id tags to externally linked headers
Diffstat (limited to 'docs/newbs_testing_debugging.md')
| -rw-r--r-- | docs/newbs_testing_debugging.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_testing_debugging.md b/docs/newbs_testing_debugging.md index c6c1bd50c..181238902 100644 --- a/docs/newbs_testing_debugging.md +++ b/docs/newbs_testing_debugging.md @@ -6,7 +6,7 @@ Once you've flashed your keyboard with a custom firmware you're ready to test it Testing your keyboard is usually pretty straightforward. Press every single key and make sure it sends the keys you expect. You can use [QMK Configurator](https://config.qmk.fm/#/test/)'s test mode to check your keyboard, even if it doesn't run QMK. -## Debugging +## Debugging :id=debugging Your keyboard will output debug information if you have `CONSOLE_ENABLE = yes` in your `rules.mk`. By default the output is very limited, but you can turn on debug mode to increase the amount of debug output. Use the `DEBUG` keycode in your keymap, use the [Command](feature_command.md) feature to enable debug mode, or add the following code to your keymap. |