ETAS
XETK Configuration
BR_XETK-S3.0
-
User Guide
41
6
XETK Configuration
This chapter contains information about the following topics:
• Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
• Configuration Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1
Overview
As already mentioned in previous chapters, some project-specific adjustments
are necessary. Configuration data is stored permanently in a serial Flash.
Generating a valid configuration data set is supported by the "(X)ETK Configu
-
ration Tool" (XCT Tool). The XCT Tool contains information on all available
XETKs. 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 XETK to the ECU.
The ECU hardware developer defines the connection of the
XETK to the ECU. The corresponding signals usually have to be
adjusted for each microcontroller. All inputs are checked for
plausibility, to make sure that a valid configuration is gener
-
ated.
The "(X)ETK Configuration Tool" can create the following output:
• Direct XETK 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 will be created. These are:
• Overlay Region definitions
• Memory Segment definitions
• XETK configuration features
• Raster definitions
• Trace windows (in the case of trace measurement)
If these parameters are entered correctly in the corresponding ECU description
file, it guarantees that every time the calibration system is started, the XETK is
checked for the appropriate configuration. If necessary, the XETK will be con
-
figured appropriately to the corresponding project.
