document change history - autosar...31.01.2007 autosar 1.1.0 administration • add: compiler058 •...

Specification of Compiler Abstraction V2.0.2

R3.1 Rev 0001

Document Title Specification of Compiler Abstraction

Document Owner AUTOSAR GbR Document Responsibility AUTOSAR GbR Document Identification No 051 Document Classification Standard Document Version 2.0.2 Document Status Final Part of Release 3.1 Revision 0001

Document Change History Date Version Changed by Change Description 15.08.2008 2.0.2 AUTOSAR

Administration Layout adaptations

23.06.2008 2.0.1 AUTOSAR Administration

Legal disclaimer revised


• Keyword "_STATIC_" has been renamed to "STATIC"

• Keyword "_INLINE_" has been renamed to "INLINE"

• Keyword "TYPEDEF" has been added as empty memory qualifier for use in type definitions

• Document meta information extended • Small layout adaptations made


• Add: COMPILER058 • Add: COMPILER057 • Change: COMPILER040 • Legal disclaimer revised • Release Notes added • “Advice for users” revised • “Revision Information” added


Initial Release

1 of 43 Document ID 051: AUTOSAR_SWS_CompilerAbstraction - AUTOSAR confidential -


R3.1 Rev 0001

Page left intentionally blank



R3.1 Rev 0001

Disclaimer

This document of a specification as released by the AUTOSAR Development Partnership is intended for the purpose of information only. The commercial exploitation of material contained in this specification requires membership of the AUTOSAR Development Partnership or an agreement with the AUTOSAR Development Partnership. The AUTOSAR Development Partnership will not be liable for any use of this specification. Following the completion of the development of the AUTOSAR specifications commercial exploitation licenses will be made available to end users by way of written License Agreement only.

No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without per-mission in writing from the publisher." The word AUTOSAR and the AUTOSAR logo are registered trademarks.

Copyright © 2004-2008 AUTOSAR Development Partnership. All rights reserved. Advice to users of AUTOSAR Specification Documents: AUTOSAR Specification Documents may contain exemplary items (exemplary reference models, "use cases", and/or references to exemplary technical solutions, devices, processes or software). Any such exemplary items are contained in the Specification Documents for illustration purposes only, and they themselves are not part of the AUTOSAR Standard. Neither their presence in such Specification Documents, nor any later documentation of AUTOSAR conformance of products actually implementing such exemplary items, imply that intellectual property rights covering such exemplary items are licensed under the same rules as applicable to the AUTOSAR Standard.



R3.1 Rev 0001

Table of Contents 1 ................................................................... 6 Introduction and functional overview2 ............................................................................... 7 Acronyms and abbreviations3 ........................................................................................ 8 Related documentation

3.1 ........................................................................................... 8 Input documents3.2 Related standards and norms ...................................................................... 9

4 Constraints and assumptions ............................................................................ 10

4.1 Limitations .................................................................................................. 10 4.2 Applicability to car domains........................................................................ 10 4.3 Applicability to safety related environments ............................................... 10

5 Dependencies to other modules........................................................................ 11

5.1 Code file structure ...................................................................................... 11 5.2 Header file structure ................................................................................... 11 5.3 Connections to other modules.................................................................... 11

5.3.1 Compiler Abstraction........................................................................... 11 5.3.2 Memory Mapping ................................................................................ 11 5.3.3 Linker-Settings .................................................................................... 12

6 Requirements traceability .................................................................................. 13

7 Analysis ............................................................................................................. 18

7.1 Keywords for functions ............................................................................... 18 7.2 Keywords for pointers................................................................................. 19

8 Functional specification ..................................................................................... 24

8.1 General issues ........................................................................................... 24 8.2 Contents of Compiler.h............................................................................... 24 8.3 Contents of Compiler_Cfg.h ....................................................................... 25

9 API specification................................................................................................ 26

9.1 Definitions .................................................................................................. 26 9.1.1 memory class AUTOMATIC................................................................ 26 9.1.2 memory class TYPEDEF .................................................................... 26 9.1.3 STATIC ............................................................................................... 26 9.1.4 NULL_PTR.......................................................................................... 26 9.1.5 INLINE ................................................................................................ 27

9.2 Macros for functions ................................................................................... 27 9.2.1 FUNC .................................................................................................. 27

9.3 Macros for pointers..................................................................................... 27 9.3.1 P2VAR ................................................................................................ 27 9.3.2 P2CONST ........................................................................................... 28 9.3.3 CONSTP2VAR.................................................................................... 29 9.3.4 CONSTP2CONST............................................................................... 29 9.3.5 P2FUNC.............................................................................................. 30

9.4 Keywords for constants .............................................................................. 31 9.4.1 CONST ............................................................................................... 31



R3.1 Rev 0001

9.5 Keywords for variables ............................................................................... 31 9.5.1 VAR..................................................................................................... 31

10 Sequence diagrams....................................................................................... 33

11 Configuration specification............................................................................. 34

11.1 How to read this chapter ............................................................................ 34 11.1.1 Configuration and configuration parameters ....................................... 34 11.1.2 Variants............................................................................................... 35 11.1.3 Containers........................................................................................... 35

11.2 Containers and configuration parameters .................................................. 35 11.2.1 Variants............................................................................................... 35 11.2.2 Module Configuration (Memory and pointer classes) .......................... 36

11.3 Published Information................................................................................. 39

12 Annex............................................................................................................. 40

12.1 List of Compiler symbols ............................................................................ 40 12.2 Requirements on implementations using compiler abstraction .................. 40 12.3 Proposed process ...................................................................................... 42 12.4 Comprehensive example............................................................................ 43



R3.1 Rev 0001

1 Introduction and functional overview This document specifies macros for the abstraction of compiler specific keywords used for addressing data and code within declarations and definitions. Mainly compilers for 16 bit platforms (e.g. Cosmic and Metrowerks for S12X or Tasking for ST10) are using special keywords to cope with properties of the microcontroller architecture caused by the limited 16 bit addressing range. Features like paging and extended addressing (to reach memory beyond the 64k border) are not chosen automatically by the compiler, if the memory model is not adjusted to ‘large’ or ‘huge’. The location of data and code has to be selected explicitly by special keywords. Those keywords, if directly used within the source code, would make it necessary to port the software to each new microcontroller family and would prohibit the requirement of platform independency of source code. If the memory model is switched to ‘large’ or ‘huge’ by default (to circumvent these problems) the project will suffer from an increased code size. This document specifies a three-step concept:

1. The file Compiler.h provides macros for the encapsulation of definitions and declarations.

2. Each single module has to distinguish between at least the following different

memory classes and pointer classes. Each of these classes is represented by a define (e.g. EEP_CODE).

3. The file Compiler_Cfg.h allows to configure these defines with the appropriate

compiler specific keywords according to the modules description and memory set-up of the build scenario.

Environment



R3.1 Rev 0001

2 Acronyms and abbreviations Acronyms and abbreviations that have a local scope are not contained in the AUTOSAR glossary. These must appear in a local glossary. Acronym: Description: Large, huge Memory model configuration of the microcontroller’s compiler. By default, all access

