Memory Layout Editor

The Memory Layout Editor of the (X)ETK Configuration Tool enables you to edit the memory layout of the ECU in an intuitive way.

It is divided into different sub-editors:

In the Memory Segments editor, you can specify the number of memory segments and their use. The memory layout is presented as a table, one row for each memory segment.
In the editor for the Limited Emulation RAM Configuration, you can configure the boundaries for the blocks that shall be used by INCA for emulating calibration variables in the ECU. The blocks used by INCA as default will then be defined in the Calibration Handles editor. During calibration in INCA, these might be changed by INCA to adapt the RAM emulation for the calibrated variables.

This editor is not available for all serial (X)ETKs; whether it is available depends on type and driver version of the (X)ETK device.

For detailed information on limited emulation RAM RAM that is used to replace (overlay) the FLASH memory in order to make the parameter values changeable functionality, see the PDF document "Serial (X)ETK Calibration Concepts — Limited Emulation RAM", which you can find in the Manuals folder of your INCA installation.
The Trace Windows editor is typically only available if you are configuring a serial XETK XETK-S. It lets you define the trace windows Item within the configuration of a trace triggered measurement which determines the range that shall be traced. that will be used by the microcontroller itself for sending data to the connected XETK.

To define additional trace windows or deleting trace window definitions, you can select the commands Add New Trace Window or Delete Trace Window from the context menu of the corresponding table row.

If you are defining several trace windows, you should size the trace windows in such a way that they contain all relevant data without allotting unnecessary memory.

The Calibration Handles editor is typically only available if you are configuring a serial (X)ETK. Here you can define which RAM blocks shall form the working page in the ECU by activating the overlay mechanism.

You can assign emulation addresses for the calibration handles either manually or by selecting Assign All Handles (Fixed Configuration), Assign All Handles (Dynamic Configuration) or Flash Range Specific from the context menu.

Not all combinations of ETK and controller support the Flash Range Specific calibration. An overview of the supported ETKs and controllers as well as information about the configuration can be found here: Flash Range Specific Calibration Method

This assigns emulation addresses to all calibration handles apart from those whose usage is set to Not Available. The emulation addresses are taken from the data memory segments that are defined in the Memory Segments Editor, starting with the smallest start address.

In addition to assigning the emulation addresses, the context menu item Assign All Handles (Dynamic Configuration) sets the usage of all calibration handles (apart from those with the usage Not Available) to Dynamic Configuration. This usage should be selected if you are using INCA as your measurement and calibration tool, because INCA can modify dynamically the emulation addresses as required. If you are working with another measurement, calibration or bypass tool, select Assign All Handles (Fixed Configuration) instead; this will set the usage of the calibration handles to Fixed Configuration.

Fixed configuration is not available for all device types.

You can reset either the selected handle or all handles (apart from those with the usage Not Available) by selecting Reset Handle or Reset All Handles from the context menu. This removes the emulation address from the corresponding field and sets the status of the calibration handle to Not Used.

Editing the entries in the Memory Layout Editor may lead to invalid settings or conflicts between certain settings. In this case the corresponding fields are underlaid in red. To correct the settings, modify the entries until they are not marked as invalid any more, otherwise it will not be possible to download the settings to the (X)ETK device.

Limited Emulation RAM Configuration editor (only available for devices supporting the emulation RAM toolbox and the calibration method Reconfigurable Size)

Calibration Method

Defines which calibration method will be used for dynamic emulation in INCA:

Fixed Size

All blocks have a constant size. Typically it has to be the same size for all blocks.

Reconfigurable Size

The blocks may have individual and changing sizes; these have to comply with the constraints set in this editor. INCA will use these settings to re-configure the calibration handles if this is required by the calibration task.

In case of online access to the X(ETK) device, the changes will be visualized in the XCT after another configuration upload.

If you set the calibration method to Reconfigurable Size, the memory layout must include a memory segment of the type Reconfigurable Emu RAM. If this does not yet exist, you must add this memory segment before you can configure the individual size and location of the calibration handles.

The possible values for handle number and handle size depend on the abilities of the microcontroller used in the ECU.

Calibration Handles Editor (typically only available for serial (X)ETK)

Number, status and size of the calibration handles depend on the microcontroller family and/or type. The list of calibration handles for the supported microcontroller is provided by the XETK Configuration Tool.

Therefore, if you change the microcontroller assignment in the Hardware Settings editor, the current set of calibration handles might become invalid. Via the context menu item Create Default Calibration Handles Set a set of calibration handles matching the currently selected microcontroller can be created.

Status

Shows the status of the calibration handle. This can be 'OK' or error messages:

OK	The plausibility check reports no mistakes.
Overlapping	The calibration handles overlap.
Not Assigned	This region is currently not activated because there is no emulation address assigned. Measurement, calibration and bypass tools can not use this region for the overlay function (exception: INCA).
Unaligned	The relationship between emulation address and size is not correct. For most microcontrollers, the emulation address must be a multiple of the size.
Invalid Address	The address is not located completely in a data segment.
Not used	No emulation address has been set for the handle; the calibration handle is not be used for the RAM emulation.

The calibration handle is only valid if the emulation address is located in a memory segment of the type Data which can be accessed by the (X)ETK, i.e. it must be emulated or of type 'Serial access', but not ignored.

