ASCET V7.1 Release Notes EN - ETAS...ETAS Introduction ASCET V7.1.0 Release Notes Page 4 of 14 1...

ASCET V7.1.0

Release Notes

of 14

Copyright

The data in this document may not be altered or amended without special notification

from ETAS GmbH. ETAS GmbH undertakes no further obligation in relation to this docu-ment. The software described in it can only be used if the customer is in possession of a

general license agreement or single license. Using and copying is only allowed in concur-rence with the specifications stipulated in the contract.

Under no circumstances may any part of this document be copied, reproduced, transmit-

ted, stored in a retrieval system or translated into another language without the express written permission of ETAS GmbH.

© Copyright 2015 ETAS GmbH, Stuttgart

The names and designations used in this document are trademarks or brands belonging

to the respective owners.

ETAS Contents

ASCET V7.1.0 Release Notes of 14

Contents

1 Introduction ............................................................................................................................ 4

1.1 Definitions and Abbreviations ............................................................................................ 4 1.2 Conventions ..................................................................................................................... 4 1.3 User Documentation ......................................................................................................... 4

2 Product Definition .................................................................................................................... 5

2.1 Functions at a glance ....................................................................................................... 5 2.2 General Description .......................................................................................................... 5 2.2.1 Safety Advice ............................................................................................................... 5 2.2.2 Your Safety Obligations ................................................................................................ 5 2.2.3 System Prerequisites .................................................................................................... 6 2.2.4 Software Prerequisites .................................................................................................. 6 2.2.5 Release Test Configuration ........................................................................................... 6 2.3 Delivery ........................................................................................................................... 7 2.3.1 Used 3rd Party Software ............................................................................................... 8 2.4 Installation ...................................................................................................................... 8

3 Changes ................................................................................................................................. 9

3.1 What’s New ..................................................................................................................... 9 3.2 Compatibility to Earlier Releases ...................................................................................... 10 3.2.1 Unsupported use-cases .............................................................................................. 10 3.3 Fixed Problems .............................................................................................................. 11 3.4 Known Issue Reports ...................................................................................................... 11 3.5 Known Issues ................................................................................................................ 12

4 Contact, Support and Problem Reporting ................................................................................ 14

ETAS Introduction


1 Introduction

1.1 Definitions and Abbreviations

EHI

ETAS Help Desk International

HW

Hardware

KIR

Known Issue Report – For severe Problem Reports which occur after a release, ETAS has introduced the Known Issue Report to inform affected customer immediately. The current Known Issues of former versions can be found on the ETAS website: http://www.etas.com/kir

PR

Problem Report

SW

Software

1.2 Conventions

The following typographical conventions are used in this document:

OCI_CANTxMessage msg0 = Code snippets are presented on a gray background and in the Courier font.

Meaning and usage of each command are explained by means of comments. The comments are enclosed by the

usual syntax for comments.

Choose File Open. Menu commands are shown in boldface.

Click OK. Buttons are shown in boldface.

Press <ENTER>. Keyboard commands are shown in angled brackets.

The "Open File" dialog box is displayed.

Names of program windows, dialog boxes, fields, etc. are shown in quotation marks.

Select the file setup.exe Text in drop-down lists on the screen, program code, as well as path- and file names are shown in the Courier font.

A distribution is always a one-

dimensional table of sample points.

General emphasis and new terms are set in italics.

1.3 User Documentation

The ASCET V7.1 Getting Started guide in PDF format can be found on the DVD.

All other user documentation is provided as online help. The online help is:

Linked from the ASCET Welcome page that is shown the first time you use the

product

Available at any time from the Help Help Contents menu.

http://www.etas.com/kir

ETAS Product Definition


2 Product Definition

2.1 Functions at a glance

ASCET is an object-oriented model-based software development tool that is designed to help you build real-time, high-performance, low-overhead, ultra-portable, safe and secure

software for deeply embedded hardware.

ASCET supports multi-paradigm modelling, allowing models in both graphical and textual notation to co-exist. The graphical modelling language is called “Block Diagram Expression”

(or BDE for short) and the textual modelling language is called “Embedded Software

Development Language”, or “ESDL” for short. Both notations allow you to work at the right level of detail for your problem, and make it easy to find classes of error that can be hard to

detect by traditional software development approaches.

ASCET provides:

an Eclipse-based rich text editor tooling that makes developing and understanding

BDE models and ESDL code quick and easy

a code generator that translates models into production ready, MISRA-C:2004

