ASCET V6.4.

3
Release Notes
 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 2017 ETAS GmbH, Stuttgart
The names and designations used in this document are trademarks or brands belonging
to the respective owners.
ASCET V6.4.3 Release Notes R01 EN – 7 December 2017

2
ETAS Introduction

Contents
1 Introduction ............................................................................................................................4
1.1 Definitions and Abbreviations ............................................................................................4
1.2 References ......................................................................................................................4
1.3 Conventions .....................................................................................................................5
1.4 User Documentation .........................................................................................................5
2 Product Definition....................................................................................................................6
2.1 Functions at a glance .......................................................................................................6
2.2 General Description ..........................................................................................................6
2.2.1 Safety Notice ...............................................................................................................6
2.2.2 System Prerequisites ....................................................................................................6
2.2.3 Software Prerequisites ..................................................................................................7
2.2.4 Access Rights...............................................................................................................7
2.3 Release Test Configuration ...............................................................................................9
2.4 Delivery ...........................................................................................................................9
2.4.1 Used 3rd Party Software ............................................................................................. 10
2.5 Installation .................................................................................................................... 10
2.6 Licensing ....................................................................................................................... 10
3 Changes ............................................................................................................................... 12
3.1 What’s New ................................................................................................................... 12
3.2 Compatibility to Earlier Releases...................................................................................... 12
3.3 Fixed Problems .............................................................................................................. 13
3.4 Known Issue Reports ...................................................................................................... 14
3.5 Known Issues ................................................................................................................ 14
4 Hints .................................................................................................................................... 16
4.1 Release Notes ................................................................................................................ 16
4.2 Non ANSI-C compliant identifier in older ASCET versions .................................................. 16
4.3 XML Workspace and Export/Import ................................................................................. 16
4.4 Use of Microsoft Visual Studio C++ Compiler V6.0 ........................................................... 16
4.5 Double Byte Characters are not supported ....................................................................... 17
4.6 Long compilation times with Visual Studio Compiler under Windows 8 x86_64 ................... 17
4.7 Removal of Borland V4.5 for PC experiments ................................................................... 17
4.8 Advanced Information .................................................................................................... 17
5 ETAS Contact Addresses ........................................................................................................ 19

ASCET V6.4.3 Release Notes 3

ETAS Introduction

1 Introduction

1.1 Definitions and Abbreviations

Term/Abbreviation Definition
ASCET-DIFF ASCET Difference Browser.
Code Generation Code generation is the first step in the transformation of a
physical model to executable code. The physical model is
transformed into ANSI C code. Since the C code is compiler
(and therefore target) dependent, different code for each
target is produced.
EHI ETAS Help Desk International
File extension ASCET model description, XML based description format of
*.amd ASCET models
File extension Archived XML for ASCET
*.axl
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
Target The hardware a program or an experiment runs on, e.g.
MPC55xx, TriCore, SH2
WB Walkback: ASCET system error

1.2 References
[ASW_GS_EN]
ASCET V6.4 Getting Started
[ASW_INST_EN]
ASCET V6.4 Installation Guide
[ASW_ADMIN_EN]
ASCET V6.4 Administration Guide
[ASW_AR_UG_EN]
ASCET V6.4 AUTOSAR User’s Guide
[ASW_ARCONV_UG_EN]
ASCET V6.4 AUTOSAR to ASCET Converter User’s Guide
[ASW_ICON_REF_EN]
ASCET V6.4 Icon Reference Guide
[ASW_RP_UG_EN]
ASCET-RP V6.4 User’s Guide
[ASW_RPOSMON_UG_EN]
ASCET-RP V6.4 OS Monitor User’s Guide

ASCET V6.4.3 Release Notes 4

ETAS Introduction

[ASW_SE_UG_EN]
ASCET-SE V6.4 User’s Guide
[ASW_DIFF_INST_EN]
ASCET-DIFF V6.4 Installation Guide
[ASW_SCM_UG_EN]
ASCET-SCM V6.4 User’s Guide

1.3 Conventions

The following typographical conventions are used in this document:

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 Consolas font.
A distribution is always a one-dimensional General emphasis and new terms are set in italics.
table of sample points.

1.4 User Documentation

The set of ASCET manuals (see Section 1.2) can be found on the DVD installation medium.

ASCET V6.4.3 Release Notes 5

ETAS Product Definition

2 Product Definition

2.1 Functions at a glance

ASCET is a development environment that enables the specification and implementation of

