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.

• • • • • • • •<br />

<strong>Linker</strong>/<strong>Locator</strong> Error Messages H−15<br />

W 505: vector table address at 0hexnumberh not aligned on segment<br />

boundary<br />

The XC16x/Super10 architecture allows the vector table to be located<br />

elsewhere in memory, but it must be at a segment boundary and not in<br />

segment 191. Relocating the vector table to a non−aligned address is<br />

only allowed when using it for debugging purposes. A non−debug<br />

vector table must always be aligned at a segment boundary.<br />

W 506: scaling of vector tables differs between modules<br />

Seperate modules declared a different scaling for the vector table. The<br />

locator will use the largest scaling declared, or the scaling declared on<br />

the command line if that is larger. This warning is only generated when<br />

no scaling is defined on the command−line and two or more modules<br />

declare a different scaling.<br />

W 508: maximum number of configurable groups is 255<br />

W 509: maximum number of configurable classes is 255<br />

W 511: minimum number of configurable groups is 1<br />

W 512: minimum number of configurable classes is 1<br />

W 513: control name is deprecated<br />

This control has no effect anymore. It is supported for backwards<br />

compatibility, but in the future it may cause a syntax error.<br />

W 514: userstack section name is truncated to number bytes<br />

The linker / locater will automatically truncate a userstack section to<br />

the maximum value allowed for this type of section.<br />

W 515: section section is removed, because it is never used<br />

With the smart linking control in effect, the linker/locator tries to<br />

identify sections that are never used. Together with the compiler smart<br />

linking pragma which will put all functions in a seperate section, this<br />

eliminates unused functions from the output file.<br />

W 516: resolving variable, but control control not specified<br />

Some predefined variables must be accompanied by certain controls.<br />

For example, the ?USRSTACK1_TOP predefined variable is an<br />

EXTEND2 architecture variable. The locator will resolve this variable<br />

but other effects of the missing control will not be applied. This may<br />

result in a non−executable output file.

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

Saved successfully!

Ooh no, something went wrong!