(error 100): unrecognised command line arguments, try -h or --help for more.

The interface tool has detected that there are command line options which mean nothing to the tool.

(error 101) file 'file name': could not open interface file for reading, 'error message'.

The interface tool could not read the interface file given by 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 102) file 'file name': could not open AST debug file for writing, 'error message'.

The interface tool could not create or write to the first debug file called 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 103) file 'file name': could not open AST debug file for writing, 'error message'.

The interface tool could not create or write to the second debug file called 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 104) file 'file name': could not open code file for writing, 'error message'.

The interface tool could not create or write to the first code file called 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 105) file 'file name': could not open code file for writing, 'error message'.

The interface tool could not create or write to the second code file called file name and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 106) file 'file name': could not open m-script file for writing, 'error message'.

The interface tool could not create or write to the MATLAB m-script file, call file name and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 107) file 'file name': could not open generic ASAP2 file for writing, 'error message'.

The interface tool could not create or write to the generic ASAP2 file called file name and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 108) file 'file name': could not open INCA ASAP2 file for writing, 'error message'.

The interface tool could not create or write to the ETAS INCA ASAP2 file called file name and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 109) file 'file name': could not open Vision ASAP2 file for writing, 'error message'.

The interface tool could not create or write to the ATI Vision ASAP2 file called file name and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 110): at least one command option required an ASAP2 file to be generated but no MAP file or ELF information file was specified. Try -h or --help for more information.

The interface tool has been asked to generate an ASAP2 file but has not been told the MAP or ELF information file to derive the addresses of DDEs.

(error 111): the asap2 naming pattern must be one of 'prefix_name', 'prefix.name', 'prefix.name_prefix', 'name', 'name_prefix'.

The interface tool has been told to transform the DDE names when generating an ASAP2 file, but the interface tool does not understand the transformation required (there are only a few pre-determined transforms).

(error 112): the boolean type must be specified as 'u8' or 'float'.

The interface tool has been told to generate ASAP2 boolean types with a specific type, but the interface tool does not understand the type provided.

(error 113): you may specify a Diab or GCC MAP file OR an ELF information file as input, but not both.

The interface tool has been given more than one of a Diab MAP file, a GCC MAP file, Diab ddump file, or a GCC objdump file as input but does not know which to use. Specify only one MAP file or ELF information file as input.

(error 114): you cannot specify data dictionary generation using --output-elf-contents without also specifying an ELF information file to be read.

Using the command line option --output-elf-contents the interface tool has been told to generate a data dictionary file from the contents of a Diab ddump or GCC objdump file (derived from an ELF file) but no such file has been specified with the --diab-ddumpfile option or --gcc-objfile option.

(error 115) file 'file name': could not open DDE file for writing, 'error message'.

The interface tool could not write to the data dictionary file given by 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again (the file may be read-only or locked by another application).

(error 116) file 'file name': could not open [type of] file for writing, 'error message'.

The interface tool could not create or write to the file specified by 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again (the file may be read-only or locked by another application).

(error 117): you cannot specify address list output using --output-address-list without also specifying a ELF information file to be read.

The interface tool has been told which file to output the address list to, but it has not been told which Diab ddump or GCC objdump file to read this information from.

(error 118): the compiler must be 'diab_5_5_1_0', 'diab_5_8' or 'diab_5_9'.

The interface tool has been told which compiler is being used, but it does not recognise the compiler so identified.

(error 119) file 'file name': could not open output linker file for writing, 'error message'.

The interface tool could not write to the output linker file given by 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again (the file may be read-only or locked by another application).

(error 120): to generate a linker file output you must specify the OpenECU installation base path using the --oe-base-path option.

The interface tool can only output linker file using the --output-linker-file command line option if the --oe-base-path option is also used to specify the path to the OpenECU installation.

(error 121) file 'file name': could not open linker source file for reading, 'error message'.

The interface tool could not read from the linker source file given by 'file name' and the operating system's reason for not being able to do so is given by 'error message'. Correct the reason for failure and try again.

(error 122): the compiler must be specified when outputting a linker file for the 'target name' target.

For any target that supports more than one compiler, the interface tool needs to be passed the compiler id using the --compiler-id command line option when outputting the linker file using the --output-linker-file option.

(error 123): no input program images. Please specify values for --img-app and --img-cal.

In order to use the --output-s-rec option, the options --img-app and --img-cal must be specified.

(error 124): no diab mapfile. please specify value for --diab-mapfile.

In order to use the --output-s-rec option, the option --diab-mapfile must be specified.

(error 125): could not open s-record file for writing.

The tool tried to create the file specified by --output-s-rec , but failed. This often means that the file already exists and is read-only, or the file was specified in a non-existing directory.

(error 126): could not open application image file for reading.

The tool tried to read the file specified by --img-app , but failed. This often means that the file does not exist.

(error 127): could not open calibration image file for reading.

The tool tried to read the file specified by --img-cal, but failed. This often means that the file does not exist.

(error 128): could not open linker file excerpt for reading.

The tool tried to read the file specified by --ld-excerpt-file, but failed. This often means that the file does not exist.

(error 129): cannot check data dictionary entity data types using --check-dde-data-types.

The tool received an error when checking for the ELF file. When using the --check-dde-data-types option, the ELF file must be specified.

(error 130): Unable to validate license.

The tool received an error while verifying the license. Verify that OpenECU is installed correctly with a valid license.