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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

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

W 153: CLASSES control: class ’name’ multiply used.<br />

The class name was used more than once within a CLASSES control.<br />

The first occurrence of the class will be used. Check the CLASSES<br />

control in the invocation.<br />

W 154: CLASSES control: address range ( hexnum, hexnum ) overlaps<br />

another address range in a CLASSES control<br />

The CLASSES controls have overlapping ranges. Check the CLASSES<br />

control in the invocation.<br />

W 155: ASSIGN control: symbol ’name’ not found as an external<br />

The symbol assigned by the ASSIGN control was not found as an<br />

external in one of the objects. Check the invocation.<br />

W 156: ORDER control: section name ’name’ not in group ’name’<br />

The section did not belong to the group mentioned in the ORDER<br />

GROUPS control. The ORDER control will be ignored for this section.<br />

W 157: system stack defined by both SSKDEF directive and SYSSTACK<br />

sections<br />

System stack must be defined by either a SSKDEF directive or<br />

SYSSTACK sections.<br />

W 158: ADDRESSES LINEAR: address hexnum too low<br />

An address lower than 010000h (page 4) for the linear (LDAT) sections<br />

is not allowed. An exception is address 0000000h, which is the default.<br />

W 159: interrupt for this task multiply defined, using interrupt<br />

namenumber<br />

The locater encounters more than one interrupt record in the object file<br />

while the STRICTTASK control is set. Only one interrupt per module is<br />

allowed when this control is set.<br />

The explanation for message W 160 − W 170:<br />

The next messages concern not fitting relocations. The calculated value<br />

does not fit in the number of bits as indicated. Adjust the expression<br />

responsible for the relocation.<br />

Example: using in the assembly a line like<br />

MOV R0, #lab + 20000h<br />

Causes W 161 because lab + 20000h does not fit in 16 bit (1 word)

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

Saved successfully!

Ooh no, something went wrong!