Echelon Neuron - Manual (Page 166)

158 Project Make Errors (PMK)
PMK# Description
4014 The device template file <filename_here> could not be updated; the file might be
locked or write-protected. This does not impact the current build, but the build
status calculator might determine an incorrect build status afterwards. It is
recommended the file is made writeable, or only unconditional builds are
performed. [PMK#4014]
Write failure when updating the device template. This could be caused by a
write-protected or otherwise not writable NodeBuilder device template file
(.nbdt extension). The update failure causes a possible, subsequent, failure
in automatic boot ID management and automatic program ID management.
It is recommended to make the NodeBuilder device template file writable,
or to disable boot ID management and program ID management.
4015 The device template file <name> might be corrupted: property <propertyname>
can not be read correctly. A default value will be used instead [PMK#4015]
A possible file corruption occurred in the NodeBuilder device template file
(.nbdt extension), a property cannot be read correctly. See warning
message for details. Attempt to correct the problem by opening the device
template file in a device template editor and save it again.
4016 Possible data corruption in device template, field <fieldname> [PMK#4016]
See PMK#4015.
4017 Cannot copy file <sourcefile> to <destination>: <reason> [PMK#4017]
A file cannot be copied for reasons given in the actual message. Files are
only copied for convenience; copied files include the linker map or the
application symbol table.
4018 More than one XIF appendix file has been found in the source folder, although
only one can be added to the XIF file. The superfluous file <filename> will be
ignored [PMK#4018]
See documentation for more details about XIF appendix files and
recommended procedures when maintaining legacy applications.
4019 Library <lib> might be required but cannot be found [PMK#4019]
Library <lib> is recommended but may not be required. The build
proceeds. If the build fails with linker errors, reporting unresolved
references, this warning about the missing library file could be related to
the linker failure. Verify that the required library is present in the
expected folder.