XETK-S10.0 / XETK-S12.0 / XETK-S14.0
The XETK-S10.0, XETK-S12.0 and XETK-S14.0 are high speed emulator probes especially for the Freescale MPC56xx family of microcontrollers using the Nexus debug interface. They can be connected directly to the 100 Mbit/s Ethernet Port of the host PC and supports the standard XCP communication protocol.
Configuration Parameters
The following list shows the parameters for the devices:
Defines the type of the microcontroller used in the ECU.
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).
Defines the frequency used for the JTAG interface.
Selects the Nexus Trace Clock division factor used by the XETK. The XETK uses a "divide by n" Nexus Trace clock. Trace Clock (MCKO) = System Clock / n.
Selects the Nexus Trace port width used by the XETK.
Determines how the microcontroller’s Nexus Trace port is configured in case of microcontroller FIFO overruns.
- Yes: The microcontroller will stall or delay to avoid trace FIFO overruns.
- No: The microcontroller will not stall or delay to avoid trace FIFO overruns. If the microcontroller software causes a trace FIFO overrun the microcontroller Trace data stream will be missing messages. To use trace triggering it must be guaranteed in microcontroller software to avoid trace FIFO overruns.
Selects how the XETK determines if the microcontroller has completed processing the last JTAG access.
- Pin Available, Block Mode Used: The XETK will monitor the /RDY pin of the microcontroller.
- Pin Not Available, Block Mode Used: The XETK will poll a register of the microcontroller. This should only be used if the microcontroller does not provide the /RDY pin.
Determines whether the XETK uses separate counters for DAQ packets on one side and for commands and responses on the other side.
-
Yes: XETK uses separate counters.
If this parameter is set to 'Yes', you must enable this option for the MC software on the PC as well.
-
No: The XETK uses a common counter.
If this parameter is set to 'No', the PC software may sporadically report counter errors.
Defines how the XETK shall behave if a trace error occurs.
- Continue Measurement: The XETK sends an error event and continues measurement.
- Stop Measurement: The XETK stops the measurement and sends an error event.
Defines how the XETK shall behave if an overload occurs during data processing.
- Drop Data and Continue Measurement: The XETK drops measurement data, sends an error event and continues measurement.
- Stop Measurement: The XETK stops the measurement and sends an error event.
The Flash Programming tab shows a tabular view of the Flash programming settings. These settings, which are stored in 3 different files, can be imported from your PC and apply only to the active configuration. They can not be edited in the XETK Configuration Tool.
Shows the overall version of the Flash configuration (read from the Flash configuration meta data).
Shows the version date of the Flash configuration (read from the Flash configuration meta data).
Shows the version of the Flash driver.
Shows the version of the JPL configuration.
Shows the name of the microcontroller the Flash configuration is intended for.
The microcontroller type displayed on the Hardware Settings tab and on the Flash Configuration tab must match. If they do not match, it will not be possible to download the settings to the XETK device or generate an export file with the A2L entries of the current configuration.
The Bypass Editor provides the possibility to modify the settings for additional bypass methods. For the XETK-S10.0 and XEKT-S12.0, the additional bypass method Synchronized DMA Stim is available.
With this parameter you can enable or disable the bypass method.
- Yes: The bypass method is enabled.
- No: The bypass method is disabled.
Shows the version of the corresponding bypass method supported by the XETK.
If bypass is enabled by setting the parameter Active to "Yes", a valid mailbox address must be entered. The mailbox address must be 4 Byte aligned and different from 0x0.
See also