AUTOSAR-like Drivers

From ErikaWiki

Revision as of 17:59, 16 July 2013 by Giuseppe Serano (Talk | contribs)
Jump to: navigation, search

Contents

Synopsis

The picture in the figure below shows the general architecture of AUTOSAR-like Drivers.

AUTOSAR Device Drivers.png

AUTOSAR-like Drivers are meant to be used in the context of a process in which static configuration supported by tools is strongly suggested if not implied.


Each driver specification in AUTOSAR-like includes at the very least the following:

  • Dependencies from other drivers
  • A suggested architecture for the driver files, some of them to be defined with the help of automatic configuration tools
  • A set of driver-specific types
  • A set of driver-specific constants
  • An API consisting of a set of functions, callbacks and notification functions

Configurator RT-Druid Eclipse Plug-in

AUTOSAR-like Drivers need to be statically configured via RT-Druid Eclipse plug-in, available for free download at the EFORMS web page

Plug-in Installation

In order to install the AUTOSAR-like Drivers Configurator plug-in inside RT-Druid Eclipse, you have to select "Install New Software..." menu voice in "Help" menu.

Install New Software.png

In the "Install" dialog window, you have to push "Add..." button.

Install Add.png

In the "Add Repository" dialog window, you have to push "Archive..." button.

Add Repository Archive.png

You have to select the "Repository Archive" containig the Plug-in to install and push "Open" button.

Repository Archive.png

In the "Add Repository" dialog window, you have to push "OK" button.

Add Repository OK.png

In the "Install Details" dialog window, you have to push "Next >" button.

Install Details Next.png

In the "Install" dialog window, you have to check "Driver configurator Erika Enterprise" and click on the "Next >" button.

Install Next.png

In the "Install Review License" dialog window, you have to accept the terms of license agreements and push "Finish" button.

Install Finish.png

Now you have to wait the installation process to finish.

Installing Software Wait.png

In the "Security Warning" dialog window, you have to push "OK" button.

Security Warning.png

In the "Software Updates" dialog window, you have to push "Yes" button to finalize the installation process and restart RT-Druid Eclipse.

Software Updates.png

Now you have AUTOSAR-like Drivers Configurator plug-in installed in RT-Druid Eclipse.

Plug-in Installation Check

In order to check if the AUTOSAR-like Driver Configurator plug-in is installed in RT-Druid Eclipse, you have to select "About Eclipse" menu voice in "Help" menu.

Help About.png

In the "About Eclipse" dialog window, you have to push the "Evidence" button.

About Eclipse Evidence.png

In the "About Eclipse Features" dialog window, you have to check "Driver configurator Erika Enterprise (Core)" and "Evidece EFORMS core" are installed.

About Eclipse Features.png

Supported Drivers

MCU

The MCU driver provides services for basic microcontroller initialization, power down functionality, reset and microcontroller specific functions required by other MCAL [Microcontroller Abstraction Layer] software modules.

PORT

The PORT driver provide services for initializing the whole PORT structure of the microcontroller.

DIO

The DIO Driver abstracts the access to the microcontroller's hardware pins. Furthermore, it allows the grouping of those pins.

SCI

The SCI Driver provides serial communications services.

GPT

The GPT Driver initializes and controls the internal General Purpose Timer(s) of the microcontroller.

DMA

The DMA Driver provides services to offload data transfer tasks from the μC, allowing for more efficient use of the μC and the available bus bandwidth.

SPI

The SPI Driver provides services for reading from and writing to devices connected via SPI busses. It also provides the required mechanism to configure the onchip SPI peripheral.

WDG

The WDG Driver provides services for initialization, changing the operation mode and setting the trigger condition (timeout) of a watchdog device.

Build

To enable AUTOSAR-like Drivers in Erika Enterprise build process, the following EE_OPT attribute is needed in the OS object of the OSEK/VDX configuration:

 EE_OPT = "__AUTOSAR_R4_0__";

AUTOSAR-like Drivers need to be statically configured through the configurator described above. The configuration process shall generate configuration header and source C files that shall be added to Erika Enterprise build process.

The configuration C header files inclusion is done by CFLAGS attribute in the OS object of the OSEK/VDX configuration:

 CFLAGS = "-I<PATH>";

Where <PATH> is the absolute or relative directory path which configuration C header files is stored.

Note: Each AUTOSAR-like Driver must be enabled individually.

Stand-alone Library

To build a stand-alone library (libas.a) containing build-enabled AUTOSAR-like Drivers, the following code is needed in the OS object of the OSEK/VDX configuration:

 EE_OPT = "__ADD_LIBS__";
 LIB = ENABLE {
   NAME = "AUTOSAR";
 };

It's possible to include into library the drivers configurations by the following EE_OPT attribute in the OS object of the OSEK/VDX configuration:

 EE_OPT = "__NO_APP__";

Supported Architectures

Texas Instruments Stellaris LM4F232xxxx with ARM KEIL uVision Compiler Toolchain

Configuration Instatiation

In order to configure AUTOSAR-like Drivers for Texas Instruments Stellaris LM4F232xxxx with ARM KEIL uVision Compiler Toolchain, you have to create an instance of the drivers configuration inside your RT-Druid Eclipse project.

The first step to do this is to right-click on the project folder in the project explorer.

In the first Context-Menu popped-up, you have to choose the "New" menu voice.

In the next Context-Menu popped-up, you have to select the "Other..." menu voice.

Project New Other.png

In the "New" dialog window, you have to expand the "Evidence" folder, select "Erika Driver Configurator" and then push "Next >" button.

New Evidence Driver Configurator.png

In the "Erika Driver Configuration" dialog window, you may change/choose the drivers configuration instance file name and then you have to push "Finish" button.

Erika Driver Configuration File Name.png

The AUTOSAR-like Drivers configuration instance file is now created and ready to be edited.

Erika Driver Configurator Main.png

Configuration Editing

The edit process for AUTOSAR-like Drivers configuration file is related to each individual driver.

Please refer to specific driver documentation.

Configuration Generation

Once you have edited the configuration file for AUTOSAR-like Drivers you wish to use in your application, to generate the configuration header and source C files for all drivers configured, you have to select "Generate Code" menu voice in the "Erika Driver Editor" Menu.

Erika Driver Editor Generate Code.png

The configured AUTOSAR-like drivers configuration header and source C files will be generated in "src-gen" project folder.

Erika Driver configuration Generated.png

Keil uVision Integration

To integrate AUTOSAR-like Drivers for Texas Instruments Stellaris LM4F232xxxx with ARM KEIL uVision Compiler Toolchain in a ARM KEIL uVision application project, it nees:

  • To add a previously builded libas.a (containing drivers configurations) to a Target Sources Group of ARM KEIL uVision Project.
  • To add AUTOSAR Drivers include path (contrib/as/include/) to ARM KEIL uVision C/C++ compiler include paths.
  • To add AUTOSAR Drivers for Texas Instruments Stellaris LM4F232xxxx with ARM KEIL compiler toolchain contrib/as/arch/stellaris/keil/include/ to Keil uVision C/C++ compiler include paths.
  • To add AUTOSAR Drivers configurations for Texas Instruments Stellaris LM4F232xxxx with ARM KEIL uVision Compiler Toolchain include path to ARM KEIL uVision C/C++ compiler include paths.

See also

Personal tools