[otbn] A fatal error always transitions into locked state
When OTBN detect a fatal error, it unconditionally transitions into
locked state, not only if OTBN was busy before.
Signed-off-by: Philipp Wagner <phw@lowrisc.org>
diff --git a/hw/ip/otbn/doc/_index.md b/hw/ip/otbn/doc/_index.md
index e20876d..622226c 100644
--- a/hw/ip/otbn/doc/_index.md
+++ b/hw/ip/otbn/doc/_index.md
@@ -607,8 +607,8 @@
- A [secure wipe of internal state](#design-details-secure-wipe-internal) is performed.
- The {{< regref "ERR_BITS" >}} register is set to a non-zero value that describes the error.
- The current operation is marked as complete by setting {{< regref "INTR_STATE.done" >}}.
- - The {{< regref "STATUS" >}} register is set to `LOCKED`.
-3. A [fatal alert]({{< relref "#alerts" >}}) is raised.
+3. The {{< regref "STATUS" >}} register is set to `LOCKED`.
+4. A [fatal alert]({{< relref "#alerts" >}}) is raised.
Note that OTBN can detect some errors even when it isn't running.
One example of this is an error caused by an integrity error when reading or writing OTBN's memories over the bus.
