MM2S Block Requirements - WP545

Replacing FMEA with Datapath Analysis for IP Designs (WP545)

Document ID
WP545
Release Date
2023-06-14
Revision
1.0 English

For each block, a different tab (as represented in the MM2S Block table in MM2S Block) is used for the specific logic within the block where the diagnostics are applied. The MM2S Block table contains the following three sections:

  • External Connections into and out of the block that communicate information from outside the IP block.
  • Internal Signal Block Connections that identify internal signaling between blocks within the IP.
  • Block Function Description that describes the operation of the block.

For each entry under the external connections section, the following information is required:

  • External connection number: used for grouping properties for the signal or bus.
  • Signal name.
  • Unique ID tag: used to identify the signal for analysis.
  • Fault modes: a list of fault modes associated with the unique ID tag. A new line for each fault mode is used to help identify the related diagnostic.
  • Fault initiators: a list of potential causes of the fault mode affect.
  • Diagnostic: a proposed diagnostic to detect each fault initiator mode based on first principles discussed. Not all fault modes can be addressed.
  • Repeat: a repeat tag that indicates this signal has already been analyzed in a previous tab or entry, so the diagnostic coverage of the signal is not double counted.
  • Claimed diagnostic coverage: the percentage of the diagnostic coverage that the diagnostic provides based on the fault initiator entered.

For each entry under the internal connections section, the following information is required:

  • Internal connection number: used for grouping properties for the signal or bus connection between blocks.
  • Signal name.
  • Unique ID tag: used to identify the signal for analysis
  • Fault modes: a list of fault modes associated with the unique ID tag. A new line for each fault mode is used to help identify the related diagnostic.
  • Fault initiators: a list of potential causes of the fault mode affect.
  • Diagnostic: proposed diagnostic to detect each fault initiator based on first principles discussed.
  • Repeat: a repeat tag that indicates this signal has already been analyzed in a previous tab or entry so the diagnostic coverage of the signal is not double counted.
  • Claimed diagnostic coverage: the percentage of the diagnostic coverage that the diagnostic provides based on the fault mode entered.

For the block functional description entry, the following information is required:

  • Block description.
  • Unique block ID_Tag.
  • Fault modes of the logic implemented in the block. A new line for each fault mode is used to help identify the related diagnostic.
  • Fault initiators: a list of potential causes of the fault mode affect.
  • Diagnostic: proposed diagnostic to detect each fault initiator based on first principles discussed.
  • Claimed diagnostic coverage: the percentage of the diagnostic coverage that the diagnostic provides based on the fault mode entered.