Firmware Status Report
Compact engineering summary for the live M62 firmware on March 31, 2026. This report combines tonight’s standard suite coverage with the one-off non-reset capability sweep.
Device
M62CF-EU
Serial 67C10M25F00120
Firmware
1.0.11.26032007
Primary test target on 192.168.1.1
Controller Host
192.168.1.132
Oktopus and artifact viewer host
Reset Used
No
Factory reset explicitly excluded
Overall Assessment
Works Well
- Discovery and large read collection
- Router-local USP runtime presence
- Guest Wi-Fi toggle and rollback
- Neighbor scan command acceptance
- Router-side recovery and evidence capture
Works With Limits
- Single-leaf Wi-Fi changes under controlled conditions
- Targeted controller-driven troubleshooting writes
- Acceptance and advertised analysis for model-gap discovery
Needs Work
- Repeated write stability
- Rollback reliability
- Controller/runtime host and station alignment
- Radio toggle behavior
- OpenSpeedTest operational path
Test Plan
- Collect baseline controller and router context from Oktopus and router SSH.
- Run a phased one-off capability sweep with no reset.
- Recover any residual configuration drift manually if needed.
- Run tonight’s standard suite coverage for overall firmware status.
- Consolidate results into an engineering-facing summary.
Standard Suite Results
| Suite |
Run |
Result |
Notes |
all --read-only |
1775014940-all |
PASS 1271, FAIL 756, SKIP 38, BLOCKED 1 |
Most failures were advertised/acceptance coverage gaps rather than hard runtime outage. This run overlapped the nightly write run and should be read as stressed concurrent coverage. |
nightly |
1775014940-nightly |
PASS 1, FAIL 1 |
guest_wifi.toggle passed. wifi.radio.toggle failed. |
router --read-only |
1775015576-router |
PASS 1, FAIL 3 |
Router-local USP runtime passed, but controller-side Wi-Fi host/station trees were empty during the compare run. |
Capability Sweep Results
| Run |
Actions |
Set Accepted |
Verify Succeeded |
Rollback Succeeded |
Headline |
| 1775010413 |
6 |
5 |
0 |
2 |
Individual writes can be accepted, but rollback is inconsistent. |
| 1775011894 |
9 |
1 |
0 |
0 |
After stress, writes degraded quickly into 504/503. |
| 1775012582 |
81 |
1 |
0 |
0 |
Broad mutation is not currently a reliable automation path for this firmware. |
Key Findings
- Discovery and baseline reads are good enough for ongoing QA.
- The router remains the stronger truth source when controller results are ambiguous.
- One-off troubleshooting writes are possible, but batch write campaigns overwhelm the path quickly.
- The controller can temporarily lose Wi-Fi host/station/DataElements visibility while router runtime remains healthy.
- No reset was executed. One temporary SSID rename drift was manually restored.
Final State
- SSID
Device.WiFi.SSID.4.SSID restored from mud puddle-lab to mud puddle.
- All three radios reported up after recovery.
- Main
WaterCooler SSIDs were serving clients on 2.4 GHz and 5 GHz.
Recommended Next Steps
- Use paced, category-by-category mutation testing instead of broad batch sweeps.
- Prioritize engineering fixes for repeated write stability and rollback reliability.
- Keep router-SSH validation as the default evidence path whenever USP results are incomplete.
- Use the Actions tab for targeted troubleshooting, not wide mutation campaigns.