control algorithms for embedded systems. ASCET V6.4 forms the core installation and must
be installed first.
The products ASCET-MD (Modeling & Design), ASCET-MDV (Model Viewer), ASCET-RP
(Rapid Prototyping) and ASCET-SE (Software Engineering) for various micro controller
targets can be installed on it independently.
Together with the add-on products ASCET-SCM (Software Configuration Management) and
ASCET-DIFF (Difference Browsing), ASCET forms a complete software development tool-
chain.

2.2 General Description

2.2.1 Safety Notice

If ASCET is used to generate code for safety-related applications, the following assumptions
are made on, and must be validated for, all users:
• You are a trained software engineer who wants to use the ASCET model-based
development approach to generate C code for use in a safety-related system.
• 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.
Further information about the use of ASCET in safety-related applications is available in the
following documents that are available on request from ETAS:
• ASCET V6.4 Safety Manual
• ASCET V6.4. MISRA-C:2012 Compliance Guide
2.2.2 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

Supported Operating Windows® 10 x86_64

Systems Windows® 8.1 x86_64
Windows® 8 x86_64
Windows® 7 x86_64 & x86

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

Required Software Microsoft® .NET Framework 3.5

Microsoft® .NET Framework 4.6.2 or later
Microsoft® Visual C++ Redistributable Package 2010

ASCET V6.4.3 Release Notes 6

ETAS Product Definition

SP1
Microsoft® Visual C++ Redistributable Package 2015
SP2

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 1280 x 1024, 128 MB RAM
32 Bit color and DirectX 7 or higher and hardware
acceleration

Recommended Operating Windows® 7 x86_64

System

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

Required Software Microsoft® .NET Framework 3.5

Microsoft® .NET Framework 4.6.2 or later
Microsoft® Visual C++ Redistributable Package 2010
SP1
Microsoft® Visual C++ Redistributable Package 2015
SP2

2.2.3 Software Prerequisites

You ensure that your PC has the following Microsoft® redistributables installed before
installing ASCET:
 Microsoft® .NET Framework 4.6.2 or later
 Microsoft® Visual C++ Redistributable Package 2010 SP1
 Microsoft® Visual C++ Redistributable Package 2015 SP2
ASCET V6.4 cannot be used without installing at least one of the product executables:
 ASCET-MD V6.4
 ASCET-MDV V6.4
 ASCET-RP V6.4
 ASCET-SE V6.4 for a microcontroller target.
Any combination of these products can be installed once ASCET V6.4 is present. For details
see the ASCET Installation manual.
ASCET uses XML technology for code preview and code documentation. Please see the
“Hints” section for details on the required software installation.
2.2.4 Access Rights

Users must have the following access rights to install and use ASCET.

Administrator rights
Administrator rights are:
 Mandatory for installation.

ASCET V6.4.3 Release Notes 7

ETAS Product Definition

 Optional for normal operation.

Registry access
ASCET places data in the Windows registry and requires read/write access to the following
locations:
 HKEY_LOCAL_MACHINE\Software\ETAS
 HKEY_LOCAL_MACHINE\Software\WOW6432Node\ETAS
 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{A19A0268-
9053-4ae8-BE50-C807A11245E2}
 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\AppID\{A19A0268-
9053-4ae8-BE50-C807A11245E2}
 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ETAS
 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ETAS\ASCET
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
 HKEY_CLASSES_ROOT\Ascet.Ascet
 HKEY_CLASSES_ROOT\Ascet.Ascet.6
 HKEY_CLASSES_ROOT\Ascet.Ascet.6.4
 HKEY_CLASSES_ROOT\Ascet.Ascet.6.4.3
 HKEY_CLASSES_ROOT\CLSID\{A19A0268-9053-4ae8-BE50-C807A11245E2}
 HKEY_CLASSES_ROOT\AscetServer.AscetServer
 HKEY_CLASSES_ROOT\AscetServer.AscetServer.6
 HKEY_CLASSES_ROOT\AscetServer.AscetServer.6.4
 HKEY_CLASSES_ROOT\AscetServer.AscetServer.6.4.3
 HKEY_CLASSES_ROOT\CLSID\{63C4AEF3-B847-4b01-B25D-319D0CF1C698}
 HKEY_CLASSES_ROOT\.six
 HKEY_CLASSES_ROOT\SCOOP-IX_file
 HKEY_CLASSES_ROOT\SCOOP-IX_file\DefaultIcon
 HKEY_CLASSES_ROOT\SCOOP-IX_file\shell
 HKEY_CLASSES_ROOT\SCOOP-IX_file\shell\Open in Browser\command
 HKEY_CLASSES_ROOT\ascet
 HKEY_CLASSES_ROOT\ascet\shell\open\command
 HKEY_CLASSES_ROOT\asd
 HKEY_CLASSES_ROOT\asd\shell\open\command
 HKEY_CURRENT_USER\Software\ETAS
 HKEY_CURRENT_USER\Software\ETAS\ASCET

