AADL committee, Valencia October 2 nd, Pierre Dissaux (Ellidiss) Maxime Perrotin (ESA)

Transcription

1 AADL committee, Valencia October 2 nd, 2014 Pierre Dissaux (Ellidiss) Maxime Perrotin (ESA)

2 what is TASTE? A tool-chain targeting heterogeneous, embedded systems, using a model-centric development approach A laboratory platform for experimenting new softwarerelated technologies, based on free, open-source solutions A process supporting the creation of systems using formal models and automatic code generation An outcome of the European research project ASSERT

3 Main contributors ESA (European Space Agency): Project lead and funding, development: PolyORB-HI-C, Vertical transformation, code generators, OpenGEODE, MSC Editor, Auto-generated GUIs ISAE (Institut Supérieur de l'aéronautique et de l'espace): Ocarina, PolyORB-HI-Ada, RTEMS, PolyORB-HI-C, AADL UPM (Universidad Politécnica de Madrid): Ada runtime (gnatforleon), TASTE MSC Editor, TASTE GUI for Windows Neuropublic: ASN.1 compiler, Data Modeling Toolchain, VHDL support, Orchestrator, MSC2Python, SMP2, SQL Support Pragmadev: Free SDL Editor Ellidiss Technologies: Frame contract management, Interface View, Deployment View and Concurrency View editors, SMP2, AADL

4 Main targets and philosophy Use DSL : select the most appropriate language to solve a given problem But do not reinvent the wheel : use existing languages and tools Mature languages with long-term support Interoperable tools, limiting vendor lock-in Not all languages however We target safe systems

5 Supported technologies ASN.1 VHDL AADL CHEDDAR SQL SDL Modeling SIMULINK SCADE Ada Code generation & deployment Model analysis MAST PolyORB/HI SMP2 Win32 Execution platform RTEMS C/C++ Xenomai Linux MSC Debugging & testing Python

6 Quick overview

7 Status at a glance Mature tools with commercial support AADL to Ada and C compilers ASN.1 compiler (Ada and C) and tools SDL editor with Ada code generator DSL graphical editors with AADL as a pivot language Maturing tools (prototype-level) GUI & Testing Framework Model verification tools (Cheddar, Mast, Model Checker) Hardware-Software co-engineering package Support for SMP2

8 Distribution Bundled in a virtual machine full Debian Linux installation, with all dependencies installed: Update mechanism triggered from the desktop Manual installation is possible (instructions on the Wiki) Ask for help. Documentation and reference card on the desktop Print the reference card! Linux-based, but a Windows GUI prototype exists

9 Target : reactive and discrete systems Communication : Message exchanges between the system and its environment Asynchronous and synchronous interactions Algorithms, GUIs Databases Wide range of applications Safety and mission-critical communicating systems Real-time applications (embedded systems) Wide range of architectures X86 (Linux, Win32, Xenomai, FreeBSD), SPARC (Leon), ARM 32 and 64 bits

10 Process Describe the system logical architecture and interfaces with ASN.1 and AADL Generate code skeletons and write (or reuse) the applicative code or models Capture the system hardware and deployment Verify models Build the system and download it on target Monitor and interact with the system at run-time

11 Workflow SDL editor Monitoring and Testing toolbox Procedural Code (SDL, Ada, C, ) Application Data types (ASN.1) ASN.1 toolbox Data type Encoders/Decoders Ocarina Data View (AADL) Interface View (AADL) Deployment View (AADL) Concurrency View (AADL) Interface View editor Deployment View editor Vertical Transformation Concurrency View editor HW library (AADL)

12 Data View: ASN.1 International, widely used standard (ISO and ITU-T) Simple text notation for precise and complete data type description Real added value : the physical encoding rules (compact binary encoding, endianness-neutral, but also XML encoding, legacy encoding specifications). Separate the encoding rules from the types specification Can be translated into standard textual AADL (Data components)