mechanisms are using extended/paged addressing. Some compilers are using the term ‘huge’ instead of ‘far’.

Tiny, small Memory model configuration of the microcontroller’s compiler. By default, all access mechanisms are using normal addressing. Only data and code within the addressing range of the platform’s architecture is reachable (e.g. 64k on a 16 bit architecture).

far Compiler keyword for extended/paged addressing scheme (for data and code that may be outside the normal addressing scheme of the platform’s architecture).

near Compiler keyword for normal addressing scheme (for data and code that is within the addressing range of the platform’s architecture).

C89 ANSI X3.159-1989 Programming Language C C90 ISO/IEC 9899:1990 C99 ISO/IEC 9899:1999, 2nd edition, 1. December 1999 EmbeddedC ISO/IEC DTR 18037, draft standard, 24. September 2003



R3.1 Rev 0001

3 Related documentation

3.1 Input documents

[1] List of Basic Software Modules, AUTOSAR_BasicSoftwareModules.pdf

[2] General Requirements on Basic Software Modules,

AUTOSAR_SRS_General.pdf [3] Layered Software Architecture,

AUTOSAR_LayeredSoftwareArchitecture.pdf

[4] Specification of ECU Configuration, AUTOSAR_ECU_Configuration.pdf

[5] AUTOSAR Basic Software Module Description Template, AUTOSAR_BSW_Module_Description.pdf

[6] Cosmic C Cross Compiler User’s Guide for Motorola MC68HC12,V4.5 [7] ARM ADS compiler manual [8] GreenHills MULTI for V850 V4.0.5:

Building Applications for Embedded V800, V4.0, 30.1.2004 [9] TASKING for ST10 V8.5:

C166/ST10 v8.5 C Cross-Compiler User's Manual, V5.16 C166/ST10 v8.5 C Cross-Assembler, Linker/Locator, Utilities User's Manual, V5.16

[10] Wind River (Diab Data) for PowerPC Version 5.2.1:

Wind River Compiler for Power PC - Getting Started, Edition 2, 8.5.2004 Wind River Compiler for Power PC - User's Guide, Edition 2, 11.5.2004

[11] TASKING for TriCore TC1796 V2.0R1:

TriCore v2.0 C Cross-Compiler, Assembler, Linker User's Guide, V1.2 [12] Metrowerks CodeWarrior 4.0 for Freescale HC9S12X/XGATE (V5.0.25):

Motorola HC12 Assembler, 2.6.2004 Motorola HC12 Compiler, 2.6.2004 Smart Linker, 2.4.2004



R3.1 Rev 0001

3.2 Related standards and norms

[13] ANSI X3.159-1989 Programming Language C [14] ISO/IEC 9899:1990 [15] ISO/IEC 9899:1999, 2nd edition, 1. December 1999 [16] ISO/IEC DTR 18037, draft standard, 24. September 2003



R3.1 Rev 0001

4 Constraints and assumptions

4.1 Limitations

During specification of abstraction and validation of concept the compilers listed in chapter 3.1 have been considered. If any other compiler requires keywords that cannot be mapped to the mechanisms described in this specification this compiler will not be supported by AUTOSAR. In this case, the compiler vendor has to adapt its compiler. The concepts described in this document do only apply to C compilers according the standard C90. C++ is not in scope of this version. In contradiction to the C-standard, some extensions are required:

- keywords for interrupt declaration - keywords for hardware specific memory modifier - uninitialized variables

If the physically existing memory is larger than the logically addressable memory in either code space or data space and more than the logically addressable space is used, logical addresses have to be reused. The C language (and other languages as well) can not cope with this situation.

4.2 Applicability to car domains

No restrictions.

4.3 Applicability to safety related environments

No restrictions. The compiler abstraction file does not implement any functionality, only symbols and macros.



R3.1 Rev 0001

5 Dependencies to other modules COMPILER048: The SWS Compiler Abstraction is applicable for each AUTOSAR software module. Therefore the implementation of the of memory class (memclass) and pointer class (ptrclass) macro parameters (see COMPILER040) shall fulfill the implementation and configuration specific needs of each software module in a specific build scenario.

5.1 Code file structure

Not applicable

5.2 Header file structure

COMPILER052: Include structure of the compiler specific language extension header:

cd file structure

Compiler.h Std_Types.h

Compiler_Cfg.h

«includes»

«includes»

Figure 1: Include structure of Compiler.h

5.3 Connections to other modules

The following shall describe the connections to modules, which are indirectly linked to each other.

5.3.1 Compiler Abstraction

As described in this document, the compiler abstraction is used to configure the reachability of elements (pointers, variables, function etc.)

5.3.2 Memory Mapping

This module is used to do the sectioning of memory. The user can define sections for optimizing the source code.



R3.1 Rev 0001

5.3.3 Linker-Settings

The classification which elements are assigned to which memory section can be done by linker-settings.



R3.1 Rev 0001

6 Requirements traceability Document: AUTOSAR requirements on Basic Software, general Requirement Satisfied by [BSW003] Version identification COMPILER043

[BSW00300] Module naming convention Not applicable (Compiler Abstraction is not a BSW module)

[BSW00301] Limit imported information Not applicable (Compiler Abstraction is not a BSW module)

[BSW00302] Limit exported information Not applicable (Compiler Abstraction is not a BSW module)

[BSW00304] AUTOSAR integer data types Not applicable (Compiler Abstraction is not a BSW module)

[BSW00305] Self-defined data types naming convention Not applicable (Compiler Abstraction is not a BSW module)

[BSW00306] Avoid direct use of compiler and platform specific keywords

supported by: COMPILER001, COMPILER006, COMPILER010, COMPILER012, COMPILER013, COMPILER015, COMPILER023, COMPILER026, COMPILER031, COMPILER032, COMPILER033, COMPILER035, COMPILER036, COMPILER039, COMPILER044, COMPILER046

[BSW00307] Global variables naming convention Not applicable (Compiler Abstraction is not a BSW module)

[BSW00308] Definition of global data Not applicable (Compiler Abstraction is not a BSW module)

[BSW00309] Global data with read-only constraint Not applicable (Compiler Abstraction is not a BSW module)

[BSW00310] API naming convention Not applicable (Compiler Abstraction is not a BSW module)

[BSW00312] Shared code shall be reentrant Not applicable (Compiler Abstraction is not a BSW module)

[BSW00314] Separation of interrupt frames and service routines

Not applicable (Compiler Abstraction is not a BSW module)

[BSW00318] Format of module version numbers COMPILER043

[BSW00321] Enumeration of module version numbers COMPILER043

[BSW00323] API parameter checking Not applicable (Compiler Abstraction is not a BSW module)

[BSW00324] Do not use HIS I/O Library Not applicable (non-functional requirement)

[BSW00325] Runtime of interrupt service routines Not applicable (Compiler Abstraction is not a BSW module)

[BSW00326] Transition from ISRs to OS tasks Not applicable (Compiler Abstraction is not a BSW module)

