One example of a possible memory configuration (Mode 4, Table 7.1) arranged
by “T”-logic is presented in Fig. 7.16. The example reflects a 32-bit configuration
with four modules of which two are used as spares (not connected) and two
duplicated.
7.3.4 Graceful Degradation Approach and Implementation
If one of the memory modules fails, the system can be reconfigured to exclude it
from the current configuration. Depending on the original configuration and the
need of the application, several degradation scenarios are possible. Please keep in
mind that a reconfiguration is only required to recover the system in case of a
permanent fault and not in case of a malfunction.
We present here two scenarios, the first starting from a triplicated system+spare
(Fig. 7.17) and the second starting from a duplicated system (Fig. 7.18). We then
use these scenarios to discuss in which cases further software intervention is
required.
Fig. 7.16 TLMU and syndrome as memory controllers
7.3 System Monitoring of Checking Process: A Syndrome
97
by “T”-logic is presented in Fig. 7.16. The example reflects a 32-bit configuration
with four modules of which two are used as spares (not connected) and two
duplicated.
7.3.4 Graceful Degradation Approach and Implementation
If one of the memory modules fails, the system can be reconfigured to exclude it
from the current configuration. Depending on the original configuration and the
need of the application, several degradation scenarios are possible. Please keep in
mind that a reconfiguration is only required to recover the system in case of a
permanent fault and not in case of a malfunction.
We present here two scenarios, the first starting from a triplicated system+spare
(Fig. 7.17) and the second starting from a duplicated system (Fig. 7.18). We then
use these scenarios to discuss in which cases further software intervention is
required.
Fig. 7.16 TLMU and syndrome as memory controllers
7.3 System Monitoring of Checking Process: A Syndrome
97