diff options
| author | Kurtis Lew <kurtis.a.lew@gmail.com> | 2020-09-10 18:44:39 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-09-10 18:44:39 -0700 |
| commit | 5b38fcff71a0e22407dbd418fb1900614ecbfb6f (patch) | |
| tree | 30db7afef86c6ff9ee0ec76a32b152f19c8ae678 | |
| parent | 073f5c8b98c5111d954fe5bfe98951b24983449d (diff) | |
Reversed pairing instructions
| -rw-r--r-- | docs/docs/troubleshooting.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md index 4820e11..deb89b6 100644 --- a/docs/docs/troubleshooting.md +++ b/docs/docs/troubleshooting.md @@ -9,7 +9,7 @@ The following page provides suggestions for common errors that may occur during ### File Transfer Error -Variations of the warnings shown below occur when flashing the `<firmware>.uf2` onto the microcontroller. This is because the microcontroller resets itself before the OS receives confirmation that the file transfer is complete. Errors like this are normal and can generally be ignored. Verification of a functional board can be done by attempting to pair your computer to your newly flashed keyboard via Bluetooth or plugging in a USB cable if `ZMK_USB` is enabled in your Kconfig.defconfig. +Variations of the warnings shown below occur when flashing the `<firmware>.uf2` onto the microcontroller. This is because the microcontroller resets itself before the OS receives confirmation that the file transfer is complete. Errors like this are normal and can generally be ignored. Verification of a functional board can be done by attempting to pair your newly flashed keyboard to your computer via Bluetooth or plugging in a USB cable if `ZMK_USB` is enabled in your Kconfig.defconfig. |  | | :-------------------------------------------------------------------------------: | |