Closed flihp closed 7 months ago
I've seen this again but this time it was immediately following the expected (but annoying) period that the UART is unstable on the LPC55 after a cold boot. Makes sense that the last failed exchange might only be partially corrupt. This isn't a bug.
Been a while since I've run through the identity certification process but one of the first things I did threw back a warning that's interesting:
If the
Ack
we got back from the RoT was invalid then I would expect we would do more than just warn the caller. Seems like this indicates that the RoT got a corrupted message and we should throw an error.