Skip to content

images: handle MikroTik sysupgrade-v7 sysupgrade images#73

Draft
map-b wants to merge 1 commit intoefahl:mainfrom
map-b:images-handle-mikrotik-v7
Draft

images: handle MikroTik sysupgrade-v7 sysupgrade images#73
map-b wants to merge 1 commit intoefahl:mainfrom
map-b:images-handle-mikrotik-v7

Conversation

@map-b
Copy link
Copy Markdown

@map-b map-b commented Apr 26, 2026

MikroTik boards with NOR flash need different sysupgrade images if the board is running RouterBOOT v7 or newer. Add a runtime check for the active bootloader and select the correct sysupgrade image accordingly.

Exploit the naming scheme and apply the logic for all existing profiles which includes a sysupgade image of type(named): "sysupgrade-v7".

Fixes: #68
Fixes: openwrt/openwrt#23057
Reported-by: corncobble (GitHub)

MikroTik boards with NOR flash need different sysupgrade images if the
board is running RouterBOOT v7 or newer. Add a runtime check for the
active bootloader and select the correct sysupgrade image accordingly.

Exploit the naming scheme and apply the logic for all existing profiles
which includes a sysupgade image of type(named): "sysupgrade-v7".

Fixes: efahl#68
Fixes: openwrt/openwrt#23057
Reported-by: corncobble (GitHub)
Signed-off-by: Mario Andrés Pérez <mapb_@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ramips: missing mikrotik bootloader check in platform.sh Support for additional syntax after Sys-Type (e.g. sysupgrade-v7)?

1 participant