Getting started
Copyright IXXAT Automation GmbH
25
IEM Manual, 1.5
src/src/src-externals/BSP
Board support package
Hint:
This Unit should be adapt to your
system, if you use a different µC
src/src/src-externals/CCI/CFG
Configuration file of the controller communi-
cation interface
src/src/src-externals/CCI/Common
API of the CCI
src/src/src-externals/COM
Common and protocol specific type and
structure definitions
src/src/src-externals/CRC
Cyclic redundancy check
src/src/src-externals/DCI
Data communication interface; abstraction to
the physical layer (SHM, SPI)
src/src/src-externals/EMI
API of the EMI containing generic access
functions
src/src/src-externals/FUP
Host Firmware update*
src/src/src-externals/FUPH
Host Firmware update*
src/src/src-externals/SHM
Shared memory unit, provides host access
src/src/src-externals/SPI/<cpu
name>
Serial Peripheral Interface containing device
driver
Hint:
This Unit should be adapt to your
system, if you use a different µC
* EtherCAT not supported at the moment
Figure 2-2: Unit description
2.2
EMI
– Ethernet Module Interface
The EMI Unit provides the required functionality to connect the host application
and the industrial Ethernet protocol on the module. Even though a variety of
protocols are supported, the application programmer should not be charged
with different API’s. Therefore, a unique API with a high abstraction level is
defined. It contains a set of subunits and functions to access general and pro-
tocol specific functionality. The provided functions and services include the ini-
tialization of the module and protocol, the generation and the access of varia-
bles, consistent data transfer mechanisms as well as event and error handling.
Multiple modules are supported. The IEM can be interfaced either via an ad-
dress/data bus (MCI) or a Serial Peripheral Interface (SPI).