Hardware Settings Editor
The Hardware Settings Editor provides the possibility to modify hardware configuration parameters. The XETK Configuration Tool displays the hardware configuration parameters of the active configuration.
The Hardware Settings Editor is divided into the following parts:
- The left side of the Hardware Settings Editor shows (X)ETK hardware-related settings that apply to all devices in the project.
- On the right side, you can see a tabular view of hardware configuration parameters and their current values. These parameters are specific to the (X)ETK device type and apply only to the active configuration.
Project-related fields and buttons in the Hardware Settings Editor
Which of the following settings are available depends on the (X)ETK device types that are included in the project.
Enter the base address for the trigger segment.
The trigger segment base address must be located in an emulated memory segment.
Shows the version of the page switch method. If different page switch versions are available, you can select the desired version from the combo-box.
Select from the combo-box whether the working page, the reference page or the last active page shall be activated upon powering the ECU/(X)ETK system.
Select from the combo-box whether Protocol Based or Direct Register Access page switching shall be used by the ECU/(X)ETK system. The (X)ETK device may support only one or both types.
Specify the version number of the mailbox protocol used by the ECU/(X)ETK system.
This parameter is not configurable for all (X)ETK device types. It is only displayed when the Page Switch Method: Page Switch Using entry is set to 'Protocol Based'.
Specify the worst case time, in milliseconds, the ECU software needs to process the page switch mailbox request by the (X)ETK device.
This parameter is not configurable for all (X)ETK device types. It is only displayed when the Page Switch Method: Page Switch Using entry is set to 'Protocol Based'.
Specify the base address of the page switch mailbox location in ECU RAM. The address must be located within an (X)ETK accessible memory segment defined in the Memory Layout Editor.
This parameter is not configurable for all (X)ETK device types. It is only displayed when the Page Switch Method: Page Switch Using entry is set to 'Protocol Based'.
Compatibility ID of the OMD
Overlay Memory Layout Descriptor; a page switch method. Depicts incompatible changes.
Version of the OMD Overlay Memory Layout Descriptor; a page switch method. Depicts compatible changes.
Start address of the OMD Overlay Memory Layout Descriptor; a page switch method.
Maximum length of the OMD Overlay Memory Layout Descriptor; a page switch method.
Number of emulation handles provided by the current ECU.
Version of the OCT Overlay Configuration Table.
Start address of the OCT Overlay Configuration Table for switching to the working page.
Maximum length of the OCT Overlay Configuration Table for switching to the working page.
Start address of the OCT Overlay Configuration Table for switching to the reference page.
Maximum length of the OCT Overlay Configuration Table for switching to the reference page.
This area is not configurable for all (X)ETK device types.
The coldstart handshake is optionally used by the ECU/(X)ETK system to synchronize the measurement configuration process with the ECU software boot process to ensure measurement data is collected from the first events on the ECU.
Specify the base address coldstart handshake location in ECU RAM. The address must be located within an (X)ETK accessible memory segment defined in the Memory Layout Editor. A value of 0x00000000 indicates the coldstart handshake is not used.
Specify the pattern the (X)ETK writes to the pattern address to inform the ECU the (X)ETK has started preparing measurement for the coldstart process. The pattern may be from 1 byte to 4 bytes in length.
Specify the pattern the (X)ETK writes to the pattern address to inform the ECU the (X)ETK has finished preparing measurement for the coldstart process. The length of the pattern should match the length of the wait pattern.
The “Advanced Code Check” configuration is written to the output file in the A2L export.
Specify the address of the pattern in the data area.
Specify the address of the pattern in RAM.
Specify the length of the pattern.
Specify the refresh timeout in ms.
Specify the address of the pattern in the working page.
|
Note |
|---|
|
The Advanced Code Check parameters are not configured in the device. They are evaluated by the Asap driver in INCA. |
This area is not configurable for all (X)ETK device types.
When the ECU supports only limited emulation RAM, it is sometimes necessary to freeze the data (i.e. to flash the ETK data). For security reasons, it is possible to define a Data Freeze safety mailbox in the A2L file (optional). This safety mailbox makes the measurement and calibration tool (e.g. INCA) check if the ECU is in a safe state which allows flashing. In case no safety mailbox is used, the measurement and calibration tool will only execute the operation if the user confirms the ECU safe state or the ECU reset state change.
Specify the base address of the safety mailbox location in ECU RAM. The address must be located within an (X)ETK accessible memory segment defined in the Memory Layout Editor.
Specify the version number of the safety mailbox protocol used by the ECU/(X)ETK system.
The version consist of a magic identifier (byte 2 & 3) and a version containing a major (byte 1) and a minor (byte 0) version digit. The magical identifiers are “4D31” (i. e. 0x4D310100 for version 1.0) for the Safety Mailbox and “4D32” for the Startup Mailbox.
Specify the worst case time, in milliseconds, the ECU software needs to process the safety mailbox request by the (X)ETK device.
Enter the message that shall be displayed by the measurement and calibration tool while waiting for the ECU safe state (optional).
This message will be displayed in addition to the general ETAS message.
Specify the base address of the startup mailbox location in ECU RAM. The address must be located within an (X)ETK accessible memory segment defined in the Memory Layout Editor.
This mailbox handshake can be used to request a different ECU startup behavior from the measurement and calibration application tool during the Data Freeze execution.
This might be necessary to make sure that during the Data Freeze execution, the ECU software will only be entered after the microcontroller has gone into the debug halt mode.
Specify the version number of the startup mailbox protocol used by the ECU/(X)ETK system.
For particularly important Flash segments, you can specify validate and invalidate patterns which are used to indicate whether a dataset is valid after the data freeze procedure.
Specify the pattern which is written to the Flash segment after having successfully erased and rewritten the Flash segement during the data freeze procedure.
The patterns have the format <address><pattern>, i.e. the entry „0x30080000 AAAAAAAAAAAAAAAAAAAAAAAAA“ would write the pattern „AAAAAAAAAAAAAAAAAAAAAAAAA“ to address 0x30080000.
Specify the pattern which is written to the Flash segment before erasing and rewriting the Flash segment during the data freeze procedure
The patterns have the format <address><pattern>, i.e. the entry „0x30080000 AAAAAAAAAAAAAAAAAAAAAAAAA“ would write the pattern „AAAAAAAAAAAAAAAAAAAAAAAAA“ to address 0x30080000.
Device-specific fields and buttons in the Hardware Settings Editor
This function enables you to compare the hardware settings of two loaded configurations. Only configurations of the same (X)ETK type can be compared. The XETK Configuration Tool marks the differences between two configurations in red. Alternatively, you can compare the active configuration in the XETK Configuration Tool with the configuration of a linked (X)ETK device. The Show differences dropdown list affects both, the left and the right side of the Hardware Settings Editor.
A table with three columns is used to display the hardware configuration parameters. The cells in the middle column display the name of the hardware configuration parameters. The cells in the right column list their current values. Click onto the drop down lists to see all possible values.
In case of errors and warnings, the cells in the left column display a status information symbol. When you keep the mouse placed over the concerned symbol, the tool tip function shows system messages, e.g. the reason for an occurring conflict.
|
Symbol |
Reason of occurence |
Consequence/effect |
|
|
The value of this hardware configuration parameter is no valid setting for a possible export via A2L file. |
An A2L export with the option 'ETK_XETK' is not possible. |
|
The setting of this hardware configuration parameter is not compatible to an other setting. |
|
|
|
When comparing two configurations, differences occured in the marked hardware configuration parameter. |
|
|
|
A conflict between the current values of two or more hardware configuration parameters occured. If a |
Via 'mouseover' a suggestion for solving the conflict is shown. (This is matching only for the "passive" conflict partners).
|
|
|
(Additional information): It means that the value of this hardware configuration parameter represents the value 'infinite'. |
|
symbol has a pink background,
it means that this hardware configuration parameter has caused the conflict
("active" conflict partner).
All contents in the parameter table are (X)ETK type dependent. See the XETK and ETK hardware configuration parameters reference.
You can choose in the Mode menu whether Standard Mode, which displays only frequently used parameters, or Extended Mode, which displays all available hardware configuration parameters, is to be used in the Hardware Settings Editor.
Set to
default
This function enables you to reset the hardware configuration parameters to the default values. These default values are preset when creating a new project. The Set to default button affects only the right side of the Hardware Settings Editor.
If you can not find the desired hardware configuration parameters in the Standard Mode, switch to the Extended Mode.
|
|
When you use the extended mode, it is particularly important that you make sure that the configuration contains reasonable and correct data before you download it to the (X)ETK device. Downloading a configuration containing hardware configuration parameters which are not suitable for the ECU may lead to unexpected behavior or could damage the ECU. |
See also
Compare Configuration against (X)ETK Device