The Firmware Updater plugin can be used to flash pre-compiled firmware images to your printer from a local file or URL.

1. Supported Boards
2. Plugin Installation
3. Plugin Configuration
4. Flashing Firmware
5. Advanced Options
   1. Customizing the Command Lines
   2. Pre and Post Flash Settings
   3. Plugin Options
6. Troubleshooting
7. Donations

The plugin supports a variety of boards, based on the MCU (processor) they have:

Please open a Github issue if you would like a new board or MCU to be supported. If it's a new type of board which requires hardware testing please consider making a donation to help fund the costs.

Install via the bundled Plugin Manager or manually using this URL: https://github.com/OctoPrint/OctoPrint-FirmwareUpdater/archive/master.zip

Using OctoPrint's Software Update plugin you can choose one of three Release Channels to follow:

If you report a bug or request a new feature you will probalby be asked to test development or RC builds.

The appropriate flashing tool for the board type needs to be selected. See the table in the supported boards section to choose the appropriate method.

Note: If your board is updated by copying a file named firmware.bin to the SD card and resetting the board, you should use the lpc176x method. This applies to SKR Pro v1.1 or SKR Mini E3 v2 boards and probably others.

Plugin settings vary depending on the flashing tool and are documented on the page for each flash method. Follow the instructions on the appropriate page to install and configure any necessary tools:

• Atmega (AVR) based boards
• AT90USB based boards
• LPC176x and other boards which are updated from the SD card
  • Option 1 - File copy using SD mount
  • Option 2 - File transfer using serial protocol
• SAM based boards
• STM32 based boards which do not update from the SD card

Once the plugin is configured, flashing firmware is a simple operation:

1. Select the COM port to communicate with the board
2. Select a firmware file, either located on the filesystem or via a URL
3. Click the appropriate Flash from button
4. Wait for the firmware update to complete

The command lines for avrdude, bossac, and dfu-programmer can be customized by editing the string in the advanced settings for the flash method. Text in braces ({}) will be substituted for preconfigured values if present.

1. avrdude flash method only
2. bossac flash method only
3. dfu-programmer flash method only
4. avrdude and dfu-programmer flash methods

Command lines can be returned to the default by clicking the Reset button.

{avrdude} -v -q -p {mcu} -c {programmer} -P {port} -D -C {conffile} -b {baudrate} {disableverify} -U flash:w:{firmware}:i

{bossac} -i -p {port} -U true -e -w {disableverify} -b {firmware} -R

Erase: {bossac} -i -p {port} -U true -e -w {disableverify} -b {firmware} -R Flash:

The flash sequence is:

1. Execute the pre-flash system command(s) on the host
2. Send the pre-flash gcode commands(s) to the printer
3. Pause for the pre-flash gcode delay
4. Disconnect the printer
5. Execute the firmware update
6. Pause for the post-flash delay
7. Execute the post-flash system command(s) on the host
8. Reconnect the printer
9. Send the post-flash gcode command(s) to the printer

Log messages can be found in the OctoPrint log octoprint.log and the Firmware Updater's console log plugin_firmwareupdater_console.log.

Both log files can be downloaded from OctoPrint's logging interface, found under 'Logging' in the settings page.

If you have trouble using the plugin please check these logs for any error messages. If you need help, please include both logs when reporting a problem.

Donations to help with the cost of test hardware are gratefully received using any of the methods below.