[BSW00327] Error values naming convention Not applicable (Compiler Abstraction is not a BSW module)

[BSW00328] Avoid duplication of code supported by: COMPILER048

[BSW00329] Avoidance of generic interfaces Not applicable (Compiler Abstraction is not a BSW module)

[BSW00330] Usage of macros / inline functions instead of functions


[BSW00331] Separation of error and status values Not applicable (Compiler Abstraction is not a BSW module)

[BSW00333] Documentation of callback function context




R3.1 Rev 0001

Requirement Satisfied by [BSW00334] Provision of XML file Not applicable

(Compiler Abstraction is not a BSW module)

[BSW00335] Status values naming convention Not applicable (Compiler Abstraction is not a BSW module)

[BSW00336] Shutdown interface Not applicable (Compiler Abstraction is not a BSW module)

[BSW00337] Classification of errors Not applicable (Compiler Abstraction is not a BSW module)

[BSW00338] Detection and Reporting of development errors


[BSW00339] Reporting of production relevant error status


[BSW00341] Microcontroller compatibility documentation


[BSW00342] Usage of source code and object code Not applicable (non-functional requirement)

[BSW00343] Specification and configuration of time Not applicable (Compiler Abstraction is not a BSW module)

[BSW00344] Reference to link-time configuration Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00345] Pre-compile-time configuration Chapter 11.2.1

[BSW00346] Basic set of module files Not applicable (Compiler Abstraction is not a BSW module)

[BSW00347] Naming separation of different instances of BSW drivers


[BSW00348] Standard type header COMPILER003, COMPILER004, COMPILER052

[BSW00350] Development error detection keyword Not applicable (Compiler Abstraction is not a BSW module)

[BSW00353] Platform specific type header Not applicable (Compiler Abstraction is the C-language extension header)

[BSW00355] Do not redefine AUTOSAR integer data types


[BSW00357] Standard API return type Not applicable (Compiler Abstraction is not a BSW module)

[BSW00358] Return type of init() functions Not applicable (Compiler Abstraction is not a BSW module)

[BSW00359] Return type of callback functions Not applicable (Compiler Abstraction is not a BSW module)

[BSW00360] Parameters of callback functions Not applicable (Compiler Abstraction is not a BSW module)

[BSW00361] Compiler specific language extension header COMPILER003, COMPILER004

[BSW00369] Do not return development error codes via API


[BSW00370] Separation of callback interface from API Not applicable (Compiler Abstraction is not a BSW module)

[BSW00371] Do not pass function pointers via API Not applicable (Compiler Abstraction is not a BSW module)

[BSW00373] Main processing function naming convention


[BSW00374] Module vendor identification COMPILER043

[BSW00375] Notification of wake-up reason Not applicable (Compiler Abstraction is not a BSW module)

[BSW00376] Return type and parameters of main processing functions




R3.1 Rev 0001

Requirement Satisfied by [BSW00377] Module specific API return types Not applicable

(Compiler Abstraction is not a BSW module)

[BSW00378] AUTOSAR boolean type Not applicable (Compiler Abstraction is not a BSW module)

[BSW00379] Module identification COMPILER043

[BSW00380] Separate C-Files for configuration parameters [approved]

Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00381] Separate configuration header file for pre-compile time parameters COMPILER052

[BSW00383] List dependencies of configuration files Figure 1: Include structure of Compiler.h

[BSW00384] List dependencies to other modules COMPILER048

[BSW00385] List possible error notifications Not applicable (Compiler Abstraction is not a BSW module)

[BSW00386] Configuration for detecting an error Not applicable (Compiler Abstraction is not a BSW module)

[BSW00387] Specify the configuration class of callback function


[BSW00388] Introduce containers Chapter 11.2

[BSW00389] Containers shall have names COMPILER044

[BSW00390] Parameter content shall be unique within the module


[BSW00391] Parameter shall have unique names Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00392] Parameters shall have a type Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00393] Parameters shall have a range Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00394] Specify the scope of the parameters Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00395] List the required parameters (per parameter)


[BSW00396] Configuration classes COMPILER044

[BSW00397] Pre-compile-time parameters COMPILER044

[BSW00398] Link-time parameters Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00399] Loadable Post-build time parameters Not applicable (Compiler Abstraction is specific per build scenario)

[BSW004] Version check Not applicable (Compiler Abstraction is not a BSW module)

[BSW00400] Selectable Post-build time parameters Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00401] Documentation of multiple instances of configuration parameters


[BSW00402] Published information COMPILER043

[BSW00404] Reference to post build time configuration Not applicable (Compiler Abstraction is specific per build scenario)



R3.1 Rev 0001

Requirement Satisfied by

[BSW00405] Reference to multiple configuration sets Not applicable (Compiler Abstraction is specific per build scenario)

[BSW00406] Check module initialization Not applicable (Compiler Abstraction is not a BSW module)

[BSW00407] Function to read out published parameters Not applicable (Compiler Abstraction is not a BSW module)

[BSW00408] Configuration parameter naming convention


[BSW00409] Header files for production code error IDs Not applicable (Compiler Abstraction is not a BSW module)

[BSW00410] Compiler switches shall have defined values


[BSW00411] Get version info keyword Not applicable (Compiler Abstraction is not a BSW module)

[BSW00412] Separate H-File for configuration parameters COMPILER052

[BSW00413] Accessing instances of BSW modules Not applicable (Compiler Abstraction is not a BSW module)

[BSW00414] Parameter of init function Not applicable (Compiler Abstraction is not a BSW module)

[BSW00415] User dependent include files Not applicable (non-functional requirement)

[BSW00416] Sequence of Initialization Not applicable (Compiler Abstraction is not a BSW module)

[BSW00417] Reporting of Error Events by Non-Basic Software


[BSW00419] Separate C-Files for pre-compile time configuration parameters


[BSW00420] Production relevant error event rate detection


[BSW00421] Reporting of production relevant error events


[BSW00422] Debouncing of production relevant error status


[BSW00423] Usage of SW-C template to describe BSW modules with AUTOSAR Interfaces


[BSW00424] BSW main processing function task allocation


[BSW00425] Trigger conditions for schedulable objects Not applicable (Compiler Abstraction is not a BSW module)

[BSW00426] Exclusive areas in BSW modules Not applicable (Compiler Abstraction is not a BSW module)

[BSW00427] ISR description for BSW modules Not applicable (Compiler Abstraction is not a BSW module)

[BSW00428] Execution order dependencies of main processing functions


[BSW00429] Restricted BSW OS functionality access Not applicable (Compiler Abstraction is not a BSW module)

[BSW00431] The BSW Scheduler module implements task bodies


[BSW00432] Modules should have separate main processing functions for read/receive and write/transmit data path


[BSW00433] Calling of main processing functions Not applicable (Compiler Abstraction is not a BSW module)



R3.1 Rev 0001

Requirement Satisfied by [BSW00434] The Schedule Module shall provide an API for exclusive areas


[BSW005] No hard coded horizontal interfaces within MCAL

Not applicable (non-functional requirement)

