summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2022-07-02 12:49:19 +0000
committerQMK Bot <hello@qmk.fm>2022-07-02 12:49:19 +0000
commitfcc14b8838281487bd048a4366113fb271d6113c (patch)
tree5b32952bf84835d5e2b6a557e52f3163ca867b72 /docs
parentbf44fc81bd1b8fcaa0215b8c7e568c9aaab6ec5d (diff)
parent4e35697e1a76a54f0ed756f98033535cf1322792 (diff)
downloadqmk_firmware-fcc14b8838281487bd048a4366113fb271d6113c.tar.gz
qmk_firmware-fcc14b8838281487bd048a4366113fb271d6113c.zip
Merge remote-tracking branch 'origin/master' into develop
Diffstat (limited to 'docs')
-rw-r--r--docs/newbs_flashing.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/newbs_flashing.md b/docs/newbs_flashing.md
index 6e90af9d10..549ffcb2be 100644
--- a/docs/newbs_flashing.md
+++ b/docs/newbs_flashing.md
@@ -108,6 +108,8 @@ However, this does rely on the bootloader being set by the keyboard. If this inf
In this case, you'll have to fall back on specifying the bootloader. See the [Flashing Firmware](flashing.md) Guide for more details.
+!> If your bootloader is not detected by `qmk flash`, try running `qmk doctor` for suggestions on how to fix common problems.
+
## Test It Out!
Congrats! Your custom firmware has been programmed to your keyboard and you're ready to test it out!