|
cannot access filename
|
|
The given file cannot be found.
|
|
cannot create filename
|
|
The output file cannot be created. Check that you have space on the output device and that the output file is neither in use nor write-protected.
|
|
cannot find memory for object
|
|
App2Coff needs to locate memory areas to hold a small loader and data for the application (mainly the information needed to load non-root processors). This error indicates that there isn’t a contiguous lump of unallocated memory on the root processor large enough to hold the given object.
|
|
corrupt application file filename
|
|
This is usually the consequence of specifying a file that is not a Diamond application or one that has been corrupted in some way.
|
|
error reading filename
|
|
This is usually the consequence of specifying a file that is not a Diamond application or one that has been corrupted in some way.
|
|
file is too large to be processed
|
|
This is usually the consequence of specifying a file that is not a Diamond application.
|
|
filename references unavailable memory on processor: nnn bytes at address
|
|
Your application (filename) has a reference to some memory that is not available on the given processor. This is most commonly the consequence of specifying a processor type in the App2Coff command that is different from the type given for the root in the configuration file.
|
|
internal error/nnn
|
|
This indicates that an internal consistency check has failed. Rebuild your application and try again. If the error persists, please contact 3L.
|
|
unknown processor type xxx
|
|
You have given a processor type that does not correspond to any of the TIMs that App2Coff supports. Check the spelling of the processor type.
|