BR_XETK-S3.0C
The BR_XETK-S3.0C is a high speed emulator probe designed for the Infineon AURIX microcontroller family (TC4xx). It uses the BroadR-Reach Automotive Ethernet standard, and can be connected to an 100Mbit/s Ethernet Port of a host PC via a suitable media converter.
Configuration Parameters
The following list shows the parameters for the BR_XETK-S3.0C device:
Defines the type of the microcontroller used in the ECU.
Defines the frequency used for the DAP interface.
Defines the DAP (data) pin usage. (Standard 2-PIN bidirectional, Wide 3-PIN bidirectional, Uni 3-PIN unidirectional, UniWide 4-PIN unidirectional).
Selects the polling rate in μs. Typically at least twice as fast as the fastest raster in a measurement.
Defines the hardware handshake timeout in case the ECU did not perform or does not support a hardware handshake.
To force the ECU to perform the handshake, enter -1 (infinite). Using this setting, measurement and calibration is only possible if the ECU performs the specified handshake type.
Otherwise enter a value between 0 and 65534 ms. The value should be set to the earliest time the XETK should access the ECU memory after the ECU is running (both powered and out of reset).
Selects how the XETK controls the ECU watchdog.
- Controlled by ECU: The XETK will not drive the signal.
- Enabled: Enables watchdog control from the XETK debugger connector. The XETK will drive the signal as configured to enable the watchdog when the debugger requests the watchdog to be enabled.
- Disabled: The XETK will drive the signal as configured to disable the watchdog.
Controls which level of the watchdog disable signal shall disable the watchdog.
- Low: Low level shall disable the watchdog.
- High: High Level shall disable the watchdog.
Configures whether the ECU is set into reset during ETK sleep. This may improve the handshake after wakeup.
Selects the method used for the hardware handshake between the ECU and the XETK, as well as for triggering a data acquisition by the ECU.
- Pinless Triggering: Integrated functionality of the debug interface is used for handshake and triggering. No additional microcontroller pins are required.
The (X)ETK has the ability to wake up the ECU by applying voltage to the CalWakeUp pin of the ECU connector. This makes it possible to download the content of the working page and configure a measurement while the ECU is off.
When waking up the ECU via the CalWakeUp pin it can be selected whether the pin is pulled until the microcontroller core voltage (VDDP) is high or whether the pin should be kept on high state until the start-up handshake between ECU and (X)ETK signals to the (X)ETK that the ECU has finished its initialization.
- YES: The CalWakeUp pin will be kept on high state until the start-up handshake between ECU and (X)ETK signals to the (X)ETK that the ECU has finished its initialization.
- NO: The CalWakeUp pin is pulled until the microcontroller core voltage (VDDP) is high.
Selects the signal the (X)ETK will use for ECU standby RAM (working page) power supply supervision.
- ETK Standby Supply: (X)ETK is monitoring the standby supply it provides to the ECU.
- No Standby Supply: (X)ETK is monitoring the standard ECU power supply; the working page is not using a standby supply.
In case Enhanced Coldstart is used it defines the base address of the Distab Checksum array.
- 0xFFFFFFFF: Enhanced Coldstart is not used.
- Any other value: Enhanced Coldstart is used. The value is the base address of Distab Checksum array.
Defines how the ETK will configure the microcontroller’s DAP timeout value. When the microcontroller’s internal bus is under high load, it takes additional time to read or write data using the DAP Interface. To reduce the chance of a DAP timeout, the ETK can be configured to increase the DAP timeout value.
-
On / Auto – Detect: The ETK will increase the timeout, if supported by the microcontroller.
-
Off – The ETK will leave the timeout at the default value defined by the microcontroller.
See also