The Defend-O-Tron supports two separate firmware update paths, each for a different situation:
The Defend-O-Tron also receives routine Debian package updates as shown on the admin interface under Software Updates. Those keep the underlying operating system patched and are separate from firmware-image updates — both are safe to run, both happen alongside each other.
Open the admin interface and look for Firmware Image in the Cockpit sidebar on the left.

When there's nothing to do, the page shows a Current state card listing the running firmware version and a Last result of up-to-date. You don't need to do anything — the Defend-O-Tron checks for new firmware on its own once a week.

A blue Update available card appears with the firmware version on offer and a Download & stage button.

Click Download & stage.
Once the download finishes, an Image staged card appears. The new firmware is on the device but hasn't taken over yet — your current firmware is still running.

Click Apply. This tells the Defend-O-Tron to use the new firmware on the next reboot.
Reboot the Defend-O-Tron when convenient — use the Reboot button on the Cockpit Overview page.
The previous firmware stays on the device after you apply a new one. If anything goes wrong, you can switch back to it — see Rolling back firmware below.
The page shows a banner across the top whenever something important happens:
Two ways to undo a firmware change:
Both rollback options require a reboot to take effect.
Firmware rollback is intended for problems you discover after an update — for example, a setting that didn't carry over cleanly. It's not a substitute for cabling the device out of your network if you suspect a serious issue.
The Defend-O-Tron checks the firmware server once a week on its own. You don't need to remember to check — just open the Firmware Image page when it's convenient. If an update was found between checks, the blue Update available card will be waiting.
You only need this section if you're setting up a new device for the first time, recovering from a problem the admin interface can't fix, or wiping a device for redeployment. For routine firmware updates, use the in-place method above.
You'll require an SD card imaging utility to start and a microSD card, preferrably 16GB - 32GB.

You can download the Etcher utility from here https://etcher.balena.io and install it.
The firmware images for the Defend-O-Tron can be downloaded from here https://firmware.awesome-o.cloud
Firmware:
Download the firmware image and burn it to the microSD card (at least 16G) with Etcher.

Once Etcher is complete flashing the SD card, Windows may display a disk and give a popup window saying each disk is un-recognized, click cancel.
If you accidentally click format disk you will have to re-flash the SD card again with Etcher.

The MASK ROM button allows the Defend-O-Tron to bypass booting from the internal eMMC disk and look for a bootable SD card instead.
This serves a few purposes:
The Mask ROM feature is meant to be protected physically. Keep the device secured and away from any unauthorized personnel who could access it with this method. Gaining physical access to any device, not just the Defend-O-Tron can allow bad actors to penetrate or exploit your security equipment.
You have to mask boot the device with the SD card inserted correctly in the slot, which is located on the side of the unit. This is best done with a monitor, keyboard and mouse attached.
The eMMC MASK button is located on the side for revision 1 of the unit.

The eMMC MASK button is located on the front for revision 2 of the unit.

Do not cancel the process or it will leave your Defend-O-Tron in an unstable and/or unusable state
When the setup is completed you can browse to the admin interface and continue with the admin-interface setup.