Issue #18: Fix wrong documentation
This commit is contained in:
parent
c7ebe441c7
commit
569d42bbe9
@ -9,7 +9,7 @@ Overview
|
|||||||
The STM controller's backup RAM is used to store different kinds of information that shall be preserved if the controller resets.
|
The STM controller's backup RAM is used to store different kinds of information that shall be preserved if the controller resets.
|
||||||
The hardware setup is missing a separate powersupply for the controller's backup domain. Therefore, the backup RAM is cleared, when the power is cut.
|
The hardware setup is missing a separate powersupply for the controller's backup domain. Therefore, the backup RAM is cleared, when the power is cut.
|
||||||
|
|
||||||
The backup RAM is used to store permanent error flags (See :ref:`safety_flags`). This ensures the flags stay present, even if a system reset is performed. The only way to clear them is by cutting the power.
|
The backup RAM is used to store permanent error flags (See :ref:`safety_flags`). This ensures the flags that trigger hard faults / the panic mode, can be identified, although the wathcoog resets the controller. The only way to clear them is by cutting the power.
|
||||||
Because cutting the power is a way to clear the backup RAM, no separate method for clearing the error entries in the backup RAM is defined.
|
Because cutting the power is a way to clear the backup RAM, no separate method for clearing the error entries in the backup RAM is defined.
|
||||||
|
|
||||||
The backup RAM contents are protected by a `CRC Checksum`_.
|
The backup RAM contents are protected by a `CRC Checksum`_.
|
||||||
|
Loading…
Reference in New Issue
Block a user