XETK-T2.1 / XETK-T2.2
The XETK-T2.1 and XETK-T2.2 are high speed emulator probes designed for the Infineon Tricore microprocessors family. They can be connected directly to the 100 Mbit/s Ethernet Port of the host PC and support the standard XCP communication protocol.
Configuration Parameters
The following list shows the parameters for the XETK-T2.1 and XETK-T2.2 devices:
Defines the type of the microcontroller used in the ECU.
Defines which amount of (X)ETK device memory is used. This permits the adaption of the (X)ETK device to an ECU memory layout.
- 1 MByte
- 512 KByte
This field describes the Application Modes with which you can run the XETK device:
- RAM Adapter initialized: The XETK device is used as RAM extension for the ECU. If an XETK power failure occurs, the XETK RAM is loaded with the content of the backup flash.
- RAM Adapter not initialized: The XETK device is used as RAM extension for the ECU. If an XETK power failure occurs, the XETK RAM contains random data.
- XETK Mode initialized: The XETK is used as a measurement and calibration device. If an XETK power failure occurs, the XETK RAM is loaded with the content of the backup flash. When running the XETK device together with INCA this mode is set during hardware initialisation.
- XETK Mode not initialized: The XETK is used as a measurement and calibration device, but when a power failure occurs, the XETK RAM contains random data. This mode is only useful for special cases.
If you want to use the XETK device together with INCA, the 'XETK Mode initialized' is the only appropriate mode.
Defines the state of the XETK device after the ECU power 'on'.
- Active: The XETK is enabled at ECU power 'on'. The ECU is able to access the memory of the XETK device.
- Inactive: The XETK is inactive at ECU power 'on'. The ECU needs to activate the XETK before accessing the memory of the XETK device.
Defines the frequency used for the JTAG interface.
(Edit field): Defines the time the XETK device will wait after the ECU reset went off before signaling to the application (e.g. INCA) that the ECU is accessable. The XETK device does not access ECU memory during this wait time. This timeout corresponds to the latency required after ECU reset 'off' until the serial interface can be operated at the defined clock speed.
Defines how the (X)ETK device arbitrates between the connected debugger and its own accesses to the ECU memory.
- Dynamic: The arbitration is carried out dynamically. The used debugger needs to support the arbitration protocol. The (X)ETK device is able to use the serial interface to the ECU while the debugger is connected.
- Static: The arbitration is carried out statically. The used debugger does not need to support the arbitration protocol. The (X)ETK device does not use the serial interface to the ECU except for ECU flash programming.
See also