You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-26Lines changed: 21 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,13 @@
6
6
7
7
3. Press the reset button on your keyboard.
8
8
9
-
4. In your terminal, change to the directory where you downloaded the executable.
9
+
4. In your terminal, change to the directory where you downloaded the executable and applet-*.bin file(s).
10
10
11
-
5.**Windows** - Run `mdloader_windows.exe --list`. Copy the port name, e.g. `/dev/ttyACM0`, `/dev/ttyS23`, `/dev/cu.usbmodem234411`.
12
-
**Linux** - Run `./mdloader_linux --list`. Copy the port name as described above.
13
-
**Mac** - Run `./mdloader_mac --list`. If you downloaded with Mac Safari, run `./mdloader_mac.dms --list`. Copy the port name as described above.
11
+
5.**Windows** - Run `mdloader_windows.exe --first --download FILE_NAME --restart`. Replace "FILE_NAME" with the filename of your compiled firmware.
12
+
**Linux** - Run `mdloader_linux --first --download FILE_NAME --restart`. Replace "FILE_NAME" with the filename of your compiled firmware.
13
+
**Mac** - Run `mdloader_mac --first --download FILE_NAME --restart`. If you downloaded with Mac Safari, run `mdloader_mac.dms --first --download FILE_NAME --restart`. Replace "FILE_NAME" with the filename of your compiled firmware.
14
14
15
-
6.**Windows** - Run `mdloader_windows.exe --port PORT_NAME --download FILE_NAME --restart`. Replace "PORT_NAME" with the port name you copied in the previous step. Replace "FILE_NAME" with the filename of your compiled firmware.
16
-
**Linux** - Run `./mdloader_linux --port PORT_NAME --download FILE_NAME --restart`. Replace "PORT_NAME" and "FILE_NAME" in the command as instructed above.
17
-
**Mac** - Run `./mdloader_mac --port PORT_NAME --download FILE_NAME --restart`. If you downloaded with Mac Safari, run `./mdloader_mac.dms --port PORT_NAME --download FILE_NAME --restart`. Replace "PORT_NAME" and "FILE_NAME" in the command as instructed above.
18
-
19
-
7. Enjoy (important)
15
+
6. Enjoy (important)
20
16
21
17
-----
22
18
@@ -27,8 +23,8 @@ Massdrop Loader is used to read firmware from and write firmware to Massdrop key
27
23
## Supported operating systems
28
24
29
25
Windows XP or greater (32-bit and 64-bit versions, USB Serial driver in drv_win folder)
30
-
Linux x86 (32-bit and 64-bit versions)
31
-
Mac OS X
26
+
Linux x86 (32-bit and 64-bit versions)
27
+
Mac OS X
32
28
33
29
## Supported devices
34
30
@@ -40,15 +36,17 @@ Enter mdloader directory where Makefile is located and excute:
40
36
41
37
`make`
42
38
43
-
This will create a build/ directory with the compiled executable.
39
+
This will create a `build` directory with the compiled executable and required applet-*.bin files.
44
40
Run `./build/mdloader` to test.
41
+
Note that the target MCU applet file must exist in the directory the executable is called from.
45
42
46
43
## Usage
47
44
```
48
45
Usage: mdloader [options] ...
49
46
-h --help Print this help message
50
47
-v --verbose Print verbose messages
51
48
-V --version Print version information
49
+
-f --first Use first found device port as programming port
52
50
-l --list Print valid attached devices for programming
53
51
-p --port port Specify programming port
54
52
-U --upload file Read firmware from device into <file>
@@ -61,27 +59,24 @@ Usage: mdloader [options] ...
61
59
--restart Restart device after successful programming
62
60
```
63
61
64
-
To detect connected keyboards ready for programming:
65
-
66
-
`mdloader --list`
67
-
68
-
If you do not see your keyboard listed, try pressing the reset button on your keyboard and try again.
69
-
70
-
Assume for example the listing included a device at port name `THE_PORT`
The program will now be searching for your device. Press the reset switch found through the small hole on the back case or by appropriate key sequence to enter programming mode and allow programming to commence.
67
+
Firmware may be provided as a binary ending in .bin or an Intel HEX format ending in .hex, but .hex is preferred for data integrity.
68
+
Note that safeguards are in place to prevent overwriting the bootloader section of the device.
0 commit comments