Specifications

Warning Message Meaning and Remedy
Action
If you want to use symbolic names and/or source-code
references, supply a COFF file with a symbol table. The
usual solution is to recompile and relink the target program
with "debug" options, for example -g for the GNU compiler.
Unexpected length N of optional
file header (skipped).
Reasons
The COFF optional file header structure has a different
length (N) than Bound-T expects. This probably means that
the header structure is different from Bound-T's expectation,
so the whole optional header is skipped.
Action
Usually none. If the information in the optional header is
essential for your analysis, please ask Tidorum for help.
Unresolved JSR @Rn/@@aa taken
as no-operation.
Reasons
Bound-T was not able to find a single possible value for the
register operand (Rn), or the indirect memory vector at
address aa, in a dynamic call instruction, and therefore
cannot analyse the callees.
Action
Find out which subprogram or subprograms are meant to be
called and use an assertion to specify these subprograms as
the possible callees for this dynamic call.
Unsure about COFF symbol with
Storage Class = class: symbol
Reasons The COFF symbol-table gives the symbol an unexpected or
unknown storage class so that Bound-T cannot deduce the
nature of the object that the symbol denotes. The COFF file
may be incorrect or may use a different variant of COFF
than Bound-T expects.
Action Usually none. If the nature of the symbol is essential for your
analysis, please ask Tidorum for help.
WCET omits sleeping time for
SLEEP instruction
Reasons
The program contains a SLEEP instruction at this point.
Action
Understand that the WCET bound given for this subprogram
does not include the time spent sleeping.
7.2 Error messages
The following table lists the Bound-T error messages that are specific to the H8/300 or that
have a specific interpretation for this processor. The messages are listed in alphabetical order.
Any italic word or symbol in the message stands for a variable string.
The Bound-T Reference Manual [2] explains the generic error messages, all of which may
appear also when the H8/300 is the target. The Bound-T Assertion Language manual [3]
explains the generic error messages related to assertions.
As Bound-T evolves, the set and form of these messages may change, so this list may be out of
date to some extent. However, we have tried to make the messages clear enough to be
understood even without explanation. Feel free to ask Tidorum for an explanation of any
Bound-T output that seems obscure.
38 Error messages Bound-T for H8/300