A DWT comparator match on a read is thus treated as unknown, even though it could indicate an error of some kind. While the action is not defined in the context of RTIC Scope, warning the user that an unexpected read occurred to a variable hidden from the user (indicative of something going very wrong) is a good idea. The packet should still be treated as unknown for replay purposes.
In
recovery.rs
:A DWT comparator match on a read is thus treated as unknown, even though it could indicate an error of some kind. While the action is not defined in the context of RTIC Scope, warning the user that an unexpected read occurred to a variable hidden from the user (indicative of something going very wrong) is a good idea. The packet should still be treated as unknown for replay purposes.