ETAS
ETK / XETK / FETK Configuration
FETK-T3.0 - User’s Guide
41
6
ETK / XETK / FETK Configuration
The "ETK / XETK / FETK Configuration" chapter describes the FETK-T3.0 hard-
ware configuration.
6.1
Overview
As already mentioned in previous chapters, some project-specific adjustments
are necessary. Configuration data is stored permanently.
Generating a valid configuration data set is supported by the XETK Configura-
tion Tool (XCT). The XCT contains T3.0ormation on all available ETKs,
XETKs, and FETKs. The user is supported through a graphical interface.
The configuration is done in two steps:
1. Generation of the special address offset for the emulation and
measurement data memory.
The location of data areas, measured data output areas, trig-
ger segment addresses etc. are familiar to the ECU software
developer, or can be generated automatically. If an ECU
description database (ASAP, ...) with the corresponding input
exists, these inputs can be downloaded from this database. If
necessary, a plausibility check is performed.
2. Connection of the ETK / XETK / FETK to the ECU.
The ECU hardware developer defines the connection of the
ETK / XETK / FETK to the ECU. The corresponding signals usu-
ally have to be adjusted for each microcontroller. All inputs are
checked for plausibility, to make sure that a valid configuration
is generated.
The XCT can create the following output:
• Direct ETK / XETK / FETK configuration
• Storage of the configuration in a data file
• The corresponding ASAP2 input
The most important outputs are the entries for the ASAP2 file. All A2L defini-
tions necessary for configuring an ETK / XETK / FETK will be created. These
are e.g.:
• Overlay Region definitions
• Memory Segment definitions
• ETK / XETK / FETK configuration features
• Raster definitions
If these parameters are entered correctly in the corresponding ECU description
file, it guarantees that every time the calibration system is started, the ETK /
XETK / FETK is checked for the appropriate configuration.
If necessary, the ETK / XETK / FETK will be configured appropriately to the cor-
responding project.