[BSW006] Platform independency

supported by: COMPILER001, COMPILER006, COMPILER010, COMPILER012, COMPILER013, COMPILER015, COMPILER023, COMPILER026, COMPILER031, COMPILER032, COMPILER033, COMPILER035, COMPILER036, COMPILER039, COMPILER044, COMPILER046

[BSW007] HIS MISRA C Not applicable (Compiler Abstraction is the C-language extension header)

[BSW009] Module User Documentation Not applicable (Compiler Abstraction is not a BSW module)

[BSW010] Memory resource documentation Not applicable (Compiler Abstraction is not a BSW module)

[BSW101] Initialization interface Not applicable (Compiler Abstraction is not a BSW module)

[BSW158] Separation of configuration from implementation


[BSW159] Tool-based configuration Chapter 11.2.2

[BSW160] Human-readable configuration data COMPILER044

[BSW161] Microcontroller abstraction Not applicable (non-functional requirement)

[BSW162] ECU layout abstraction Not applicable (non-functional requirement)

[BSW164] Implementation of interrupt service routines Not applicable (non-functional requirement)

[BSW167] Static configuration checking Not applicable (Compiler Abstraction is specific per build scenario)

[BSW168] Diagnostic Interface of SW components Not applicable (Compiler Abstraction is not a BSW module)

[BSW170] Data for reconfiguration of AUTOSAR SW-Components


[BSW171] Configurability of optional functionality Not applicable (Compiler Abstraction is specific per build scenario)

[BSW172] Compatibility and documentation of scheduling strategy




R3.1 Rev 0001

7 Analysis This chapter does not contain requirements. It just gives an overview of used keywords and their syntax within different compilers. This analysis is required for a correct and complete specification of methods and keywords and as rationale for those people who doubt the necessity of a compiler abstraction in AUTOSAR. This chapter is no complete overview of existing compilers and platforms and their usage in AUTOSAR. But it shows examples that cover most use cases, from which the concepts specified in the consecutive chapters are derived.

7.1 Keywords for functions

On platforms with memory exceeding the addressable range of the architecture (e.g. S12X with 512k of Flash) the compiler needs to know if a called function is reachable within normal addressing commands (‘near’) or extended/paged addressing commands (‘far’). Compiler analysis for near functions: Compiler Required syntax Cosmic, S12X @near void MyNearFunction(void);

Call of a near function results in a local page call or to a call into direct page. Dependent of compiler settings the compiler controls only the calling convention or allocation and calling convention.

Metrowerks, S12X void __near MyNearFunction(void); Call of a near function results in a local page call or to a call into direct page.

IAR, HCS12 C/C++ void __non_banked MyNearFunction (void); Tasking, ST10 void _near MyNearFunction (void);

_near void MyNearFunction (void); Call of a near function results in a local segment code access (relevant in large model).

Tasking, TC1796 void MyNearFunction (void); (No keywords required)

Greenhills, V850 void MyNearFunction (void); (No keywords required)

ADS, ST30 void MyNearFunction (void); (No keywords required)

DIABDATA, MPC5554 void MyNearFunction (void); (No keywords required)



R3.1 Rev 0001

Compiler analysis for far functions: Compiler Required syntax Cosmic, S12X @far void MyFarFunction(void);

Dependent of compiler settings the compiler controls only the calling convention or allocation and calling convention.

Metrowerks, S12X void __far MyFarFunction(void); IAR, HCS12 C/C++ void __banked MyFarFunction (void); Tasking, ST10 void _huge MyFarFunction (void);

_huge void MyFarFunction (void); Tasking, TC1796 void MyFarFunction (void);

(No keywords required) Greenhills, V850 void MyFarFunction (void);

(No keywords required) ADS, ST30 void MyFarFunction (void);

(No keywords required) DIABDATA, MPC5554 void MyFarFunction (void);

(No keywords required)

7.2 Keywords for pointers

On platforms with memory exceeding the addressable range of the architecture (e.g. S12X with 512k of Flash) the compiler needs to know if data referenced by a pointer is accessible by normal addressing commands (‘near’) or extended/paged addressing commands (‘far’). Compiler analysis for near pointers pointing to variable data in RAM (use case: pointer to data buffer where data has to be copied to): Compiler Required syntax Cosmic, S12X @near uint8* MyNearPointer; Metrowerks, S12X uint8* __near MyNearPointer; IAR, HCS12 C/C++ uint8* __data16 MyNearPointer; Tasking, ST10 _near uint8* MyNearPointer; Tasking, TC1796 uint8* MyNearPointer;

(No keywords required) Greenhills, V850 uint8* MyNearPointer

(No keywords required) ADS, ST30 uint8* MyNearPointer

(No keywords required) DIABDATA, MPC5554 uint8* MyNearPointer

(No keywords required)



R3.1 Rev 0001

Compiler analysis for far pointers pointing to variable data in RAM: Compiler Required syntax Cosmic, S12X @far uint8* MyFarPointer; Metrowerks, S12X uint8* __far MyFarPointer; IAR, HCS12 C/C++ (Information not available yet) Tasking, ST10 _far uint8* MyFarPointer; /*14 bit arithmetic*/

_huge uint8* MyFarPointer; /*24 bit arithmetic*/_shuge uint8* MyFarPointer; /*16 bit arithmetic*//* My personal note: CRAZY */

Tasking, TC1796 uint8* MyFarPointer; (No keywords required)

Greenhills, V850 uint8* MyFarPointer (No keywords required)

ADS, ST30 uint8* MyFarPointer (No keywords required)

DIABDATA, MPC5554 uint8* MyFarPointer (No keywords required)

Compiler analysis for near pointers pointing to constant data in RAM (use case pointer to data buffer where data has to be read from): Compiler Required syntax Cosmic, S12X @near uint8* MyNearPointer;

(Results in access of direct memory area) Metrowerks, S12X const uint8* __near MyNearPointer;

(Results in access of direct memory area) IAR, HCS12 C/C++ const uint8* MyNearPointer;

(Results in access of direct memory area) Tasking, ST10 const _near uint8* MyNearPointer; Tasking, TC1796 const _near uint8* MyNearPointer; Greenhills, V850 const uint8* MyNearPointer

(No additional keywords required) ADS, ST30 const uint8* MyNearPointer

(No additional keywords required) DIABDATA, MPC5554 const uint8* MyNearPointer

(No additional keywords required) Compiler analysis for far pointers pointing to constant data in RAM: Compiler Required syntax Cosmic, S12X @far uint8* MyFarPointer; Metrowerks, S12X const uint8* __far MyFarPointer; IAR, HCS12 C/C++ (Information not available yet) Tasking, ST10 const _far uint8* MyFarPointer; Tasking, TC1796 uint8* MyFarPointer;

(No keywords required) Greenhills, V850 const uint8* MyFarPointer

(No additional keywords required) ADS, ST30 const uint8* MyFarPointer

(No additional keywords required) DIABDATA, MPC5554 const uint8* MyFarPointer

(No additional keywords required)



R3.1 Rev 0001

