Skip to content

Commit c4d56b4

Browse files
Update README.md
1 parent aeee189 commit c4d56b4

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

README.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,21 +6,23 @@
66

77
3. In your terminal, change to the directory where you downloaded the executable file.
88

9-
4. Run the following command:
9+
4. Move your compiled firmware to the same directory as the executable file.
10+
11+
5. Run the following command:
1012
```
1113
./mdloader --first --download FILE_NAME --restart
1214
```
1315
**Note**: Replace `FILE_NAME` with the filename of your compiled firmware.
1416

15-
5. You should see the message:
17+
6. You should see the message:
1618
```
1719
Scanning for device for 60 seconds
1820
.....
1921
```
2022

21-
6. Within 60 seconds, press the reset button on your keyboard. For most keyboards running the default firmware, you can hold `Fn` + `b` for half a second and release to reset your keyboard (you will see the LEDs turn off). For CTRL keyboards in the first production run running original firmware or of the first method does not work for you, you will need to use a pin to press the reset button through the hole in the bottom of the keyboard.
23+
7. Within 60 seconds, press the reset button on your keyboard. For most keyboards running the default firmware, you can hold `Fn` + `b` for half a second and release to reset your keyboard (you will see the LEDs turn off). For CTRL keyboards in the first production run running original firmware or of the first method does not work for you, you will need to use a pin to press the reset button through the hole in the bottom of the keyboard.
2224

23-
7. You should see a series of messages similar to:
25+
8. You should see a series of messages similar to:
2426
```
2527
Device port: /dev/cu.usbmodem234431 (SAMD51J18A)
2628
@@ -33,7 +35,7 @@ Booting device... Success!
3335
Closing port... Success!
3436
```
3537

36-
8. Afterwards, you should see the keyboard's LEDs light up again (if your configuration has LEDs enabled) and the keyboard should respond to typing. Your keyboard is now running the new firmware you specified.
38+
9. Afterwards, you should see the keyboard's LEDs light up again (if your configuration has LEDs enabled) and the keyboard should respond to typing. Your keyboard is now running the new firmware you specified.
3739

3840
-----
3941

0 commit comments

Comments
 (0)