compliant code that is free from insecurities, vulnerabilities and portability problems.

a bridge to the ETAS Experiment Environment that allows you to test the

functionality of your models by connecting model inputs to signal generators and

observe model outputs.

2.2 General Description

2.2.1 Safety Advice

Safety advice for this ETAS product is available in the following formats:

A printed document shipped with the DVD media.

In electronic form on the DVD. See Documentation\ASCET Safety

Advice.pdf for details.

As a modal dialog displayed by ASCET when a new workspace is opened.

As a dialog accessible from the IDE menu under Help Safety Advice.

2.2.2 Your Safety Obligations

You are a recognized expert in the design and implementation of software-intensive safety-

related systems. You have detailed knowledge about the failure modes of the system you are constructing and will have been the author or technical reviewer of the system safety

case as it relates to aspects of the systems realized in software.

In particular, you know which safety requirements rely on the correct functioning of code generated by ASCET. This establishes the context in which the use of ASCET generated code

is relevant to overall system safety.

You are familiar with:

embedded programming in the C language;

tasks in the software engineering process and the use of tools to assist with those

tasks;

ISO26262:2011, IEC61508:2010 or a similar standard (e.g. EN50128) as it applies to

your domain.

It is your responsibility to ensure that any code generated by ASCET meets the requirements of any regulatory regime and national or international laws with which your development

process must comply.

If you require help or further guidance on the use of ASCET generated code in safety-related applications please contact ETAS.



2.2.3 System Prerequisites

The following minimum system prerequisites must be met:

Required Hardware 1,5 GHz PC

1 GB RAM

DVD-ROM drive

Network adapter

Graphics with a resolution of at least 1024 x 768, 32 MB RAM 16Bit color and DirectX 7

Required Operating System Windows® 7 (x86_64)

Required Free Disk Space 1.5 GB (not including the size for application data)

Required Software .NET Framework 4.5.2 (or later)

The following system prerequisites are recommended:

Recommended Hardware 2,0 GHz Dual-Core PC or equivalent

4 GB RAM

DVD-ROM drive

Network adapter

Graphics with a resolution of 1650 x 1080, 128 MB RAM 32 Bit color and DirectX 7 or higher and hardware acceleration

Recommended Operating System

Windows® 7 (x86_64)

Recommended Free Disk Space 1.5 GB (not including the size for application data)

Required Software .NET Framework 4.5.2 (or later)

2.2.4 Software Prerequisites

The following minimum software prerequisites have to be met:

Administrator rights are required to install the ETAS License Manager (LiMa)

Use of ASCET’s PC Experiment bridge requires installation of the following ETAS

tools:

o ETAS Experiment Environment V3.5.0 or later

ETAS Experiment Environment V3.6.1 is shipped with the installation

media.

ASCET examples that include an experiment configuration have been built using ETAS Experiment Environment V3.6.1 and may not

run with other versions of the ETAS Experiment Environment.

o (Optionally for XCP-based experiment interaction) ETAS INCA-EIP V7.1.0

Important: Both the ETAS Experiment Environment and ETAS INCA-EIP are not compatible with Windows® 10.

2.2.5 Release Test Configuration

This release of ASCET has been tested on the following host systems:



Windows 7 (x86_64 / 64-bit)

Windows 8.1 (x86_64 / 64-bit)

Windows 10 (x86_64 / 64-bit)

This release of ASCET has been integration tested with the following additional software:

MinGW GCC V4.8.1 (x86 / 32-bit)

ETAS Experiment Environment V3.6.1

ETAS INCA-EIP V7.1.0

Compatibility of release test configurations and Windows versions is shown in the following

table:

Tool Windows 7

x86_64

Windows 8.1

x86_64

Windows 10

x86_64

ETAS ASCET 7.1 ETAS Experiment Environment V3.6.1 ETAS INCA-EIP V7.1.0 MinGW GCC V4.8.1 (x86 / 32-bit)

2.3 File Format Compatibility

ASCET is compatible with the file format versions.

File Format Compatible Versions

AUTOSAR ARXML R4.0.3, R4.1.2 & R4.2.1 ASAM MCD-2 MC (ASAP2, A2L) V1.5 ASAM MDF V3.01 ETAS DCM V1.11, V2.01

2.4 Delivery

The software is delivered with an installation routine on a DVD including ASCET software, documentation, tools, utilities, and further information. All software documentation is

available in the Portable Document Format (PDF), which requires Adobe® Reader®.

The DVD contains the following items:

