MikroTik reuses board names across hardware revisions — the 2025 hEX S is a completely different SoC than the original. /system/resource/print only says architecture-name: arm, which doesn’t tell you the real ISA. The truth is in /system/routerboard/print:
rb.rsc
/system/routerboard/printoutput.txt
routerboard: yes
board-name: hEX S
model: E60iUGS
serial-number: ...
firmware-type: en7562
minimum-firmware: 7.20.8
current-firmware: 7.20.8
upgrade-firmware: 7.24.5Decoding
| Field | Meaning |
|---|---|
model | Product code. E60iUGS = hEX S 2025 = EcoNet EN7562CT (ARMv5!). Original hEX S = IPQ4019 (ARM Cortex-A7 / armv7). |
firmware-type | SoC family identifier — en7562 is the giveaway for EN7562-based boards |
Why it matters
- EN7562CT devices (hEX S 2025
E60iUGS, hEX RefreshE50UG, hAP ax S): containers can only run arm32v5 binaries — anything armv6/armv7/aarch64 exits withsignal 4 (Illegal instruction). - Same “hEX S” board name, different CPU → wildly different container compatibility.
current-firmwarevsupgrade-firmwarealso shows whether RouterBOOT is behind RouterOS (worth knowing — but there are community reports of issues after RouterBOOT upgrades on EN7562 boards; many deliberately leave it).
If you’re automating device provisioning, key off model/firmware-type, not board-name.
Check out similar posts by category:
MikroTik Networking Embedded
If this post helped you, please consider buying me a coffee or donating via PayPal to support research & publishing of new posts on TechOverflow