Compiler analysis for near pointers pointing to data in ROM (use case pointer to display data in ROM passed to SPI Driver): Compiler Required syntax Cosmic, S12X const uint8* MyNearPointer;

(Without near keyword because this is by default near!)Metrowerks, S12X const uint8* __near MyNearPointer; IAR, HCS12 C/C++ const uint8* MyNearPointer;

(Without near keyword because this is by default near!)Tasking, ST10 const _near uint8* MyNearPointer; Tasking, TC1796 const uint8* MyNearPointer;

(No keywords required) Greenhills, V850 const uint8* MyNearPointer

(No additional keywords required) ADS, ST30 const uint8* MyNearPointer

(No additional keywords required) DIABDATA, MPC5554 const uint8* MyNearPointer

(No additional keywords required) Compiler analysis for far pointers pointing to constant data in ROM: Compiler Required syntax Cosmic, S12X not possible Metrowerks, S12X const uint8* __far MyFarPointer; IAR, HCS12 C/C++ Access function and the banked constant data are located in the same

bank: const uint8* MyFarPointer; but caller shall use the __address_24_of macro Access function is located in non-banked memory: PPAGE register has to be handled manually Access function and the banked constant data are located in different banks: Not possible

Tasking, ST10 const _far uint8* MyFarPointer; Tasking, TC1796 const uint8* MyFarPointer;

(No keywords required) Greenhills, V850 const uint8* MyFarPointer

(No additional keywords required) ADS, ST30 const uint8* MyFarPointer

(No additional keywords required) DIABDATA, MPC5554 const uint8* MyFarPointer

(No additional keywords required) The HW architecture of the S12X supports different paging mechanisms with different limitations e.g. supported instruction set or pointer distance. Therefore the IAR, HCS12 C/C++ and the Cosmic, S12X compilers are limited in the usage of generic pointers applicable for the whole memory area because of the expected code overhead.



R3.1 Rev 0001

Conclusion: These vendors should adapt their compilers, because a generic SW architecture as described by AUTOSAR cannot be adjusted in every case to the platform specific optimal solution. Compiler analysis for pointers, where the symbol of the pointer itself is placed in near-memory: Compiler Required syntax Cosmic, S12X uint8* @near MyPointerInNear; Metrowerks, S12X __near uint8* MyPointerInNear; Tasking, ST10 uint8* _near MyPointerInNear; Tasking, TC1796 uint8* MyPointerInNear;

(No keywords required) Greenhills, V850 uint8* MyPointerInNear

(No keywords required) ADS, ST30 uint8* MyPointerInNear

(No keywords required) DIABDATA, MPC5554 uint8* MyPointerInNear

(No keywords required) Compiler analysis for pointers, where the symbol of the pointer itself is placed in far-memory: Compiler Required syntax Cosmic, S12X uint8* @far MyPointerInFar; Metrowerks, S12X __far uint8* MyPointerInFar; Tasking, ST10 uint8* _far MyPointerInFar; Tasking, TC1796 uint8* MyPointerInFar;

(No keywords required) Greenhills, V850 uint8* MyPointerInFar

(No keywords required) ADS, ST30 uint8* MyPointerInFar

(No keywords required) DIABDATA, MPC5554 uint8* MyPointerInFar

(No keywords required) The examples above lead to the conclusion, that for definition of a pointer it is not sufficient to specify only one memory class. Instead, a combination of two memory classes, one for the pointer’s ‘distance’ and one for the pointer’s symbol itself, is possible, e.g.: /* Tasking ST10, far-pointer in near memory * (both content and pointer in RAM) */ _far uint8* _near MyFarPointerInNear; Compiler analysis for function pointers: Compiler Required syntax Cosmic, S12X @near void (* const Irq_InterruptVectorTable[])(void)

Call of a near function results in an interpage call or to a call into direct page:



R3.1 Rev 0001

Compiler Required syntax Metrowerks, S12X void (*const __near Irq_InterruptVectorTable[]) (void)

Call of a near function results in an interpage call or to a call into direct page: Near functions and far functions are not compatible because of other ret-statements:

IAR, HCS12 C/C++ __non_banked void (* const Irq_InterruptVectorTable[])(void) Casting from __non_banked to __banked is performed through zero extension: Casting from __banked to __non_banked is an illegal operation.

Tasking, ST10 _far void (*NvM_AsyncCbkPtrType) (NvM_ModuleIdType ModuleId, NvM_ServiceIdType ServiceId ) Call of a near function results in a local segment code access (relevant in large model):

Tasking, TC1796 void (*NvM_AsyncCbkPtrType) (NvM_ModuleIdType ModuleId, NvM_ServiceIdType ServiceId ) (No additional keywords required)

Greenhills, V850 void (*NvM_AsyncCbkPtrType) (NvM_ModuleIdType ModuleId, NvM_ServiceIdType ServiceId ) (No additional keywords required)

ADS, ST30 void (*NvM_AsyncCbkPtrType) (NvM_ModuleIdType ModuleId, NvM_ServiceIdType ServiceId ) (No additional keywords required)

DIABDATA, MPC5554 void (*NvM_AsyncCbkPtrType) (NvM_ModuleIdType ModuleId, NvM_ServiceIdType ServiceId ) (No additional keywords required)



R3.1 Rev 0001

8 Functional specification

8.1 General issues

COMPILER003: For each compiler and platform an own compiler abstraction has to be provided.

8.2 Contents of Compiler.h

COMPILER004: The file name of the compiler abstraction shall be ‘Compiler.h’. COMPILER053: The file Compiler.h shall contain the definitions and macros specified in chapter 9. Those are fix for one specific compiler and platform. COMPILER005: If a compiler does not require or support the usage of special keywords; the corresponding macros specified by this specification shall be provided as empty definitions or definitions without effect. Example: #define FUNC(type, memclass) type /* not required for DIABDATA */ COMPILER010: The compiler abstraction shall define a symbol for the target compiler according to the following naming convention: _<COMPILERNAME>_C_<PLATFORMNAME>_ Note: These defines can be used to switch between different implementations for different compilers, e.g.

• inline assembler fragments in drivers • special pragmas for memory alignment control • localization of function calls • adaptions to memory models

List of symbols: see COMPILER012 COMPILER030: “Compiler.h” shall provide information of the supported compiler vendor and the applicable compiler version. COMPILER035: The macro parameters memclass and ptrclass shall not be filled with the compiler specific keywords but with one of the configured values in COMPILER040. The rationale is that the module’s implementation shall not be affected when changing a variable’s, a pointer’s or a function’s storage class. COMPILER036: C forbids the use of the far/near-keywords on function local variables (auto-variables). For this reason when using the macros below to allocate a pointer on stack, the memclass-parameter shall be set to AUTOMATIC.



R3.1 Rev 0001

COMPILER047: The Compiler.h header file shall protect itself against multiple inclusions. For instance: #ifndef COMPILER_H #define COMPILER_H /* implementation of Compiler.h */ ... #endif /* COMPILER_H */ There may be only comments outside of the ifndef - endif bracket. COMPILER050: It is allowed to extend the Compiler Abstraction header with vendor specific extensions. Vendor specific extended elements shall contain the AUTOSAR Vendor ID in the name.

