Skip to content

Commit a07e539

Browse files
committed
small dfu clarifications
1 parent 2ee02fb commit a07e539

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

content/updatefirmware/expansionboard.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -29,10 +29,10 @@ In normal operation, the expansionboard is in Application mode. However when we
2929

3030
| Board | DFU bootloader (update mode) | Application firmware (normal mode) |
3131
| :--- | :--- | :--- |
32-
| Pygate | `0xED15` | `0xED14` |
33-
| Pytrack | `0xF014` | `0xF013` |
34-
| Pysense | `0xF011` | `0xF012` |
35-
| Pyscan | `0xEF37` | `0xEF38` |
32+
| Pygate | `0xED15` | `0xED14` |
33+
| Pytrack | `0xF014` | `0xF013` |
34+
| Pysense | `0xF011` | `0xF012` |
35+
| Pyscan | `0xEF37` | `0xEF38` |
3636
| Expansion Board v3 | `0xEF99` | `0xEF98` |
3737

3838
_Note: USB Vendor ID is always_ `0x04D8`
@@ -61,8 +61,8 @@ _Note: USB Vendor ID is always_ `0x04D8`
6161

6262
* Windows
6363

64-
Download and install [DFU-util v0.9](http://dfu-util.sourceforge.net/releases/dfu-util-0.9-win64.zip)
65-
64+
Download and install [DFU-util v0.9](http://dfu-util.sourceforge.net/releases/dfu-util-0.9-win64.zip)
65+
6666
For Windows, we will need to install separate drivers for the board to recognized as a Pycom board in DFU mode.
6767
1. Disconnect the USB cable to your expansion board
6868
2. Hold down the DFU mode button on the shield
@@ -92,7 +92,7 @@ To enter update mode follow these steps:
9292
1. Navigate the terminal to the folder where you downloaded the `.dfu` file to
9393
2. Unplug the device
9494
3. Remove the development module
95-
4. Press this button on your device:
95+
4. Press and hold the S1/MCLR button on your device. Highlighted in red below:
9696

9797
| Expansionboard 3.1 | Pygate | Pysense | Pysense 2.0 X | Pytrack | Pytrack 2.0 X | PyScan |
9898
|:----|:----|:-----|:--------|:-----|:-----|:----|
@@ -145,9 +145,9 @@ Done!
145145

146146
Using `lsusb` command, the device should be visible in both normal and bootloader modes.
147147

148-
For exemple, a Pytrack board is visible as either:
148+
For example, a Pytrack board is visible as either:
149149

150150
* `Bus 020 Device 004: ID 04d8:f014 Microchip Technology Inc. Application Specific Device`
151-
* this is bootloader mode (`f014` is USB PID), active just for 7-8 seconds, if the reset button was just pressed before plugging USB connector.
151+
* This is the bootloader mode (`f014` is USB PID). It is active for just 7-8 seconds, if the MCLR button was pressed just before plugging in the USB connector.
152152
* `Bus 020 Device 005: ID 04d8:f013 Microchip Technology Inc. Pytrack Serial: Pyabcde0`
153-
* this is normal, application mode (`f013` is USB PID), this means the bootloader verified application partition and it boot-up correctly.
153+
* This is the normal, application mode (`f013` is USB PID). This means the bootloader verified the firmware and it boot-up correctly.

0 commit comments

Comments
 (0)