File system access

ASCET requires access to the following file-system locations:

Folder Default(s) Installation Use

C:\ETAS\ASCETx.y RW RW
C:\ETAS\LogFiles RW RW
<installation folder>
C:\ETAS\ETASManuals RW R
C:\ETASData\ASCETx.y RW RW

ASCET V6.4.3 Release Notes 8

ETAS Product Definition

C:\Program Files RW RW
(x86)\Common Files\ETAS
C:\Windows\SysWOW64 RW RW
%ProgramData%\ETAS C:\ProgramData\ETAS RW RW
C:\Users\<username>\App RW RW
Data\Local\Temp
C:\Users\<username>\App RW RW
Data\Roaming\ETAS

2.3 Release Test Configuration

The ASCET release-tests have been executed with the following configuration:
 Host OS:
o Windows® 7 x86_64 Service Pack 1
o Windows® 8.1 x86_64
o Windows® 10 x86_64
 Compilers for host PC:
o Microsoft Studio 2005 Express
o Microsoft Studio 2008
o GNU C Compiler V4.7.2
 Compilers for Prototyping targets:
o GNU C Compiler V3.4.4
 µC on target testing:
o MPC55xx, WindRiver Compiler V5.6.0
o C16x, Tasking VX V2.2r1

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®. You find
the installation link in the ToolsAndUtilities directory on the installation DVD.
The DVD contains the following items:
Directory Meaning / Explanation
ASCET V6.4 ASCET base system installation, including release notes
ASCET-DIFF V6.4 ASCET Model Difference Browser installation
ASCET-MD V6.4 ASCET Modeling & Design installation
ASCET-MDV V6.4 ASCET Model Viewer installation
ASCET-VIEW V6.4 ASCET Eclipse-based Model Viewer installation
ASCET-RP V6.4 ASCET Rapid Prototyping installation
ASCET-SCM V6.4 ASCET Software Configuration Management installation
ASCET-SE V6.4 ASCET Software Engineering (for multiple targets)
installation
Documentation Documentation set for complete ASCET V6.4 product family
(in PDF format)

ASCET V6.4.3 Release Notes 9

ETAS Product Definition

Graphic Graphical elements for the product installer program

Main Main elements for the product installer program
MDA V5.3 Measure Data Analyzer installation
Partner ETAS Partner information for the product installer program
Support ETAS customer support contact information for the product
installer program
ToolsAndUtilities - ASCET-SCM_CM-Tool-Configuration
(content also incl. in online help)
- ASCET-SCM_Difference Browsing
- ASCET-SCM_Driver Toolkit
- ASCET-SCM_Subversion Client V1.6
- ASCET-SCM_Subversion ScriptingAPI Example
- CaliberRM Coupling
- Code Coverage Analysis
- DotNetFx
- Licensing Tools for FlexLM
- MikTex Documentation Generation
- MSVisualCPP6 Compiler
- OpenSourceSoftware
- WebService Example
- Winroll

2.4.1 Used 3rd Party Software

ASCET makes use of the following products that are released under the respective licenses.
For details please refer to the following documents on the DVD under the folder:

\ToolsAndUtilities\OpenSourceSoftware\

2.5 Installation

You must install the following Microsoft® redistributables before installing ASCET:
 Microsoft® .NET Framework 4.6.2 or later
 Microsoft® Visual C++ Redistributable Package 2010 SP1
 Microsoft® Visual C++ Redistributable Package 2015 SP2
These are available from Microsoft.
After you have installed the r, follow the installation instructions on the DVD installer or the
ASCET installer.exe. Further details are available in the installation manual [ASW_INST_EN]

2.6 Licensing

The use of ASCET products is protected by electronic licensing. Valid licenses are necessary
to install ASCET and its add-ons. The use of unlicensed ETAS software is prohibited. The
required licenses are not included in this delivery.