8.3 Contents of Compiler_Cfg.h

COMPILER055: The file Compiler_Cfg.h shall contain the module specific parameters (ptrclass and memclass) that are passed to the macros defined in Compiler.h. See COMPILER040 for memory types and required syntax. COMPILER054: Module specific extended elements shall contain the short name of BSW module list in the name.



R3.1 Rev 0001

9 API specification

9.1 Definitions

9.1.1 memory class AUTOMATIC

Define: AUTOMATIC Range: “empty” --

Description: COMPILER046: The memory class AUTOMATIC shall be provided as empty definition, used for the declaration of local pointers.

Caveats: COMPILER040

9.1.2 memory class TYPEDEF

Define: TYPEDEF Range: “empty” --

Description: COMPILER059: The memory class TYPEDEF shall be provided as empty definition. This memory class shall be used within type definitions, where no memory qualifier can be specified. This can be necessary for defining pointer types, with e.g. P2VAR, where the macros require two parameters. First parameter can be specified in the type definition (distance to the memory location referenced by the pointer), but the second one (memory allocation of the pointer itself) cannot be defined at this time. Hence memory class TYPEDEF shall be applied.

Caveats: COMPILER040

9.1.3 STATIC

Define: STATIC Range: static / “empty” --

Description: COMPILER049: The compiler abstraction shall provide the STATIC define for abstraction of compiler keyword static.

Caveats: --

9.1.4 NULL_PTR

Define: NULL_PTR Range: void pointer ((void *)0)

Description: COMPILER051: The compiler abstraction shall provide the NULL_PTR define with a void pointer to zero definition.

Caveats: --



R3.1 Rev 0001

9.1.5 INLINE

Define: INLINE Range: inline/”empty” --

Description: COMPILER057: The compiler abstraction shall provide the INLINE define for abstraction of the keyword inline.

Caveats: --

9.2 Macros for functions

9.2.1 FUNC

Macro name: FUNC Syntax: #define FUNC(rettype, memclass)

rettype return type of the function Parameters (in): memclass classification of the function itself Parameters (out):

none --

Return value: none -- Description: COMPILER001: The compiler abstraction shall define the FUNC macro for the

declaration and definition of functions, that ensures correct syntax of function declarations as required by a specific compiler. COMPILER058: In the parameter list of this macro no further Compiler Abstraction macros shall be nested. Instead use a previously defined type as return type. Example: typedef P2VAR(uint8, AUTOMATIC, _near) NearDataType; FUNC(NearDataType, _far) FarFuncReturnsNearPtr(void);

Caveats: -- Configuration: --

Example (Cosmic, S12X): #define FUNC(rettype, memclass) memclass rettype Required usage for function declaration and definition: FUNC(void, @near) ExampleFunction (void);

9.3 Macros for pointers

9.3.1 P2VAR

Macro name: P2VAR Syntax: #define P2VAR(ptrtype, memclass, ptrclass)

ptrtype type of the referenced variable Parameters (in): memclass classification of the pointer’s variable itself



R3.1 Rev 0001

ptrclass defines the classification of the pointer’s distance Parameters (out):

none --

Return value: none -- Description: COMPILER006: The compiler abstraction shall define the P2VAR macro for the

declaration and definition of pointers in RAM, pointing to variables. The pointer itself is modifiable (e.g. ExamplePtr++). The pointer’s target is modifiable (e.g. *ExamplePtr = 5).

Caveats: -- Configuration: -- Example (Metrowerks, S12X): #define P2VAR(ptrtype, memclass, ptrclass) \ ptrclass ptrtype * memclass Required usage for pointer declaration and definition: #define SPI_APPL_DATA @far #define SPI_VAR_FAST @near P2VAR(uint8, SPI_VAR_FAST, SPI_APPL_DATA) Spi_FastPointerToApplData;

9.3.2 P2CONST

Macro name: P2CONST Syntax: #define P2CONST(ptrtype, memclass, ptrclass)

ptrtype type of the referenced constant memclass classification of the pointer’s variable itself

Parameters (in):

ptrclass defines the classification of the pointer’s distance Parameters (out): none -- Return value: none -- Description: COMPILER013: The compiler abstraction shall define the P2CONST macro for

the declaration and definition of pointers in RAM pointing to constants The pointer itself is modifiable (e.g. ExamplePtr++). The pointer’s target is not modifiable (read only).


Example (Metrowerks, S12X): #define P2CONST(ptrtype, memclass, ptrclass) \ const ptrtype memclass * ptrclass Example (Cosmic, S12X): #define P2CONST(ptrtype, memclass, ptrclass) \ const ptrtype ptrclass * memclass Example (Tasking, ST10): #define P2CONST(ptrtype, memclass, ptrclass) \ const ptrclass ptrtype * memclass



R3.1 Rev 0001

Required usage for pointer declaration and definition: #define EEP_APPL_CONST @far #define EEP_VAR @near P2CONST(Eep_ConfigType, EEP_VAR, EEP_APPL_CONST) Eep_ConfigurationPtr;

9.3.3 CONSTP2VAR

Macro name: CONSTP2VAR Syntax: #define CONSTP2VAR (ptrtype, memclass, ptrclass)

ptrtype type of the referenced variable memclass classification of the pointer’s constant itself

Parameters (in):


none --

Return value: none -- Description: COMPILER031: The compiler abstraction shall define the CONSTP2VAR macro

for the declaration and definition of constant pointers accessing variables. The pointer itself is not modifiable (fix address). The pointer’s target is modifiable (e.g. *ExamplePtr = 18).


Example (Tasking, ST10): #define CONSTP2VAR (ptrtype, memclass, ptrclass) \ ptrclass ptrtype * const memclass Required usage for pointer declaration and definition: /* constant pointer to application data */ CONSTP2VAR (uint8, NVM_VAR, NVM_APPL_DATA) NvM_PointerToRamMirror = Appl_RamMirror;

9.3.4 CONSTP2CONST

Macro name: CONSTP2CONST Syntax: #define CONSTP2CONST(ptrtype, memclass, ptrclass)

ptrtype type of the referenced constant memclass classification of the pointer’s constant itself

Parameters (in):


none --

Return value: none -- Description: COMPILER032: The compiler abstraction shall define the CONSTP2CONST

macro for the declaration and definition of constant pointers accessing constants. The pointer itself is not modifiable (fix address). The pointer’s target is not modifiable (read only).



R3.1 Rev 0001


Example (Tasking, ST10): #define CONSTP2CONST (ptrtype, memclass, ptrclass) \ const memclass ptrtype * const ptrclass Required usage for pointer declaration and definition: #define CAN_PBCFG_CONST @gpage #define CAN_CONST @near /* constant pointer to the constant postbuild configuration data */ CONSTP2CONST (Can_PBCfgType, CAN_CONST, CAN_PBCFG_CONST) Can_PostbuildCfgData = CanPBCfgDataSet;

