Non-technical summary of current USP firmware status for the M62 evaluation unit as of March 31, 2026.
We ran a full evening review of the firmware using our Oktopus USP lab. This included standard read-only reporting, controlled nightly write tests, direct router verification over SSH, and a one-time non-reset capability exercise to see how much configuration control USP can safely handle.
The firmware is in a usable position for visibility and targeted testing, but it is not yet stable enough for broad automated reconfiguration through USP.
In simple terms: it reads well, it can perform some focused actions, but it becomes unreliable when many configuration changes are attempted in sequence.
From a program perspective, the firmware is moving in the right direction. The product now supports meaningful visibility and some controlled operational actions. That is enough to continue engineering evaluation, demos, and targeted support-style workflows.
The current risk is not everyday reads. The main risk is configuration churn. When many changes are attempted one after another, the USP path can degrade into timeouts and incomplete rollback behavior.
This firmware shows good progress in observability and targeted USP control. It is suitable for continued lab validation and limited troubleshooting use, but broader automated configuration coverage still needs engineering hardening.
Full engineering detail, nightly outputs, and capability sweep artifacts are available in the companion firmware status report.