Top Banner
Workshop - November 2011 - Toulouse
20

Plan

Jan 03, 2016

Download

Documents

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 - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Plan

Workshop - November 2011 - Toulouse

Page 2: Plan

PlanSoCKET Process & Overview

Models and Platform Description

Requirements & Traceability with IP-Xact

Conclusion

Workshop - November 2011 2

Page 3: Plan

PlanSoCKET Process & Overview

Models and Platform Description

Requirements & Traceability with IP-Xact

Conclusion

Workshop - November 2011 3

Page 4: Plan

Req

uir

emen

t tr

acea

bili

ty

18/11/2011

Global SoC spec.Global SoC spec.

SoCSoCArchitectureArchitecture

Functional validationFunctional validation

C/C++/ASM

Functionality

System requirementsSystem requirements

Platform assembly

SoftwareSoftware

Metrics

Header generation

SW Performance validationSW Performance validationFunctionality

+timing

Instruction Set Simulator

Metrics

Co-simulation/Co-emulationCo-simulation/Co-emulation

Device executionDevice execution

Socket Design Flow

Page 5: Plan

Needs & Propositions Unambiguous HW IP/Platform requirement captureUnambiguous 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 facilitiesCode generation facilities Parameterizable IP-XACT description generation

Magillem TGI Workshop SystemC\TLM skeleton, netlist, makefile generation

Magillem Template JET Workshop

Requirement TraceabilityRequirement Traceability Use of IP-XACT “vendors extensions” + Generated code propagation

Workshop - November 2011 5

Page 6: Plan

PlanSoCKET Process & Overview

Models and Platform Description

Requirements & Traceability with IP-Xact

Conclusion

Workshop - November 2011 6

Page 7: Plan

Textual Specifications to IP-XACTComponent (IP) architecture description

Interfaces Ports Registers Bitfields Configuration parameters Source files

IP-XACT is not appropriate to describe IP behavioral features

Workshop - November 2011 7

Page 8: Plan

Textual Specifications to IP-XACTPlatform assembly

Components instantiation Interconnections Components configuration

Workshop - November 2011 8

Page 9: Plan

Parameterizable IP-XACT description generationTGI Workshop : Java FilesBus IP-XACT file generation, depends on

number of initiators and targets

Generation configuration

Workshop - November 2011 9

Page 10: Plan

Code generation : SystemC netlist File « top.hpp » generation

Headers component declarations

Components instantiations

TLM2 Sockets connections

Workshop - November 2011 10

Page 11: Plan

Code generation : Platform MakefileTemplate JET Workshop Easier to use than TGI for code generation

Workshop - November 2011 11

Page 12: Plan

Code generation : SystemC/TLM IP skeleton IP-XACT to Synopsys SCML2 Library mapping

Workshop - November 2011 12

Page 13: Plan

PlanSoCKET Process & Overview

Models and Platform Description

Requirements & Traceability with IP-Xact

Conclusion

Workshop - November 2011 13

Page 14: Plan

Traceability: GoalsTo conform certification goals, traceability links between textual

specification, IP-XACT files, and generated files must be demonstrated

Workshop - November 2011 14

Page 15: Plan

Traceability: IP-XACT FilesNo requirement element in

IP-XACT specificationUse of « Vendor Extentions »

with « cover » element

Workshop - November 2011 15

Page 16: Plan

Traceability: Generated codeTraceability links propagation to generated code (comment tag)

Workshop - November 2011 16

Page 17: Plan

Coverage Analysis (IP-XACT = Generated Code)

Traceability: Analysis and matrix generation

Workshop - November 2011 17

Matrix generation

Page 18: Plan

PlanSoCKET Process & Overview

Models and Platform Description

Requirements & Traceability with IP-Xact

Conclusion

Workshop - November 2011 18

Page 19: Plan

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 19

Page 20: Plan

Workshop - November 2011 20

Any Questions ?Any Questions ?