summaryrefslogtreecommitdiff
path: root/docs/newbs_testing_debugging.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/newbs_testing_debugging.md')
-rw-r--r--docs/newbs_testing_debugging.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_testing_debugging.md b/docs/newbs_testing_debugging.md
index c6c1bd50cb..1812389020 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.