kb01/zmk
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(troubleshooting): Apply suggestions from code review

Browse source 
Co-authored-by: innovaker <66737976+innovaker@users.noreply.github.com>
This commit is contained in:
Okke Formsma 2021-01-04 19:38:05 +01:00 • committed by GitHub
parent 42ba47f74f
commit ee678ded12
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/docs/troubleshooting.md
View file

@ -54,9 +54,10 @@ Since then, a much simpler procedure of performing a bluetooth reset for split k
**New Procedure:** **New Procedure:**
1. Open [latest build in Github Actions](https://github.com/zmkfirmware/zmk/actions?query=workflow%3ABuild+branch%3Amain) and open the first 'result' on that page. 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. From the next page under "Artifacts", download the `$boardname-settings_reset-zmk` zip file.
1. Unzip the downloaded file 1. Unzip the downloaded file.
1. Put each half of the split keyboard into bootloader mode 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 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. to avoid accidental bonding between the halves.