Fusa_Medini/ASIL-C_BOM/commons/table_11-51-08.measures

12 lines
3.2 KiB
XML

<?xml version="1.1" encoding="UTF-8"?>
<safety:MeasureCatalog xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:safety="http://www.ikv.de/medini/metamodels/SafetyModel/1.0" xmi:id="_t4v9QAX2Eeq4AMRV0u5rew" mediniIdentifier="_t4v9QAX2Eeq4AMRV0u5rew" name="P-11 Table 51 - PLD: Config Technology: Volatile Memory">
<collectionType href="http://www.ikv.de/medini/metamodels/SafetyModel/1.0#//SafetyMechanism"/>
<measures xsi:type="safety:SafetyMechanism" xmi:id="_kAP_YAX8Eeq4AMRV0u5rew" mediniIdentifier="_kAP_YAX8Eeq4AMRV0u5rew" id="ISO26262-11: Table 51" name="Read-back on download by downloading device" description="No default typical DC given in ISO26262" notes="Refers to the capability of many programmable devices to check the contents of their configuration registers and compare those to the intended (design specific) contents. If a mismatch is detected, this feature can change the status of an output pin or generate an interrupt so that the system can respond appropriately. To improve the usability as an online monitoring safety mechanism an efficient read back test can prioritize between safety-related and non-safety-related parts within a device. Safety related parts can be checked more frequently to considerably shorten failure detection time."/>
<measures xsi:type="safety:SafetyMechanism" xmi:id="_kAP_YQX8Eeq4AMRV0u5rew" mediniIdentifier="_kAP_YQX8Eeq4AMRV0u5rew" id="ISO26262-11: 5.1.13.5" name="RAM pattern test" maxDC="MEDIUM" notes="High coverage for stuck at failures. No coverage for linked failures. Can be appropriate to run under interrupt protection."/>
<measures xsi:type="safety:SafetyMechanism" xmi:id="_kAP_YgX8Eeq4AMRV0u5rew" mediniIdentifier="_kAP_YgX8Eeq4AMRV0u5rew" id="ISO26262-11: 5.1.13.7" name="RAM march test " maxDC="HIGH" notes="Depends on the write read order for linked cell coverage. Test generally not appropriate for run time."/>
<measures xsi:type="safety:SafetyMechanism" xmi:id="_kAP_YwX8Eeq4AMRV0u5rew" mediniIdentifier="_kAP_YwX8Eeq4AMRV0u5rew" id="ISO26262-11: 5.1.13.6" name="Parity bit" maxDC="LOW" notes="-"/>
<measures xsi:type="safety:SafetyMechanism" xmi:id="_kAP_ZAX8Eeq4AMRV0u5rew" mediniIdentifier="_kAP_ZAX8Eeq4AMRV0u5rew" id="ISO26262-11: 5.1.13.1" name="Memory monitoring using error-detection-correction codes (ECC)" maxDC="HIGH" notes="The effectiveness depends on the number of redundant bits. Can be used to correct errors."/>
<measures xsi:type="safety:SafetyMechanism" xmi:id="_kAP_ZQX8Eeq4AMRV0u5rew" mediniIdentifier="_kAP_ZQX8Eeq4AMRV0u5rew" id="ISO26262-11: 5.1.13.4" name="Block replication" maxDC="HIGH" notes="Common failure modes can reduce diagnostic coverage."/>
<measures xsi:type="safety:SafetyMechanism" xmi:id="_kAP_ZgX8Eeq4AMRV0u5rew" mediniIdentifier="_kAP_ZgX8Eeq4AMRV0u5rew" id="ISO26262-11: 5.1.13.8" name="Running checksum/CRC" maxDC="HIGH" notes="The effectiveness of the signature depends on the polynomial in relation to the block length of the information to be protected. Care is taken so that values used to determine checksum are not changed during checksum calculation. Probability is 1/maximum value of checksum if random pattern is returned."/>
</safety:MeasureCatalog>