Clarify RXPS watchdog scope in saved control results
This commit is contained in:
1 parent
e9f5d6f12f
commit
6811a9d909
2 files changed
+2
-2
No files matched your search
@@ -240,7 +240,7 @@ its existing transport and compile-time exclusions.
|
||||
The wired RAK3401 passed 19 control cases and two software-reboot persistence
|
||||
cases on the final Full repeater. Twenty-one read-only SWD samples confirmed
|
||||
the SPIM2 frequency register at 2, 4 and 8 MHz. Both profiles continued
|
||||
switching, core errors stayed zero, and no new radio-watchdog attempts were
|
||||
switching, core errors stayed zero, and no new RXPS-watchdog attempts were
|
||||
observed. Its original settings and gateway service were restored. The
|
||||
application update preserved its bootloader. These checks cover configuration,
|
||||
startup persistence and switching liveness; packet delivery, BLE, CPU sleep and
|
||||
|
||||
@@ -41,7 +41,7 @@
|
||||
8
|
||||
],
|
||||
"core_errors_after": 0,
|
||||
"new_radio_watchdog_attempts": 0,
|
||||
"new_rxps_watchdog_attempts": 0,
|
||||
"settings_restored": true,
|
||||
"gateway_service_restored": true,
|
||||
"application_only_update": true,
|
||||
|
||||
Reference in new issue
Block a user