AUTOSAR-like MCU Driver

From ErikaWiki

(Difference between revisions)
Jump to: navigation, search
(Compiling)
Line 1: Line 1:
 +
== Synopsis ==
 +
 +
== Configuration ==
 +
== Compiling ==
== Compiling ==
Line 16: Line 20:
Where <code><PATH></code> is the absolute or relative directory path which configuration C source file is stored.
Where <code><PATH></code> is the absolute or relative directory path which configuration C source file is stored.
 +
 +
== Using ==
== Examples ==
== Examples ==
Usage examples of the AUTOSAR-like MCU Driver for can be found at [http://svn.tuxfamily.org/viewvc.cgi/erika_erikae/repos/ee/trunk/ee/examples/cortex_mx/lm4f232xxxx/as  examples/cortex_mx/lm4f232xxxx/as]
Usage examples of the AUTOSAR-like MCU Driver for can be found at [http://svn.tuxfamily.org/viewvc.cgi/erika_erikae/repos/ee/trunk/ee/examples/cortex_mx/lm4f232xxxx/as  examples/cortex_mx/lm4f232xxxx/as]

Revision as of 16:03, 15 July 2013

Contents

Synopsis

Configuration

Compiling

To enable AUTOSAR-like MCU Driver in Erika Enterprise compiler toolchain, the following EE_OPT attribute is needed in the OS object of the OSEK/VDX configuration:

 EE_OPT = "__AS_MCU_DRIVER__";

The configuration C header file 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 file is stored.

Instead the configurations C source file is added to the compilation process by APP_SRC attribute in the CPU_DATA object of the OSEK/VDX configuration:

 APP_SRC = "<PATH>/Mcu_Cfg.c";

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

Using

Examples

Usage examples of the AUTOSAR-like MCU Driver for can be found at examples/cortex_mx/lm4f232xxxx/as

Personal tools