From 54c58ea6de61a0f1fefa06e8271e2e11f9027940 Mon Sep 17 00:00:00 2001 From: skullY Date: Thu, 27 Feb 2020 20:53:50 -0800 Subject: Add explicit id tags to externally linked headers --- docs/newbs_testing_debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/newbs_testing_debugging.md') 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. -- cgit v1.2.3