9.3.5 P2FUNC

Macro name: P2FUNC Syntax: #define P2FUNC(rettype, ptrclass, fctname)

rettype return type of the function ptrclass defines the classification of the pointer’s distance

Parameters (in):

fctname function name respectively name of the defined type Parameters (out):

none --

Return value: none -- Description: COMPILER039: The compiler abstraction shall define the P2FUNC macro for the

type definition of pointers to functions. Caveats: -- Configuration: --

Example (Metrowerks, S12X): define P2FUNC(rettype, ptrclass, fctname)\ rettype (*ptrclass fctname) Example (Cosmic, S12X): #define P2FUNC(rettype, ptrclass, fctname) \ ptrclass rettype (*fctname) Required usage for pointer type declaration: #define EEP_APPL_CONST @far #define EEP_VAR @near typedef P2FUNC (void, NVM_APPL_CODE, NvM_CbkFncPtrType) (void);



R3.1 Rev 0001

9.4 Keywords for constants

9.4.1 CONST

Macro name: CONST Syntax: #define CONST(consttype, memclass)

consttype type of the constant Parameters (in): memclass classification of the constant itself Parameters (out):

none --

Return value: none -- Description: COMPILER023: The compiler abstraction shall define the CONST macro for the

declaration and definition of constants. Caveats: -- Configuration: --

Example (Cosmic, S12X): #define CONST(type, memclass) memclass const type Required usage for declaration and definition: #define NVM_CONST @gpage CONST(uint8, NVM_CONST) NvM_ConfigurationData;

9.5 Keywords for variables

9.5.1 VAR

Macro name: VAR Syntax: #define VAR(vartype, memclass)

vartype type of the variable Parameters (in): memclass classification of the variable itself Parameters (out):

none --

Return value: none -- Description: COMPILER026: The compiler abstraction shall define the VAR macro for the

declaration and definition of variables. Caveats: -- Configuration: --

Example (Tasking, ST10): #define VAR(type, memclass) memclass type Required usage for declaration and definition: #define NVM_FAST_VAR _near



R3.1 Rev 0001

VAR(uint8, NVM_FAST_VAR) NvM_VeryFrequentlyUsedState;



R3.1 Rev 0001

10 Sequence diagrams Not applicable.



R3.1 Rev 0001

11 Configuration specification In general, this chapter defines configuration parameters and their clustering into containers. In order to support the specification, Chapter 11.1 describes fundamentals. We intend to leave Chapter 11.1 in the specification to guarantee comprehension. Chapter 11.2 specifies the structure (containers) and the parameters of this module. Chapter 11.3 specifies published information of this module.

11.1 How to read this chapter

In addition to this section, it is highly recommended to read the documents: AUTOSAR Layered Software Architecture [3]

AUTOSAR ECU Configuration Specification [4]. This document describes the

AUTOSAR configuration methodology and the AUTOSAR configuration metamodel in detail.

The following is only a short survey of the topic and it will not replace the ECU Configuration Specification document.

11.1.1 Configuration and configuration parameters

Configuration parameters define the variability of the generic part(s) of an implementation of a module. This means that only generic or configurable module implementation can be adapted to the environment (software/hardware) in use during system and/or ECU configuration. The configuration of parameters can be achieved at different times during the software process: before compile time, before link time or after build time. In the following, the term “configuration class” (of a parameter) shall be used in order to refer to a specific configuration point in time.



R3.1 Rev 0001

11.1.2 Variants

Variants describe sets of configuration parameters. E.g., variant 1: only pre-compile time configuration parameters; variant 2: mix of pre-compile- and post build time-configuration parameters. In one variant a parameter can only be of one configuration class. Thus describe the possible configuration variants of this module. Each Variant must have a unique name which could be referenced to in later chapters. The maximum number of allowed variants is 3.

11.1.3 Containers

Containers structure the set of configuration parameters. This means: all configuration parameters are kept in containers (sub-) containers can reference (sub-) containers. It is possible to assign a

multiplicity to these references. The multiplicity then defines the possible number of instances of the contained parameters

11.2 Containers and configuration parameters

The following chapters summarize all configuration parameters. The detailed meanings of the parameters describe Chapters 8 and Chapter 9.

11.2.1 Variants

Variant PC (Pre Compile): This is the only variant because all configuration parameters are pre-compile time parameters which influence the compilation process. Each of the different memory classes (memclass) and pointer classes (ptrclass) is represented by a define.



R3.1 Rev 0001

SWS Item COMPILER044 Container Name <MSN>_MemoryAndPointerClasses

Description

This container contains the memory and pointer class parameters of a single module. For each module this container has to be provided. The number of different pointer and memory classes per module depends on the different types of variables, constants and pointers used by the module. It is allowed to extend the classes by module specific classes. The scope of all parameters is ECU because many parameters depend on the parameters of other modules. Examples for this are given in the Annex (starting on page 40). MSN means Module Short Name.

Configuration Parameters

11.2.2 Module Configuration (Memory and pointer classes)

Name <MSN>_CODE Description Configurable memory class for code. Type #define

Unit Compiler specific, refer to chapter 7

Range Compiler specific, refer to chapter 7 e.g. @near, _far Pre-compile x Variant PC

Link time -- -- Configuration Class

Post Build -- -- Scope ECU Dependency MemMap.h Name <MSN>_VAR_NOINIT Description Configurable memory class for all global or static variables that are

never initialized. Type #define




Post Build -- -- Scope ECU Dependency MemMap.h



R3.1 Rev 0001

Name <MSN>_VAR_POWER_ON_INIT Description Configurable memory class for all global or static variables that are

initialized only after power on reset. Type #define




Post Build -- -- Scope ECU Dependency MemMap.h Name <MSN>_VAR_FAST Description Configurable memory class for all global or static variables that have at

least one of the following properties: • accessed bitwise • frequently used • high number of accesses in source code

Type #define


Range Compiler specific, refer to chapter 7 e.g. @near Pre-compile x Variant PC


Post Build -- -- Scope ECU Dependency MemMap.h Name <MSN>_VAR Description Configurable memory class for all global or static variables that are

initialized after every reset. Type #define


Range Compiler specific, refer to chapter 7 e.g. @near Pre-compile x Variant PC


Post Build -- -- Scope ECU Dependency MemMap.h Name <MSN>_CONST Description Configurable memory class for global or static constants. Type #define


Range Compiler specific, refer to chapter 7 Pre-compile x Variant PC





R3.1 Rev 0001

Name <MSN>_APPL_DATA Description Configurable memory class for pointers to application data (expected to

be in RAM or ROM) passed via API. Type #define




Post Build -- -- Scope ECU Dependency MemMap.h Name <MSN>_APPL_CONST Description Configurable memory class for pointers to application constants

(expected to be certainly in ROM, for instance pointer of Init-function) passed via API.

Type #define




Post Build -- -- Scope ECU Dependency MemMap.h Name <MSN>_APPL_CODE Description Configurable memory class for pointers to application functions

(e.g. call back function pointers). Type #define





Included Containers

