RouterBOOT is the bootloader: the program the board runs first at power-on, like a computer’s BIOS. It starts RouterOS, and if that won’t boot, it’s what reinstalls the system over the network (Netinstall). It lives apart from RouterOS, so a new system doesn’t replace it on its own.
/system routerboard print
# routerboard: yes
# board-name: hAP ax^2
# current-firmware: 7.20.8
# upgrade-firmware: 7.23.8
/system routerboard upgrade
# Do you really want to upgrade firmware? [y/n]
/system reboot
upgrade-firmware is the bootloader that came with the new RouterOS and waits to be written. current-firmware is
the one running. A difference between them means the step was skipped.
So you don’t have to remember:
/system routerboard settings set auto-upgrade=yes
Then after a RouterOS update the bootloader writes itself and takes effect on the next reboot — do it right away or wait for the next update.
The bootloader doesn’t roll back with the system: after a RouterOS downgrade it stays new, and that’s fine.
If it doesn’t work
Ran /system routerboard upgrade, but current-firmware hasn’t changed
- Cause
- The new bootloader is written but takes effect only after a reboot.
- Fix
/system reboot, then/system routerboard printagain:current-firmwareandupgrade-firmwarematch.
After an update the router logs that the bootloader is older than the system
- Cause
- The bootloader fell several versions behind: RouterOS got updated, but
routerboard upgradenever ran. - Fix
- Update the bootloader now. The old one still works, but boot and hardware fixes only arrive with it.