The memory layout is only valid if all memory segments, trace windows and calibration handles have the status 'OK'. You can only execute a download with a valid memory layout to the (X)ETK device. In the case of a memory segment, trace window or calibration handle without the status 'OK' the item Download to is disabled in the Hardware menu.

Usage

Select how the calibration handle is to be used:

Dynamic Configuration

The calibration handles shall be managed by the measurement and calibration tool or the XETK Configuration Tool; the emulation addresses will be assigned by the tool.

Fixed Configuration

A fixed emulation address will be used for the calibration handle.

When you select this usage from the combo-box, a default emulation address is entered; replace this default address by an appropriate emulation address. The emulation address must be located in a memory segment of the type Data.

This setting is not available for all device types.

Not Available

The calibration handle is reserved for other purposes and shall not be used for emulation.

If the Memory Layout Editor contains more than one individual editor (e.g. the Trace Windows Editor and the Calibration Handles Editor), you can minimize or reopen them by clicking on their title bar, or you can modify their size by dragging the title bar up or down.

Note
If the settings are invalid, e.g. because you have changed the microcontroller type after having set up the memory layout or calibration handles, you can check the context menu for commands for creating default settings (e.g. Create Default Memory Layout or Create Default Calibration Handle Set in the Memory Layout Editor). These commands create valid settings which you can use as starting point for further configuration.

Note

If the settings are invalid, e.g. because you have changed the microcontroller type after having set up the memory layout or calibration handles, you can check the context menu for commands for creating default settings (e.g. Create Default Memory Layout or Create Default Calibration Handle Set in the Memory Layout Editor). These commands create valid settings which you can use as starting point for further configuration.

OK	The plausibility check reports no mistakes.
Overlapping	The memory segments overlap.
Unaligned	The memory segment violates one of the microcontroller's requirements on the relationship between size and start address: For parallel (X)ETKs: The memory segment exceeds the upper boundary of the memory area that can be emulated; the exceeding part gets wrapped around (added at the lower end). For serial (X)ETKs: There is a conflict with the microcontroller abilities (e.g. for most microcontrollers, the start address must be divisible by its size).
Inconsistent	The concerned memory segment is invalid, e.g. due to its size.
Unknown	There is no plausibility check possible due to at least one inconsistent memory segment.
Invalid address	The memory segment is using an invalid address (i.e. a memory segment of a certain type has been defined which is physically not existing in the ECU).

Code	Program code located in non-volatile memory
Data	Calibration parameters located in non-volatile memory or in the memory of the (X)ETK device.
Offline Data Flash	Program data allowed only for offline calibration. Checksum calculation considered.
Offline Data ROM	Program data allowed only for offline calibration. Data can no longer be written to the ECU by download. Checksum calculation considered.
Calibration Variables FLASH	This RAM type is only used with INCA AddOn 'Slewing'.
SERAM	This RAM type is only used in the AUTOSAR context.
Reserved	Reserved memory segments; these segments are ignored by data freeze operations.
Reserved (Use File)	The content of the Hex file will be copied to this segment of the Flash memory after the data freeze operation. This option is only available for some serial (X)ETK devices.
Reserved (Use ECU Flash)	The data from this segment will be re-written to the Flash memory after the data freeze operation. This option is only available for some serial (X)ETK devices.
Reserved (Erase)	The contents will be erased from the corresponding segment of the Flash memory after the data freeze operation. This option is only available for some serial (X)ETK devices.
Variables	Measurement data segment located in RAM
Calibration Variables	Memory segment used for adaptive characteristics Variables that can be changed by the ECU. They are used for implementing self-optimizing algorithms in the ECU. Adaptive characteristics are not saved in datasets because they can be changed at any time. Adaptive characteristics can therefore be edited in the experiment environment only if there is calibration access to the ECU.
Reconfigurable EMU RAM	Memory segment used for emulation blocks of reconfigurable size. This option is only available for some serial (X)ETK devices. It may only be used if you are using an (X)ETK device supporting limited emulation RAM with the calibration method Reconfigurable Size.
Not in ECU	Values which are available in the Hex file and the MC tool data base but not in the ECU memory. These values cannot be downloaded or uploaded to or from the ECU memory.

Internal	Memory segment is within the microcontroller of the ECU.
External	Memory segment is located in the external memory of the ECU or in the memory of the (X)ETK device.

OK	The plausibility check reports no mistakes.
Overlapping	The trace windows overlap. Trace windows with the same bus master (e.g. CPU1) must not overlap. If, however, the trace windows refer to different bus masters, overlapping of the address ranges is allowed and does not lead to an error, because they refer to different bus activities.
Not Serial Accessed	The referenced memory segment does not have the access type "Serial".
Inconsistent	The concerned trace window is invalid, e.g. due to its size.
Unknown	There is no plausibility check possible due to at least one inconsistent trace window.

Enable	Enables address based filtering. Only trace messages touching an address used in the measurement are outputted.
Disable	Disables address based filtering. All trace messages inside the trace window are handled.
Ignore	No configuration

OK	The plausibility check reports no errors.
Error	The plausibility check reported an error. Details on the error are given in the tooltip of the error icon and in the application log.