06.02.2013 Views

C166/ST10 Cross-Assembler, Linker/Locator, Utilities ... - Tasking

C166/ST10 Cross-Assembler, Linker/Locator, Utilities ... - Tasking

C166/ST10 Cross-Assembler, Linker/Locator, Utilities ... - Tasking

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

E−4<br />

GSO166 ERRORS<br />

F 015: missing ’argument’ to option: ’−option’<br />

This option requires an argument.<br />

Appendix E<br />

F 016: cannot open file: ’file’<br />

gso166 is unable to read or write to file. Check whether the file exists<br />

and whether you have writing and/or reading rights for this file.<br />

F 017: no SIF files<br />

There are no files to be processed. Specify one or more files.<br />

F 018: missing −o option<br />

You must always specify the −ofile option.<br />

E 019: memory models cannot be mixed (file: ’file’)<br />

All .sif and .gso files must have the same memory model.<br />

E 020: memory limit cannot be greater than: max_size<br />

With the −mspace=size[,rom−part] option, the size of the memory space<br />

was set greater than the maximum value allowed.<br />

E 022: unresolved symbol: ’symbol’ in module: ’module’ (file: ’file’)<br />

No public or global symbol definition was found to resolve the symbol.<br />

E 023: object ’object’ has zero size (module: ’module’, file: ’file’)<br />

After linking the application objects are not allowed to have zero size.<br />

W 024: unreferenced object ’object’ (module: ’module’, file: ’file’)<br />

The object is not referenced by any C−code. Note that references made<br />

by static initializations are not taken into account.<br />

E 025: multiple memory spaces for object ’object’<br />

• An object is allocated in different memory spaces (cross module).<br />

• The memory of an object already allocated in a particular memory<br />

space cannot be overruled by some other memory in a<br />

pre−allocation file.<br />

W 026: duplicate module: ’module’ in file: ’file’ original declaration in<br />

file: ’file’ − ignored<br />

There are two modules with the same name in the application. This<br />

warning typically shows up when one wants to overrule a module in a<br />

library.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!