When you purchase ASCET licenses, you receive a separate entitlement letter. You activate
the license using a self-service portal on the ETAS website
(http://www.etas.com/support/licensing). For assistance, please consult the help file available

ASCET V6.4.3 Release Notes 10

ETAS Product Definition

on the start page of the self-service portal. During the activation process, you receive the
necessary license keys per E-mail.

ASCET V6.4.3 Release Notes 11

ETAS Changes

3 Changes

This chapter describes changes with respect to the previous release of ASCET.

3.1 What’s New

The following changes have been made with this release:

 Modelling
o Arrays and Matrixes can now have a larger size: arrays up to 65535
elements, matrixes up to 1.000.000 elements (with a maximum of 65535 for
each dimension).
o New operators in the block diagram to retrieve the size of an array or matrix
o New “mixed physical” implementations, that can be used in the physical
code generation to specify implementations for single elements.
 Code generation
o Removed error MIa5 “Cannot mix float and int”. If a mixture of float and int
occurs, the integer operands are casted to float and the calculation is
executed in floating point.
o Weaker type check when passing arguments to methods in C-code
components, service routine classes or prototype classes: the model type
and the limit-assignment-flag are not checked any more. The purpose is to
improve the reusability of these methods.
 EHOOKS
o Updated to add support for EHOOKS V4.2 and V4.3
o Automapping using the A2L display identifier
o Automapping of scalar messages to ECU array elements
 AUTOSAR
o The AUTOSAR importer has been enhanced to support version 4.2.2 and
system constants.

3.2 Compatibility to Earlier Releases

ASCET V6.4.3 is functionally upwards compatible with previous versions.

There are no known Database incompatibilities to ASCET V5.0 / V5.1 / V5.2 /
V6.0, V6.1, V6.2 & V6.3
ASCET V6.4.3 can only import or read models that have been created with ASCET-SD
V4.0.16 or higher.
Before exporting or converting the database, a database defragmentation (Utilities or Tools
menu, DatabasePerformance Utilitiesoptimize database) is recommended. For older
models, you have to import and export them with ASCET-SD V4.0.16 or V4.1.x first.
After opening a database that was created using a previous ASCET version (e.g. ASCET-SD
V5.2.2 or V4.2.x), ASCET asks if you want to convert the database (see screenshot below).
If you answer with yes, a path selection dialog is opened and you can define the destination
directory for the database conversion. A new ASCET V6.x database is created in that
directory. The original database remains untouched. The converted database is now usable
with ASCET V6.x but no longer with the old version.
A similar conversion is made for export files (*.exp) created with previous versions.

ASCET V6.4.3 Release Notes 12

ETAS Changes

If you encounter difficulties in using your ASCET V5.x or V6.x Database under ASCET V6.4,
please contact your local ETAS Hotline.

ASCET .amd Export Compatibility

ASCET V6.4.3 provides .amd export compatibility for the following legacy versions:
o V5.2.2
o V6.0.1
o V6.1.4
o V6.2.1
o V6.3.1
o V6.4.0
o V6.4.1
o V6.4.2

3.3 Fixed Problems

The following problems were fixed in ASCET V6.4.3.
ID Title
550941 COM-API is sometimes not working
553217 Import directory (a2l files only) does not work if database contains no folder
555522 Compile error in vatfile.c with variant coded data structures enabled
556404 Missing init values for group char table with imported distribution
559555 Incorrect generation of the unit of variables and characteristics in the ASAM-
2MC description file
559691 New info IIa14 for floating point limitations that may be not necessary
563321 Virtual Address Table for Bit Fields does not compile with Variant Coded Data
Structures
566512 Exit due to error 60 if LabCar-ASC is installed without ASCET-RP
567141 MDF file cannot be used for signal stimulation due to "Error accessing all
records of <Signal>. Advice: File may be corrupt."
572214 Value ranges in C code comments of float elements in comments are wrong
573274 Autosar compliant represenation of linear formuals with rational coefficients
573784 Record elements with user defined order are unintentionally resorted
580793 Float system constant is generated as double precision which leads to float
emulation on single precsion FPU
581525 User Order for Record Elements is not considered in Experiment
332045 Inconsistent graphical representation when changing SR-Interface to
"provided"

ASCET V6.4.3 Release Notes 13

ETAS Changes

328356 Wrong display with properties editor with multiple element selection
309275 Paste of hierarchy pins does not work
571228 Diagram incomplete despite option 'Scale Diagram to fit page' enabled
580851 xSize/ySize as well as xAxis/yAxis of a standard/fixed chartable must not
appear in the a2l file
580239 Implementation settings get corrupt via copy & paste
577316 ASCET imports a component to be a child of another component
574771 Wrong error on AMD export of model with Statement Block
573739 Entry in the unit field is not saved for new integer types
573313 CASE statement is generated with float literals
572413 normal sequencing in statementblocks is buggy to use
567231 Dead Code Elimination removes live code
567201 Lines are moved after importing an ASCET 6.1.4 model
564242 Wrong error message "Model values exceed limits" in implementation editor
564207 Missing #defines for system constants resolved at generation time and used
in C code components
563740 Memory segment not correctly propagated to the IRV copies
563732 Wrong error MMdl82 for switch statements with fall-through cases
563731 System error during Export Generated Code
563695 Missing variation point on AUTOSAR type mapping
563678 Missing Variation Point on record-IRV init values
563481 Sequence calls inside statements block are not displayed correctly
563124 Globaly analysis takes unusually long for specific projects
562607 Missing execute method on statement blocks
558346 Show Unused Elements shows used arguments
557938 Floating point comparison wrongly optimized
557436 Sequence Call in Statement Block: Missing default name and position shift
557355 Requirement: Change binding time in ARXML to CODE-GENERATION-TIME
555675 Duplicate #if removes code from compilation
555334 Open external c code editor and edit without changes marks item as modified
555314 Open external c code editor and change to object code does not mark item
as modified
555305 Erroneous sequencing within Statement Blocks
555300 Empty method list in Sequence Call Editor within Statement Blocks
544449 Wrong version information for a component
542085 Properties editor does not open when graphic objects are multiselected in the
BDE
578821 Wrongly reused subexpression if "Common Subexpression Elimination" is
enabled

3.4 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:

http://www.etas.com/kir

3.5 Known Issues

This section describes the set of known problems of the released version of ASCET V6.4.3.

ASCET V6.4.3 Release Notes 14

ETAS Changes

ID Title
[EHI ID]
293145 1GEE Online Experiment: Change measure rate is always grayed out
[50828] After adding a variable to a measurement window the acquisition rate
(alias raster / OS task) cannot be changed later on because the entry in
the context menu is always disabled (grayed out).
293808 Virtual Parameter not calibrate-able in offline simulation
[52675] Virtual variables are calibratable, but virtual Parameter are not calibratable
in offline simulation, see attached example.
=> v_param is defined as Existence: virtual
=> v_param is defined with Calibration: YES
297593 Offline experiment: Hierarchy States not correctly reinitialised when
[68869] Hierarchical CGEN
In the ASCET offline PC-experiment, hierarchy state variables in State
Machines are not reinitialised when "Experiment Stop" and "Reinit Both" is
executed.
The workaround is, to close and open the experiment whenever a full init
is required.
304106 Data buffer returned from target has invalid length, the error occurred
[90653] while retrieving the pseudo address for ...
ASCET supports only components with a maximum of 999 methods
(including direct access methods) when running an experiment on an
experimental target.
334631 Code Generation fails after conversion to ASCET V6.1 when array or
matrix of kind "parameter" is used as method argument
If a method component, using an array or matrix as method argument, is
converted to ASCET V6.1 or higher,
ASCET enables the new introduced IN and OUT attributes for this
argument to ensure that it is possible to write to the array or matrix
argument within the method code.
ASCET code generation fails
WHEN the converted method is called by another component by using an
array or matrix of kind "parameter"
The code generator will report the error MMdl104 since parameters are
not writeable.
Workaround: The OUT attribute must be unset for the array or matrix
argument in the method definition.
349823 MSVS-2005..2008 compiler defect with floating point precision
Due to a known issue of the Microsoft Visual Studio Compiler 2005..2008
in certain cases a rounding issue occurs  wrong floating point values.
Citation from:
http://msdn.microsoft.com/en-us/library/e7s85ffb%28v=vs.90%29.aspx
with topic compiler configuration /fp (Specify Floating-Point Behavior):
With /fp:precise on x86 processors, the compiler will perform rounding
on variables of type float to the proper precision for assignments and
casts and when passing parameters to a function. (...)

ASCET V6.4.3 Release Notes 15

ETAS Hints

4 Hints

UTC Time Stamps for ASCET objects and generated

artifacts

ASCET V5.2.1 and later use UTC time stamps for internal objects and generated artifacts.
If you are working V5.2.1 or later and an older ASCET version on the same database, we
strongly recommend doing a full rebuild on all ASCET sources every time you switch back
to ASCET V6.0. This is necessary to avoid any inconsistency in the ASCET sources.

Code Generation

It is recommended to perform a clean code generation directory before doing a

complete project build. Otherwise ASCET may not consistently consider all changed
options during make.

4.1 Release Notes

These release notes are copied to the ETASManuals\ASCET V6.4 folder during
installation and can be opened from there.

4.2 Non ANSI-C compliant identifier in older ASCET versions

When migrating older ASCET models (for versions < ASCET V5.0.0), ASCET code generation
may adapt non ANSI-C compliant identifier automatically in the generated C-code and issue
a warning in the build monitor.

4.3 XML Workspace and Export/Import

For externally created or adapted XML files compliance to the XML schemas (to be found in
the installation directory of ASCET) is important to obtain consistent and readable ASCET
components.

Operating ASCET's GUI during import of .axl & .amd - files

During import of the XML based description files .axl & .amd, it is possible to operate
ASCET’s GUI. This is not recommended, as inconsistencies of the manipulated ASCET
objects may occur.
Please do not work with ASCET during import of .axl or .amd files.

It is not possible to create folder hierarchies/components with pathnames exceeding 180

characters, for legacy DBs or imported components a longer pathname is possible, but
ASCET V6.4.3 won’t export such components/folders. The user will be notified to reduce the
path length by renaming/move the respective component.

4.4 Use of Microsoft Visual Studio C++ Compiler V6.0

If you want to use the older MS Studio Compiler V6.0 with ASCET V6.0, please copy the
MSVisual6.acd.xml file from the Tools & Utilities directory to your installation folder
.\Tools\compiler. This will allow you to select this compiler in your project property
settings.

ASCET V6.4.3 Release Notes 16

ETAS Hints

4.5 Double Byte Characters are not supported

ASCET does not support the use of double byte characters. You may use double byte
Characters, but the correct post processing for documentation can not be assured. The
ASCET code generation is not affected as ANSI-C does not make use of double byte
characters.

4.6 Long compilation times with Visual Studio Compiler under Windows 8 x86_64

This observed behavior of the Microsoft Visual Studio Compiler has been reported to
Microsoft and documented in Support request, No. 113040210332116

4.7 Removal of Borland V4.5 for PC experiments

ASCET 6.3 changed the default compiler for the PC experiment from Borland V4.5 to GCC
V4.7.2.
ASCET V6.4 stopped shipping the Borland V4.5 Compiler with the ASCET installation.
The Borland V4.5 compiler continues to be supported by ASCET, but you must buy and
install the compiler separately. The compiler can be obtained from
http://www.embarcadero.com.

4.8 Advanced Information

A

The following options in Build  Code Generation in the ASCET project properties will be
deprecated in the next version of ASCET:

- Force parenthesis for Binary Logical Operators

o Parentheses will always be used. This change has no impact on behavior
- Add parenthesis for readability
o Parentheses will always be used. This change has no impact on behavior
- Casting
o ASCET will use MISRA casting only in the future.
- Allow Double bit Size for Division Numerators
o This option has no effect on 32-bit targets (because numerators cannot be
doubled to 64-bit). The use case for 16-bit (ternary services with
intermediate values of a larger value range) is now implemented
independently of this option.
- Use SHIFT Operation on Signed Values instead of MUL Operation
o ASCET will always use a MUL operation in the future. When this option is
enabled it can change mathematical behavior and will break MISRA-C
compliance. In modern optimizing compilers, the compiler is intelligent
enough to perform this optimization without needing a “hint” from code
generation.

ASCET V6.4.3 Release Notes 17

ETAS Hints

The following options in Build  Code Generation  Optimization in the ASCET

project properties will be deprecated in the next version of ASCET:

- Optimize Direct Access Methods (One Level)

o Subsumed into the option for multiple levels

The following options in Build  Code Generation  Optimization  State Machine

in the ASCET project properties will be deprecated in the next version of ASCET:

- Optimize Static Actions (Restricted Modelling)

o Disabling this option leads to state machine permits strange behavior with
respect to execution order of static actions and transition conditions. This
option will always be enabled, thus making models easier to comprehend.
- Generate well-formed switch
o A well-formed switch will always be generated (as required for MISRA
compliance).

ASCET V6.4.3 Release Notes 18

ETAS ETAS Contact Addresses

5 ETAS Contact Addresses

ETAS HQ
ETAS GmbH
Borsigstraße 14 Phone: +49 711 3423-0
70469 Stuttgart Fax: +49 711 3423-2106
Germany WWW: www.etas.com

ETAS Subsidiaries and Technical Support

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

ASCET V6.4.3 Release Notes 19