summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOkke Formsma <okke@formsma.nl>2021-01-05 20:29:47 +0100
committerGitHub <noreply@github.com>2021-01-05 19:29:47 +0000
commit4c1f615714e84a5b05fe76af69faf446cd09fb45 (patch)
tree043849a42c7b1c85b95f2f716ceb6d832b1ce474
parent5c11962d986753d5da9244cf572242f43f4d126c (diff)
docs(troubleshooting): fix reset uf2 download instructions
PR: #512 Co-authored-by: innovaker <66737976+innovaker@users.noreply.github.com>
-rw-r--r--docs/docs/troubleshooting.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md
index 0fe0b66..23403ee 100644
--- a/docs/docs/troubleshooting.md
+++ b/docs/docs/troubleshooting.md
@@ -54,7 +54,10 @@ Since then, a much simpler procedure of performing a bluetooth reset for split k
**New Procedure:**
-1. Log into Github and download the "settings clear" UF2 image from the [latest build in Github Actions](https://github.com/zmkfirmware/zmk/actions?query=workflow%3ABuild+branch%3Amain)
+1. [Open the GitHub `Actions` tab and select the `Build` workflow](https://github.com/zmkfirmware/zmk/actions?query=workflow%3ABuild+branch%3Amain).
+1. Select the top 'result' on that page.
+1. From the next page under "Artifacts", download the `$boardname-settings_reset-zmk` zip file.
+1. Unzip the downloaded file.
1. Put each half of the split keyboard into bootloader mode
1. Flash one of the halves of the split with the "settings clear" UF2 image from step 1. Immediately after flashing "settings clear" to the chosen half, immediately put it into bootloader mode
to avoid accidental bonding between the halves.