v2.1.3 lets an installed system update with a plain sysupgrade, in place and keeping settings, as on any other OpenWrt device. v2.0.0 to v2.1.2 refused that and sent every update through the RAM installer, and that refusal was a mistake (below). Nothing else changes: the same base as v2.1.2 (kuncy7's c3po-tag-8021q at c36db6321c) and the same packages in the image.
- In-place updates.
sysupgrade -v /tmp/new.binfrom the installed system keeps settings;-nstarts from a clean configuration. A first install from stock still goes through the RAM installer, which reformats both UBI partitions. - Why earlier releases refused it. In July a unit stopped booting after a scripted in-place upgrade, with
UBI init error 22on every boot, which we read as the stock loader attaching only a freshly formatted kernel UBI. That was never reproduced, and it does not hold: a unit upgraded in place 13 times in a row with its settings, and the kernel UBI was rewritten in place whenever it wasn't reformatted first. The loader printsUBI init error 22whenever it tries its second slot, which can't attach on this layout, so the message alone never pointed at the kernel UBI. Details: in-place updates.
Updating from v2.0.0 to v2.1.2: those releases still refuse an in-place sysupgrade, so add -F this once. First check the image's sha256 against sha256sums.txt and that sysupgrade -T /tmp/new.bin shows only the refusal, then run sysupgrade -F -v /tmp/new.bin, which keeps settings. -F also skips the check that the image is meant for this board, so use this board's sysupgrade image. From v2.1.3 on, a plain sysupgrade does. The RAM installer route still works too (the RAM installer without UART). From v1.x, use the RAM installer as before (upgrading from v1.x). From stock firmware, python3 install.py from xiaomi-openwrt-install installs this release.
Tested on the bench, installed on NAND in place over the unit's only cable, keeping its configuration:
- v2.1.2 -> v2.1.3 with
sysupgrade -Fafter the sha256 and-Tchecks above, then v2.1.3 onto itself with a plainsysupgrade. The configuration came through unchanged, both radios' APs came up, NSS Wi-Fi offload was on, and kernel modules install from the v2.1.3 repository. - The retest behind this change: 13 in-place upgrades in a row on that unit, all booted (in-place updates).
- One spontaneous reset about two minutes after a reboot, which did not happen again; v2.1.3 has v2.1.2's kernel and modules (the NAND run).
Known issues: all. Each release has its own package repository: after updating, apk installs kernel modules from the v2.1.3 one, which the image lists.
Checksums are in sha256sums.txt; packages are signed with this port's v2 key, which the image trusts.