Root element containing the whole Tier-1 Project Helper type (generic version info). Meta information about the project Mandatory for OTP scenarios µC core of the ECU Display identifier of related core Startup address of first instruction executed on related core Option strings that are passed straight through to the OEM tool, untouched Identifier of the ECU µC family: e.g., Tricore, MPC5xxx, V85x etc. Identifier of the ECU µC Container for all the measurements in the ECU Container for all the contexts in the ECU Container for all the processes in the ECU. Option strings that are passed straight through to OEM tool, untouched. Name of symbol, i.e., name of a function, variable, segment, etc. Address in ECU memory. TBD: Remove address information from Measurements, Process, MemorySections, Core, Patches, etc. Replace by means of symbolRef Information. Size in ECU memory Bits in ECU memory Name of the context Unique numeric identifier Priority of context. Higher value indicates higher priority. The period of this context milliseconds An optional comment for describing the context Variable's A2L identifier as it appears in the ECU's ASAM MCD-2MC file States if the OEM is allowed to hook this measurement. Default: true; States if the OEM is allowed to use this measurement as an input to an on-target bypass function. Default: true; Address in ECU memory. If no address is specified, the address is applied from a dedicated symbol entry or the A2L file. A2L data type Lowest valid value for argument Highest valid value for argument Bits in memory location representing the value True: Variable is visible in Tool False: Variable is hidden Default: True Reference to computation method (name of computation method) Array's A2L identifier as it appears in the ECU's ASAM MCD-2MC file States if the OEM is allowed to hook this measurement. Default: true; States if the OEM is allowed to use this measurement as an input to an on-target bypass function. Default: true; Address in ECU memory. Possibly overrides A2L address. If no address is specified, the address is applied from a dedicated symbol entry or the A2L file. A2L data type Lowest valid value for argument Highest valid value for argument Number of DataType elements True: Variable is visible in Tool False: Variable is hidden Default: True Reference to computation method (name of computation method) Function argument specification Specifies the arguments to be provided when calling the process Name of argument C data type of argument Lowest valid value for argument Highest valid value for argument Specifies the implied references to variables and subprocesses Variable read by the process Identifier of the variable/array/array element (or copy) to which the process writes Address of related read access opcode Variable written by the process Identifier of the variable/array/array element (or copy) to which the process writes Address of related write access opcode Processes called by the process Identifier of the process called by the current process Address of related function call opcode Option strings that are passed straight through to the OEM tool, untouched Name of the process Process's address in ECU memory. If not specified, the address is taken from a dedicated symbol defined in the symbol list. Process's size in bytes. If not specified, the size is taken from a dedicated symbol defined in the symbol list. Override of context period information States if the OEM is allowed to bypass this process States if this process should be visible to the OEM in the GUI An alias to use for this process. If there is an alias, OEMs will never see the real name of the process. They will always see this alias. States if this process is a special process for synchronizing message copies Process can be used for execute OTB code Optional comment about the process The name of the memory section as used by the linker. Address in ECU memory of the section. Size in bytes of the section. The section's purpose. One of: CODE, CONST, RAM, CHARACTERISTICS. Defines the purpose of a segment Segment contains or is intended to be used for µc instructions Special instruction sets used/ to be used by/for the related µC's code segment Name of the instruction set or instruction subset Segment contains or is intended to be used for internal read-only data Segment contains or is intended to be used for calibrateable parameters Segment contains or is intended to be used for dynamically changed memory content and measurements Segment is located in a read-only memory area Segment is located in a random access memory area Segment is free to be used by RPT tool in the context of the purposes above Regular expression used to match variables generated by the RPT tool. If an RPT tool generated variable matches this regex then it will be located in this memory section. Name of the memory section Address in ECU memory of the section. If not specified, the address is taken from a dedicated symbol defined in the symbol list. Size in bytes of the section. If not specified, the size is taken from a dedicated symbol defined in the symbol list. Optional comma separated section properties: e.g., reserved, relocateable, overwrite, got, u8, u16, u32, bigendian, littleendian, flash_ff, flash_00 Name of the core which can access this memory section. If not specified, the memory is accessible by all cores. Specifies whether the copy is read, write, or read/write The context in which the message copy is used A unique identifier Address in ECU memory of the copy. If no address is specified, the address is applied from a dedicated symbol entry or the A2L file. Optional: the copy's bitmask Specifies whether the copy is read, write, or read/write. The context in which the message copy is used The name of the copy Address in ECU memory of the copy. If no address is specified, the address is applied from a dedicated symbol entry or the A2L file. For each process that writes to the variable/array/array element: identifier of the process' HookableVariableProcess or BypassableFunctionProcess. identifier of the variable/array/array element (or copy) to which the process writes. An ECU scalar variable/message that can be hooked. For messages this is the 'master' copy that appears in the ASAM MCD-2MC file. An ECU array variable/message that can be hooked. For messages this is the 'master' copy that appears in the ASAM MCD-2MC file. Added automatically by the Tier-1 tool. The name of the section as given in the A2L file. The SHA256 hash of the segment's data. SHA256 hash of the A2L file. Added automatically by the Tier-1 tool. e.g., ECU name e.g., Tier 1 name Increment this every time the ECU software/hardware is modified and rendered incompatible with existing versions. An ECU memory section. All memory sections in the ECU should be listed. Existing A2L sections will be overwritten. Name of interface, tool or tool vendor Specifies which ECU Processes write to a particular variable/array/array element. Specifies which ECU Processes write to a particular copy of a variable/array/array element. Manually specifies the address of an instruction that writes to a scalar variable. Manually specifies the address of an instruction that writes to an array variable. The version of the schema used by the configuration file Any text can be placed here Text to be shown to users in the OEM tool The password that will be needed to use the OEM tools Name of the service point Unique numeric identifier Begin/End of context ==> evtl. replace via Identification via Variable -> Process -> Context ref Name of the context containing this service point Name of service call function For each context that contains this process Name of a context that contains this process Definition of which content is to be imported from the related files. Default: All content is imported; Import variables information from related file Import function/process information from related file Import segment information from related file Import memory content from related file Path/URL to embedded file: reference distributed binary, A2L, header files, etc. Specifies that collections of scalar measurements are really elements of an array. All contiguous measurements that match this pattern are considered to be elements of an array. If the write is to a specific element in the array, this attribute should contain the index of that element in the array. If the write is to more than one element or to an element that is only decided during runtime, this attribute should be left out. Address of the pseudo array. Size of the pseudo array. Identifies a block of memory that contains an array. Any scalar measurements in this block of memory are really elements of the array. A regular expression used to identify scalar measurements that are really part of an array. Patterns are matched using .NET regular expressions, which are compatible with Perl 5 syntax. Name to be displayed in tool. The location of the patch in ECU memory The maximum length of the patch in bytes The patch content. The following macros are available: $x## inserts a byte with hex value ##. $DATE inserts the date. $DD inserts the day. $MO inserts the month. $YY inserts the year. $TIME inserts the time. $HH inserts the hour. $MI inserts the minute. $SS inserts the second. $USER inserts the current user's name. $PRODUCT inserts the name of the used Tool. $VERSION inserts the Tool version. $DESCRIPTION inserts the description field from the Tier 1 project. Optional description of the patch Optional comma separated patch properties: e.g.,: export, overwrite, endian_little, endian_big The Patch element is used to manually specify a patch to be applied to the ECU's memory The address of an element in the array. The size of an element in the array. Contains the addresses of the elements of an array. Any scalar measurement at one of these addresses is really an element of the array. The value of one of the process's arguments. The arguments should be given in the order they are passed to the process in the C code. Option strings that are passed straight through to OEM tool, untouched. This element is used to tell the tool the values of this process's arguments when it is called. If the process can be called at different times with different argument values, mutliple elements may be used. This element is optional. It is used to provide extra information to the tool to aid variable write detection.