The bits unlock_f1 and unlock_f2 in the symbol_lock_status register don't behave as documented in msk_top_regs.md. They are supposed to reset when the register is read, and they do not (unless there is somehow a constant flood of actual unlocks even when things appear to be working fine).
Now that these new debug registers are being polled by MQTT, the reset-on-read behavior is even less useful than it already would have been. I suggest these bits be rethought, or just removed.
The bits unlock_f1 and unlock_f2 in the symbol_lock_status register don't behave as documented in msk_top_regs.md. They are supposed to reset when the register is read, and they do not (unless there is somehow a constant flood of actual unlocks even when things appear to be working fine).
Now that these new debug registers are being polled by MQTT, the reset-on-read behavior is even less useful than it already would have been. I suggest these bits be rethought, or just removed.