1 / 28

C. André, J. Boucaron, A. Coadou, J. DeAntoni , B. Ferrero, F. Mallet, R. de Simone

MARTE/CCSL, TimeSquare & K-Passa A design platform using MoCCs for embedded model-based engineering. C. André, J. Boucaron, A. Coadou, J. DeAntoni , B. Ferrero, F. Mallet, R. de Simone AOSTE Project INRIA/I3S Sophia Antipolis, France. Context.

damisi
Download Presentation

C. André, J. Boucaron, A. Coadou, J. DeAntoni , B. Ferrero, F. Mallet, R. de Simone

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. MARTE/CCSL,TimeSquare & K-PassaA design platform using MoCCs for embedded model-based engineering C. André, J. Boucaron, A. Coadou, J. DeAntoni, B. Ferrero, F. Mallet, R. de Simone AOSTE Project INRIA/I3S Sophia Antipolis, France

  2. Context • Modeling environments for real-timeembedded and distributed systems

  3. Context • Modeling environments for real-timeembedded and distributed systems • Conceptual diagrammatic representations • Structural • Components / interactions • Dynamics/Behavior

  4. Context • Modeling environments for real-timeembedded and distributed systems • Conceptual diagrammatic representations • Structural • Components / interactions • Dynamics/Behavior of individual components • State-based control flow • Activity-based data flow • Constrained programs with “same” expressivity

  5. Context • Modeling environments for real-timeembedded and distributed systems • Conceptual diagrammatic representations • Structural • Components / interactions • Dynamics/Behavior of individual components • State-based control flow • Activity-based data flow • Constrained programs with “same” expressivity • Dynamics/Behavior of system • results from combining component behaviors according to structure

  6. Example of architecture modeling Structure Behavior

  7. Example of architecture modeling Structure Behavior

  8. Example of architecture modeling Structure Elaboration phase (SystemC) Behavior Simulation

  9. Traditional component approach • Structure • Black-box + Interfaces (Ports, Data Types) • Behavioral abstraction • Messages + possibly period and performance requirements • What we find missing: • Detailed definition of timing and synchronization properties • Communication protocol requirements • This missing information is often deported elsewhere

  10. Traditional component approach • Structure • Black-box + Interfaces (Ports, Data Types) • Behavioral abstraction • Messages + possibly period and performance requirements • What we find missing: • Detailed definition of timing and synchronization properties • Communication protocol requirements • This missing information is often deported elsewhere

  11. Logical functional time Functional: sequence of reaction steps Multiple times (local / global) Synchronization primitives → constraints between local activation times Synthesis / Compilation Process networks (SDF), synchronous reactive formalisms, statecharts “physical” time Extra functional Single time (total order) Timing constraints to be satisfied at execution Simulation semantics possibly different from synthesis UML, SystemC Time & Semantics

  12. Logical functional time Functional: sequence of reaction steps Multiple times (local / global) Synchronization primitives → constraints between local activation times Synthesis / Compilation Process networks (SDF), synchronous reactive formalisms, statecharts “physical” time Extra functional Single time (total order) Timing constraints to be satisfied at execution Simulation semantics possibly different from synthesis UML, SystemC Time & Semantics HDLs

  13. Logical functional time Functional: sequence of reaction steps Multiple times (local / global) Synchronization primitives → constraints between local activation times Synthesis / Compilation Process networks (SDF), synchronous reactive formalisms, statecharts “physical” time Extra functional Single time (total order) Timing constraints to be satisfied at execution Simulation semantics possibly different from synthesis UML, SystemC Semantics Our choice

  14. MARTE: Time model and CCSL MARTE = Modeling and Analysis of Real-Time and Embedded systems • OMGUML profile (adopted June 2009) • Time subprofile (defined by us) • Rich but well-defined variety of time notions (logical/physical, discrete/dense, …) • Clockscan be explicitly attached to most UML model elements → timed semantics • Clock ConstraintSpecification Language (CCSL) • Various constraints on clocks (synchronous, asynchronous, mixed) • Precise formal semantics

  15. Why CCSL? • Polychronous system modeling • Specification of sophisticated synchronizations • Notation to describe semantic relations between timed behaviors (illustrated below) • Means to define formally timedModels of Computations and Communications (MoCCs) • Akin to Tagged Systems(Lee & Sangiovanni-Vincentelli)

  16. Why CCSL? • Means to define formally timedModels of Computations and Communications (MoCCs) • In the sequel, we translate a MoCC as UML models + CCSL specifications • The chosen MoCC is SDF (weighted event graphs) models

  17. incoming src dest Synchronous DataFlow SDF Meta-model • Nodes are called actors • Input/Output have a weight (Number of data samples consumed/produced) • Arcs have a delay

  18. Synchronous DataFlow • Actor enabling = each incoming arc carries at least weight tokens • Actor execution = atomic consumption/production of tokens by an enabled actor • i.e., consume weight tokens on each incoming arcs and produce weight tokens on each outgoing arc • Delay is an initial token load on an arc. SDF firing rules: How can CCSL express this semantics?

  19. SDF Example Evolutions of the model A A B A A B Static schedule: C C

  20. How to model SDF graphs in UML ? Is that compatible with the UML semantics ? CCSL makes the semantics explicit … … within the model

  21. SDF Actor A Token T Input i Output o CCSL Clock A; Clock write, read; Var delay:int; Var weight:int; Var weight:int; SDF semantics with CCSL (1/2)

  22. SDF semantics with CCSL (2/2) • SDF • CCSL

  23. Example

  24. TimeSquare

  25. AOSTE’s Tools • TimeSquare • Software environment dedicated to the • Specification of CCSL constraints • Resolution of CCSL constraints • Simulation and generation of trace model • Animation of UML models • Exploration of augmented timing diagrams • K-Passa • Computation of static schedules for specific MoCCs • Marked Graphs, Synchronous DataFlow, Latency-Insensitive Designs, K-periodical Routed Graphs • Analysis (deadlock freeness, safety) • Optimization (latency, throughput, interconnect buffer size) • Code generation (stand-alone simulator)

  26. K-Passa

  27. Tool download • http://www-sop.inria.fr/aoste/

  28. Thank you All

More Related