Container Name Multiplicity Scope / Dependency None -- --

COMPILER042: The file Compiler.h is specific for each build scenario. Therefore there is no standardized configuration interface specified.



R3.1 Rev 0001

11.3 Published Information

Published information contains data defined by the implementer of the SW module that does not change when the module is adapted (i.e. configured) to the actual HW/SW environment. It thus contains version and manufacturer information. The standard common published information like vendorId (<Module>_VENDOR_ID), moduleId (<Module>_MODULE_ID), arMajorVersion (<Module>_AR_MAJOR_VERSION), arMinorVersion (<Module>_ AR_MINOR_VERSION), arPatchVersion (<Module>_ AR_PATCH_VERSION), swMajorVersion (<Module>_SW_MAJOR_VERSION), swMinorVersion (<Module>_ SW_MINOR_VERSION), swPatchVersion (<Module>_ SW_PATCH_VERSION), vendorApiInfix (<Module>_VENDOR_API_INFIX) is provided in the BSW Module Description Template (see [5] Figure 4.1 and Figure 7.1). Additional published parameters are listed below if applicable for this module.



R3.1 Rev 0001

12 Annex

12.1 List of Compiler symbols

COMPILER012: The following table defines target compiler symbols according to COMPILER010. For each compiler supported by AUTOSAR a symbol has to be defined. Platform Compiler Compiler symbol S12X Code Warrior _CODEWARRIOR_C_S12X_ S12X Cosmic _COSMIC_C_S12X_ TC1796 Tasking _TASKING_C_TC1796_ TC1766 Tasking _TASKING_C_TC1766_ ST10 Tasking _TASKING_C_ST10_ ST30 ARM Developer Suite _ADS_C_ST30_ V850 Greenhills _GREENHILLS_C_V850_ MPC5554 Diab Data _DIABDATA_C_MPC5554_

12.2 Requirements on implementations using compiler abstraction

COMPILER040: Each AUTOSAR software module shall support the distinction of at least the following different memory classes and pointer classes. It is allowed to add module specific memory classes and pointer classes as they are mapped and thus are configurable within the Compiler_Cfg.h file. The shortcut ‘MSN’ means ‘module short name of BSW module list’, e.g. ‘EEP’ or ‘CAN’. Memory type

Syntax of memory class (memclass) and pointer class (ptrclass) macro parameter

Comments Located in

Code <MSN>_CODE To be used for code.

Constants <MSN>_CONST To be used for global or static constants

To be used for references on application data (expected to be in RAM or ROM) passed via API

<MSN>_APPL_DATAPointer

To be used for references on application constants (expected to be certainly in ROM, for instance pointer of Init-function) passed via API

<MSN>_APPL_CONSTPointer

To be used for references on application functions. (e.g. call back function pointers)

<MSN>_APPL_CODEPointer

To be used for all global or static variables that are never initialized <MSN>_VAR_NOINITVariables

To be used for all global or static variables that are initialized only after power on reset

<MSN>_VAR_POWER_ON_INITVariables

Compiler_Cfg.h



R3.1 Rev 0001

Memory type

Syntax of memory class (memclass) and pointer class (ptrclass) macro parameter

Comments Located in

To be used for all global or static variables that have at least one of the following properties:

Variables <MSN>_VAR_FAST • accessed bitwise • frequently used • high number of accesses in source

code

To be used for global or static variables that are initialized after every reset. <MSN>_VARVariables

AUTOMATIC Variables To be used for local non static variables Compiler.h

Type Definitions

To be used in type definitions, where no memory qualifier can be specified. TYPEDEF Compiler.h

COMPILER041: Each AUTOSAR software module shall wrap declaration and definition of code, variables, constants and pointer types using the following keyword macros: For instance: native C-API: Std_ReturnType Spi_SetupBuffers ( Spi_ChannelType Channel, const Spi_DataType *SrcDataBufferPtr, Spi_DataType *DesDataBufferPtr, Spi_NumberOfDataType Length ); is encapsulated: FUNC(Std_ReturnType, SPI_CODE) Spi_SetupBuffers ( Spi_ChannelType Channel, P2CONST(Spi_DataType, AUTOMATIC, SPI_APPL_DATA) SrcDataBufferPtr, P2VAR(Spi_DataType, AUTOMATIC, SPI_APPL_DATA,) DesDataBufferPtr, Spi_NumberOfDataType Length );



R3.1 Rev 0001

12.3 Proposed process

To allow development and integration within a multi supplier environment a certain delivery process is indispensable. The following description can be seen as proposal:

AUTOSAR Integrator

Figure 2: Proposal of integration-process

Module source files

Compiler_Cfg.h

MemMap.h

Documents

Package

AUTOSAR Module Suppliers

Step 1: Delivery of basic files

• Receives and checks packages • Implements Source files and documents • Integrates modules • Assigns version and vendor numbers • Integrates the single Compiler_Cfg.h

files into main Compiler_Cfg.h • Implements module specific part of Compiler_Cfg.h and MemMap.h

• Integrates the single MemMap.h files into main MemMap.h • Builds package

Compiler.h Std_Types.h Platform_Types.h Example of MemMap.h

• Configures MemMap.h and Compiler_Cfg.h

Development Environment

Integration Environment

integrates constructs

Compiler_Cfg.h of Module A

Compiler_Cfg.h of Module B

Step 2: Delivery of modules

Compiler_Cfg.h

Compiler_Cfg.h of Module C



R3.1 Rev 0001

12.4 Comprehensive example

This example shows for a single API function where which macro is defined, used and configured. Module: Eep API function: Eep_Read Platform: S12X Compiler: Metrowerks File Eep.c: #include “Std_Types.h” /* This includes also Compiler.h */ FUNC(Std_ReturnType, EEP_CODE) Eep_Read \ ( Eep_AddressType EepromAddress, \ P2VAR(uint8, AUTOMATIC, EEP_APPL_DATA) DataBufferPtr, \ Eep_LengthType Length ) File Compiler.h: #include “Compiler_Cfg.h” #define AUTOMATIC #define FUNC(rettype, memclass) rettype memclass #define P2VAR(ptrtype, memclass, ptrclass) ptrclass ptrtype * memclass File Compiler_Cfg.h: #include “Compiler.h” #define EEP_CODE #define EEP_APPL_DATA @far /* RAM blocks of NvM are in banked RAM */ What are the dependencies? If EEP_APPL_DATA is defined as ‘far’. This means that the pointers to the RAM blocks managed by the NVRAM Manager have to be defined as ‘far’ also. The application can locate RAM mirrors in banked RAM but also in non-banked RAM. The mapping of the RAM blocks to banked RAM is done in MemMap.h. Because the pointers are also passed via Memory Interface and EEPROM Abstraction, their pointer and memory classes must also fit to EEP_APPL_DATA. What would be different on a 32bit platform? Despite the fact that only the S12X has an internal EEPROM, the only thing that would change in terms of compiler abstraction are the definitions in Compiler_Cfg.h. They would change to empty defines: #define EEP_CODE #define EEP_APPL_DATA
