AUTOSAR-like MCU Driver
From ErikaWiki
(→AUTOSAR-like MCU Driver) |
|||
Line 1: | Line 1: | ||
- | = Compiling = | + | = AUTOSAR-like MCU Driver = |
+ | |||
+ | == Compiling == | ||
To enable AUTOSAR MCU Driver for Texas Instruments Stellaris LM4F232H5QD Evaluation Board with ARM KEIL compiler toolchain, the following <code>EE_OPT</code> attribute is needed in the <code>OS</code> object of the OSEK/VDX configuration: | To enable AUTOSAR MCU Driver for Texas Instruments Stellaris LM4F232H5QD Evaluation Board with ARM KEIL compiler toolchain, the following <code>EE_OPT</code> attribute is needed in the <code>OS</code> object of the OSEK/VDX configuration: |
Revision as of 15:39, 15 July 2013
AUTOSAR-like MCU Driver
Compiling
To enable AUTOSAR MCU Driver for Texas Instruments Stellaris LM4F232H5QD Evaluation Board with ARM KEIL compiler toolchain, the following EE_OPT
attribute is needed in the OS
object of the OSEK/VDX configuration:
EE_OPT = "__AS_MCU_DRIVER__";
The AUTOSAR MCU Driver needs to be configured by C header and source files (Mcu_Cfg.h and Mcu_Cfg.c). These files (for now) need to be manually written.
Templates of these files can be found in contrib/as/arch/stellaris/config/.
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.
Usage examples of the AUTOSAR MCU Driver can be found at examples/cortex_mx/lm4f232xxxx/as