1 / 16

CLEVER: C ross- L ayer E rror V erification E valuation and R eporting

CLEVER: C ross- L ayer E rror V erification E valuation and R eporting. Rafael Kioji Vivas Maeda, Frank Sill Torres Federal University of Minas Gerais (UFMG) School of Engineering Belo Horizonte, Brazil. Focus / Principal idea:

Download Presentation

CLEVER: C ross- L ayer E rror V erification E valuation and R eporting

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CLEVER: Cross-Layer Error Verification Evaluation and Reporting Rafael Kioji Vivas Maeda, Frank Sill Torres Federal University of Minas Gerais (UFMG) School of Engineering Belo Horizonte, Brazil

  2. Focus / Principal idea: System Health Management approach for Embedded Systems / SoCs

  3. Outline • Motivation • Preliminaries • CLEVER • Verification Environment • Conclusion

  4. Motivation System Complexity • Rising complexity of Embedded Systems / Systems-on-Chip (SoC) 7,000 SoC Memory Size 5,000 # Processing Engines / SoC SoC Logic Size 3,000 1,000 2011 2014 2018 2022 2026 ITRS, 2013

  5. Motivation Faults • Due to technology scaling considerable increase of: • Temporary faults • Aging and permanent faults Altera, RELIABILITY REPORT 56, 2013

  6. Preliminaries Reliability • Technique classification • Avoidance(e.g.: Triple ModularRedundancy) • Detection and Recovery (e.g.: Rollback) • Prediction(e.g.: PHM, S.M.A.R.T) • Prognostics and Health Management (PHM) • Runtime monitoring • Remaining Useful Liftetime (RUL) estimation and extension V

  7. Preliminaries Remaining Usefile Lifetime (RUL) Failure Rate λ Time in Operation www.wikipedia.com

  8. CLEVER • Prediction of possible systemfailure important for future SoC • Limitedeffectiveness and efficiency of singlelayer solutions • Straightforward system integration required Origination of Approach • Cross-Layer • Error Verification • Evaluation and • Reporting CLEVER

  9. CLEVER Architecture • Sensors • Sensing Device • Communication • Processing Unit (PU) • Data acquisition • Prediction • Scheduler • Memories • Sensor Bus • System Bus

  10. CLEVER Architecture - Sensor • Two principal parts • Sensing device • Communication with PU • Sensing on differentlevel: • Physical / electrical (Temp., Voltage, …) • Architectural (NBTI, detected faults, …) • System (active time, load, …)

  11. CLEVER Architecture - Processing Unit • Sensor data acquisition • Error Prediction • Arbitration • Interface to Operating System (optional) • Memory access

  12. CLEVER Architecture – OS Integration (optional)

  13. CLEVER Verification Flow • SystemC implementation • Communication based on TLM (Transaction Level Modeling) • Verification based on Message Sequence Chart (MSC)

  14. CLEVER Verification – TLM2MSC

  15. Conclusion • Increasing design complexity and fault probability demand solutions • PHM solutions permit prediction of (probable) system failure • CLEVER: Cross-layer approach for Error Detection and Reporting • System Architecture of CLEVER defined • Verification by simulation of feasibilityof CLEVER architecture • Next steps: • Implementation of prediction algorithm • Test case

  16. Thank you! ART OptMAlab / ART www.asic-reliability.com

More Related