ETAS
Hardware Description
FETK-T3.0 - User’s Guide
29
4.10
Trigger Modes
4.10.1
Overview
The FETK-T3.0 supports the following trigger modes:
• Trace triggering by value
The trigger mode "Trace Triggering" uses defined values written into a
defined Trace-address for triggering (see also chapter 4.10.2
on page 29).
• Pinless triggering
The trigger mode "Pinless Triggering" uses the microcontroller’s internal
TRIG register for triggering (see also chapter 4.10.3 on page 29).
• Timer triggering
The trigger mode "Timer Triggering" uses four internal timers of the
FETK for triggering (see also chapter “Timer Triggering” on page 30).
4.10.2
Triggering via Trace Interface
The FETK-T3.0 provides support for up to 255 data trace triggers. The trace
triggers are defined within a section of RAM covered by a trace window. Both
the trace window and trace triggers are defined in the FETK’s configuration
and/or A2L file. A write by the microcontroller software to a trace trigger loca-
tion causes a trace trigger.
The trace trigger events to the FETK-T3.0 are synchronous to the microcontrol-
ler software. Variables assigned to a measurement raster using a trace trigger
are acquired using the trace interface, not via JTAG.
The FETK-T3.0 supports value based data trace trigger:
• triggers for different rasters/events have same address, but use differ-
ent values
• up to 255 value based trace trigger are supported
4.10.3
Pinless Triggering
4.10.3.1 Startup Handshake
Microcontroller registers are used for FETK startup handshake. During this
handshake, ECU software detects the connected FETK by reading and writing
to specific registers and performing basic initializations based on the register
values. When these initializations are done, the handshake is finished with suc-
cess acknowledgment to FETK. Thereafter, if a success acknowledgment is
received by FETK, it starts additional initialization processes (e.g. coldstart,
checksum, downloads, etc).
ECU software must ensure that all memory ECC initializations have been com-
pleted prior to the startup handshake. The DBG_MBIN and DBG_MBOUT regis-
ters are used to generate FETK startup handshake, please contact your local
ETAS representative for further information about the handshake.
After the startup handshake and measure enabled, FETK waits for triggers
from ECU software.
