1 / 20

Plan

IP-XACT in the design flow for embedded airborne electronic equipment development Pierre Moreau Hardware Methodology & Certification Electronics Avionics & Simulation Products Department Ludovic Letellier Hardware Methodology On behalf of Alyotech. Plan. SoCKET Process & Overview

whitneya
Download Presentation

Plan

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. IP-XACT in the design flow for embedded airborne electronic equipment developmentPierre MoreauHardware Methodology & CertificationElectronics Avionics & Simulation Products DepartmentLudovic LetellierHardware Methodology On behalf of Alyotech

  2. Plan • SoCKET Process & Overview • Models and Platform Description • Requirements & Traceability with IP-Xact • Conclusion Workshop - November 2011

  3. Plan • SoCKETProcess & Overview • Models and Platform Description • Requirements & Traceability with IP-Xact • Conclusion Workshop - November 2011

  4. Socket Design Flow System requirements System Properties Global SoC spec. Metrics Metrics Trafficgenerators SoCArchitecture HLS Requirement traceability Platform assembly Header generation HW Properties SW Properties IP-XactSoC C/C++/ASM TLMLT Software Functionality Functional validation Instruction Set Simulator Software Functionality+timing TLMAT SW Performance validation Software RTL HLS Co-simulation/Co-emulation Software Silicon Deviceexecution

  5. Needs & Propositions • Unambiguous HW IP/Platform requirement capture • IEEE 1685-2009 IP-XACT Standard • IP description tool support • Magillem IP Packager • Magillem Register View • Platform Assembly & Configuration tool support • Magillem Platform Assembly • Code generation facilities • Parameterizable IP-XACT description generation • Magillem TGI Workshop • SystemC\TLM skeleton, netlist, makefile generation • Magillem Template JET Workshop • Requirement Traceability • Use of IP-XACT “vendors extensions” + Generated code propagation Workshop - November 2011

  6. Plan • SoCKETProcess & Overview • Models and Platform Description • Requirements & Traceability with IP-Xact • Conclusion Workshop - November 2011

  7. Textual Specifications to IP-XACT • Component (IP) architecture description • Interfaces • Ports • Registers • Bitfields • Configuration parameters • Source files • IP-XACT is not appropriate to describe IP behavioral features Workshop - November 2011

  8. Textual Specifications to IP-XACT • Platform assembly • Components instantiation • Interconnections • Components configuration Workshop - November 2011

  9. Parameterizable IP-XACT description generation • TGI Workshop : Java Files • Bus IP-XACT file generation, depends on number of initiators and targets • Generation configuration Workshop - November 2011

  10. Code generation : SystemC netlist • File « top.hpp » generation • Headers component declarations • Components instantiations • TLM2 Sockets connections Workshop - November 2011

  11. Code generation : Platform Makefile • Template JET Workshop • Easier to use than TGI for code generation generation Workshop - November 2011

  12. Code generation : SystemC/TLM IP skeleton • IP-XACT to Synopsys SCML2 Library mapping Workshop - November 2011

  13. Plan • SoCKETProcess & Overview • Models and Platform Description • Requirements & Traceability with IP-Xact • Conclusion Workshop - November 2011

  14. Traceability: Goals • To conform certification goals, traceability links between textual specification, IP-XACT files, and generated files must be demonstrated Workshop - November 2011

  15. Traceability: IP-XACT Files • No requirement element in IP-XACT specification • Use of « Vendor Extentions » with « cover » element Workshop - November 2011

  16. Traceability: Generated code • Traceability links propagation to generated code (comment tag) Workshop - November 2011

  17. Traceability: Analysis and matrix generation • Coverage Analysis (IP-XACT = Generated Code) Matrixgeneration Workshop - November 2011

  18. Plan • SoCKETProcess & Overview • Models and Platform Description • Requirements & Traceability with IP-Xact • Conclusion Workshop - November 2011

  19. Results • IP-XACT Standard • Data perenity needed in avionics domain • Common HW/SW specification formalism • Rich and complete IP/Platform architecture description • Tool vendor independency • Magillem tools • Useful GUI IP-XACT editors (eg: Register Editor) • Very flexible, open tool • Easy code generation with Template Jet Workshop • Perspective • Productivity gain (code generation) • IP-XACT Extension for traceability • Potential bridges others languages, as SysML, SystemVerilog Workshop - November 2011

  20. Any Questions ? Workshop - November 2011

More Related