File or Directory Description

Autostart.exe The executable for starting the ETAS Product Installation program.

AUTORUN.INF Windows Auto-run configuration file.

Start.exe The ETAS Product Installation program.

Start.ico The ASCET icon.

\install Directory containing the software installers programs.

\Documentation Directory containing copies of the PDF user

documentation.

1 Using the ETAS Experiment Environment.



\Documentation\Open Source

Software Directory containing information about 3rd party open

source software used in or provided for use with ASCET.

\HTML Directory containing text and images for the DVD .

2.4.1 Used 3rd Party Software

ASCET makes use of third-party software components. Licensing information for these

components can be found in:

Documentation\ ASCET V7.1.0 OSS Attributions (Eclipse Platform

Components).pdf.

Documentation\ ASCET V7.1.0 OSS Attributions (Plugins -

com.etas).pdf.

2.5 Installation

Run Start.exe from the DVD follow the on-screen instructions to install ASCET.

Additional information on how to properly install and configure the product is in the ASCET

V7.1 Getting Started guide can be found in

Documentation\ASCET V7.1 Getting Started.pdf.

ETAS Changes


3 Changes

3.1 What’s New

ASCET V7.1 is the second preview release on the ASCET V7.x product line. ASCET V7.1 is

released to enable ETAS to gather user feedback only and is not intended for use in the development of series production software.

The following ASCET use-cases are supported:

Modelling with ASCET block diagrams

Modelling with ASCET’s ESDL textual modelling notation

ANSI-C code generation from block diagrams and ESDL models.

Import of AUTOSAR software component descriptions

PC experiments, with runtime interaction and visualization using

o ETAS Experiment Environment

o ETAS INCA-EIP Experimental Target Integration Package.

Packaging of an ASCET physical model as an FMU

Key new features are:

Graphical modeling

o Elements: Maps & curves (normal, fixed & group), structs (scalar fields

only), use of public elements

o Operators: mux, switch, type cast

o Comments: free-floating, per element definition, per element instance

o Custom blocks: containers with breadcrumb navigation and support for

multiple input/output pins

o Structure: public & private method definition

o Cut/copy/paste

o Multiple diagrams per class

Usability improvements

o Sorting in the outline view

o Tabular editor for variant initializers

ESDL modeling

o Calibration support: Virtual variables & dependent parameters

o Composite elements: Unconstrained array types; arrays sized by system

constants

o Type conversions

o Improved syntax for type declarations

o State machines

Multi-trigger, hierarchical states, access to current state

o Public elements

Code generation

o Use of internal ASCET 6.3 code generation engine

o Optional use of legacy (pre-installed) ASCET 6.1.4 or 6.3.0 code generator

installation

ETAS Changes


Simulation

o PC Experiment: Static class experiments; Full project experiments

o Support for FMU (Functional Mock-up Unit) generation

Model import & conversion

o Import of AUTOSAR R4.0.3, R4.1.2 and R4.2.1 software component models

o Limited conversion of ASCET 6.3 models to ASCET 7.1

Miscellaneous

o Updated to 64-bit Java and 64-bit Eclipse V4.3 (Luna)

o Numerous bug fixes and performance improvements

3.2 Compatibility to Earlier Releases

This release of ASCET is not backwards compatible with earlier versions of ASCET.

ASCET 7.0 models cannot be used with ASCET 7.1.

ASCET 6.3 models can be converted to work with ASCET 7.1. A prototype

conversion toll is supplied that has at least the following limitations regarding conversion:

o No state machines

o No variant/variable arrays/matrices

o No records

3.3 Unsupported use-cases

ASCET V7.1 does not support all ASCET 6.x use-cases.

The following use-cases are not supported in this release:

ASCET-RP: Interaction with ETAS Rapid Prototyping hardware (ES910 etc.).

ASCET-DIFF: Graphical version comparison.

ASCET-SE EHOOKS Target: Development of on-target bypass functions for ETAS

EHOOKS using ASCET

The following use-cases of ASCET are deprecated. They are not supported in the release and ETAS has no plans to support them in future releases:

ASCET-MD: CT modelling blocks for continuous time simulation.

ASCET-SE: Integration platform use-cases (configuration and build of an ECU

executable)

Note that customized add-ons that were developed for earlier versions of ASCET are not

compatible with this release of ASCET.

ETAS Changes


3.4 Fixed Problems

The following problems in ASCET 7.0 have been fixed in this release:

EHI Bug ID Description

396637 ASCET does not work on Windows 8