13 ASN.1 basic types INTEGER My-int ::= INTEGER (0..7) value My-int ::= 5 REAL My-real ::= REAL ( ) BOOLEAN ENUMERATED My-enum ::= ENUMERATED { hello, world } OCTET STRING My-string ::= OCTET STRING (SIZE (0..255)) value My-string::= 'DEADBEEF'H BIT STRING My-bitstring ::= BIT STRING (SIZE (10..12)) value My-bitstring ::= ' 'B

14 ASN.1 complex types SEQUENCE My-seq ::= SEQUENCE { x My-int, y My-enum OPTIONAL } value My-seq::= { x 5 } CHOICE My-choice ::= CHOICE { choicea My-real, choiceb My-bitstring } value My-choice ::= choicea : 42.0 SEQUENCE OF My-seq ::= SEQUENCE (SIZE (0..5)) OF BOOLEAN value My-seq:= { 1, 2,3 } SET / SET OF

15 Interface View (IV) A DSL for describing the system in terms of interconnected applicative functions An IV model must reference a Data View Functions have interfaces Provided Interfaces (PI) Required Interfaces (RI) RIs can be connected to PIs by client-server communications (subprogram calls) Interfaces have a real-time behavior that is compatible with the Ravenscar execution model IV models are serialized in standard textual AADL

16 Provided Interfaces (PI) A provided interface (PI) is a service offered by a function. It can be Periodic, in which case it does not take any parameter, and is used to handle cyclic tasks Sporadic (or asynchronous) and optionally carry a parameter. The actual execution time is decided by the real-time scheduler (call is deffered) Synchronous, with or without protection and optionally carry parameters (in and out) The protection is a semaphore (in C) or a protected object (in Ada) preventing concurrent execution of several interfaces of the same function. Use unprotected interface to implement e.g. «getter» functions Caller blocks on execution (call is immediate) Just like a direct function call. At runtime, synchronous functions execute in the caller's thread space. PIs have parameters, instance of items of the Data View PIs share the local state variables of the function (context parameter). Context parameters are also instances of items of the Data View. PIs are associated to an operation (subprogram) whose code must be provided in Ada or C, or generated from a modeling language (Scade, Simulink, SDL)

17 Deployment View (DV) Describes the hardware architecture of the execution platform. A DV model must reference an IV model and an HW library. Instantiates predefined HW components provided by libraries of processors, buses and devices. Can be used to allocate functions on processors and connections to buses DV models are serialized in standard textual AADL

18 Concurrency View (CV) The CV model is the result of a model transformation (called Vertical Transformation) taking as input a DV and referenced HW library, IV model and Data View. The CV model contains all the required information for doing: Scheduling analysis (Cheddar) Code generation and application build (Ocarina) A CV model is serialized in standard textual AADL

19 AADL subset Data View Data Type: AADL Data Component Interface View Container: AADL Package Function: AADL System Provided Interface: AADL Subprogram + Provides Subprogram Access Required Interface: AADL Requires Subprogram Access Context Parameter: AADL Data Subcomponent Deployment View Processor: AADL Processor Partition: AADL Process Bus: AADL Bus Driver: AADL Device Concurrency View Complete System Instance with AADL Threads

20 IV, DV and CV editors Graphical Editors are developed on top of the GMP framework (Tcl/Tk) AADL parsing and model transformations are using the LMP toolbox (prolog) The Taste-CV editor is a customization of AADL Inspector These editors are developed and maintained by Ellidiss GMP/LMP has become a generic solution for other AADL based DSL tools: Define the DSL meta-model (should be an input) Define the semantic mapping with AADL Produce a graphical editor compliant with the DSL (GMP) Produce the save/load transformations to/from AADL (LMP)

21 Taste-IV editor

22 Taste-DV editor

23 Monitoring tools

24 MSC comparison: regression testing MSC scenarii can be translated into Python scripts to write full-featured test suites Testing tools

25 Demo