Using software rules to enhance fpga reliability
Download
1 / 17

Using Software Rules To Enhance FPGA Reliability - PowerPoint PPT Presentation


  • 146 Views
  • Uploaded on

Using Software Rules To Enhance FPGA Reliability. Chandru Mirchandani Lockheed-Martin Transportation & Security Solutions September 7-9, 2005. MIRCHANDANI. 1. P226/MAPLD2005. Introduction. To meet… System Objectives Develop a Process to… Verify FPGA Capability Validate FPGA Reliability

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Using Software Rules To Enhance FPGA Reliability' - gaia


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Using software rules to enhance fpga reliability

Using Software Rules To Enhance FPGA Reliability

Chandru Mirchandani

Lockheed-Martin Transportation & Security Solutions

September 7-9, 2005

MIRCHANDANI

1

P226/MAPLD2005


Introduction
Introduction

  • To meet…

    • System Objectives

  • Develop a Process to…

    • Verify FPGA Capability

    • Validate FPGA Reliability

    • Enhance FPGA Quality

  • By developing an Adaptive Model……..

    …...using Software Rules….

MIRCHANDANI

2

P226/MAPLD2005


Problem statement
Problem Statement

  • Requirement: Display sensor data in near-real time

  • Constraints: No loss of data, data quality & integrity, and timeliness

  • Information: Uncertain…to make design decision with lowest risk of failure

    Solution………Adaptive Model

MIRCHANDANI

3

P226/MAPLD2005


Software reliability
Software Reliability

  • Develop Criteria for Design Objective Acceptance

  • Prioritize tasks or functions in order of criticality

  • Develop metrics to measure performance of tasks with respect to constraints

  • Evaluate design options based on measured reliability metrics

MIRCHANDANI

4

P226/MAPLD2005


Typical software options

Processor 1

Application A1 (I-ary)

Application A1 (II-ary)

Processor 2

Typical Software Options

  • Critical software functions are distributed as redundant instances on multiple processors, thus minimizing the loss of service due to a processor failure……..

MIRCHANDANI

5

P226/MAPLD2005


Typical software options contd

Processor 1

Application B1

Application B1

Processor 2

Typical Software Options (contd.)

  • Distributing system level functions so that multiple users can independently use the function…....

MIRCHANDANI


Typical software options contd1

Processor 1

Application C1

Storage 1

Application C1

Storage 2

Processor 2

Typical Software Options (contd.)

  • Data replication to minimize the loss of critical data in the event of a processor failure or software system failure…..

MIRCHANDANI


Redundant instances of software
Redundant Instances of Software

  • Initially detect, contain and recover from faults as soon as possible, and in the event this is not possible

  • Allow the control to be passed on to the redundant instance within the reliability and availability requirements levied on the system

  • Finally, include language defined mechanisms to detect and prevent the propagation of errors

MIRCHANDANI

8

P226/MAPLD2005


Methodology
Methodology

  • Estimate the reliability based on instruction set and operational usage

  • Re-design critical elements to decrease risk

  • Re-evaluate the risk of failure based on a change in critical task design based on performance and requirements

  • Re-evaluate the reliability based on failure rate

  • Factor in the Uncertainty in Evaluation

MIRCHANDANI

9

P226/MAPLD2005


Task times
Task Times

MIRCHANDANI


Fpga system conceptual
FPGA System - Conceptual

  • Consider a FPGA-based system comprising of the Reading, Parsing and Pre-Processing Tasks…..

…each Task is a subsystem

MIRCHANDANI


Task reliability block diagram
Task Reliability Block Diagram

(exp(-γh.uh.λhwi.t).exp(-γs.us.λswi.t)

[1-{1-(exp(-(1-γh).λshwi.t).exp(-(1-γs).λsswi.t))}^2]

AND

OR

MIRCHANDANI


Definitions
Definitions

MIRCHANDANI


Parameters derivations
Parameters & Derivations

  • Failure Intensity: λshwi = λhwi.uh.(1-γh)

  • Failure Intensity: λsswi = λswi.us.(1-γs)

  • Common Cause: λhwi.uh.(γh) and λswi.us.(γs)

  • Execution Time t: ei . Τ

  • RSSi : Subsystem Reliability

  • System Reliability RS : RSS1 .RSS2 .RSS3

MIRCHANDANI

14

P226/MAPLD2005



Results
Results

MIRCHANDANI

16

P226/MAPLD2005


Conclusions
Conclusions

  • Cost and Schedule Slips

  • Development Delays and Costs

  • Adaptive Model

  • Optimization and Design Constraints

    Contact Address: chandru.j.mirchandani@lmco.com

MIRCHANDANI

17

P226/MAPLD2005