408214 C code for classes is not generated when running a second instance of the product.

429922 Generated C code does not compile when a shared axis is declared with

modifier "public"

431374 Code generation server is not terminated if two instances of ASCET7

started and both are terminated

433281 PC Experiment harness created in wrong project if 2 projects contain ESDL file with same name

433813 Failure to generate valid .experiment file after project has been deleted

and is then re-created

436775 Using characters !@#$%^& in file names causes an exception

438563 Cannot rename a file after renaming it with a training space in the

filename

438885 Static distributions defined in other classes are not supported for PC

experiments

439048 Cannot cut/copy/paste a message from a referenced project

439237 Cannot use a representation clause for a struct with a unit-based field

439276 Generated C code does not link when argument and return of a map of

curve in a static class are defined in a representation clause

439714 Stack overflow when type definition and its representation have a cyclic dependency

439770 The sequencing view is blank after closing, deleting methods and open it

again

439960 Messages appear as variables on the canvas

3.5 Known Issue Reports

If a product issue develops, ETAS will prepare a Known Issue Report (KIR) and post it on the internet. The report includes information regarding the technical impact and status of

the solution. Therefore you must check the KIR applicable to this ETAS product version and follow the relevant instructions prior to operation of the product.

The Known Issue Report (KIR) can be found here:



ETAS Changes


3.6 Known Issues

This section describes the set of known problems in ASCET V7.1.0:


453346 Code generation fails when using unary minus on a real characteristic

inside the abs() intrinsic function.

EXAMPLE:

characteristic real charRealFirstVal = 0.5;

…

if (0.5 == abs(-charRealFirstVal)) {…} // This form of expression

results in a code generation failure

WORKAROUND: Modify the model to remove the unary minus. There is

typically no need to say abs(-MyInteger) as the negation will be removed

by use of abs() .

476316 Curves & maps marked @equidistant are not supported for PC

experiments.

WORKAROUND: Remove (or comment out) the @equidistant

annotation. The maps/curve will be generated as normal maps and

curves. This has identical functionality to earlier ASCET versions as “fixed” maps and curves are generated as “normal” maps and curves for PC

experiments.

477555 Automatically created test harness classes are added to newly created PC experiments.

WORKAROUND: Delete the generated *_test.[hc] files that contain

the experiment wrapper ESDL before re-creating the PC experiment.

491244 OutOfMemory exception when using hundreds of BD editors.

WORKAROUND: None.

496076 NullPointerException when creating a public static element in new BD specification and then saving the model.

WORKAROUND: Public static elements are essentially global data. Global elements are modelled in ASCET 7 using unprotected data

interfaces:

data interface Globals

{

@unprotected

integer GlobalVariable = 42;

}

ETAS Changes



500750 Generating C code fails when assigning the result of an unconstrained

array access using the maximum index value to an out argument of

integer type.

EXAMPLE:

type UnArrType is array[] of integer;

class Bugcmm

{

UnArrType unArr[0 .. 1];

public integer getII( integer out i, UnArrType in arr)

{

i = unArr[last(indextype(arr))];

return i;

}

}

WORKAROUND: None.

502970 Installation fails on Windows 7 x86_64 if .Net 4.5.x is not installed

.Net 4.5.x is not provided with Windows 7 x86_64 or SP1. If you do not have an up-to-date Windows 7 installation, then this is detected during

the ASCET installation and you will be prompted to download .Net. The

download however fails.

WORKAROUND: Install .Net 4.5.x manually before installing ASCET.

See: https://www.microsoft.com/en-US/download/details.aspx?id=30653

This section describes the set of known problems in the ETAS Experiment Environment

V3.6.1:


484279 The signal generator in the ETAS Experiment Environment does not

support data interface element of enumeration type

ETAS Contact, Support and Problem Reporting


4 Contact, Support and Problem Reporting

For details of your local sales office as well as your local technical support team and product hotlines, take a look at the ETAS website:

ETAS subsidiaries WWW: www.etas.com/en/contact.php

ETAS technical support WWW: www.etas.com/en/hotlines.php

http://www.etas.com/en/contact.php

http://www.etas.com/en/hotlines.php

ASCET V7.1 Release Notes EN - ETAS...ETAS Introduction ASCET V7.1.0 Release Notes Page 4 of 14 1...

Documents

Transcript of ASCET V7.1 Release Notes EN - ETAS...ETAS Introduction ASCET V7.1.0 Release Notes Page 4 of 14 1...