Specifications

Error Message Meaning and Remedy
Reasons
The line is too long. Note that blanks and other white-
space characters are included in the length.
Solution
Shorten the line.
No -device was specified
Problem
The command line lacks the option -device=X to choose
the H8/300 device (chip).
Reasons
Missing obligatory option.
Solution
Add the option -device=X to the command line, with
some valid device name X.
No instruction loaded at this address
Problem
The control-flow analysis has given the Program
Counter (PC) a value that points to a memory location
where nothing is loaded; the executable file does not
contain data or code for this address.
Reasons
See the error message "Invalid instruction".
Solution
See the error message "Invalid instruction".
Option argument is not a number: "value" Problem
In a command-line option of the form -keyword=value,
the value is expected to be a number but the actual
value is not a number.
Reasons
Error in the command line.
Solution
Correct the command line.
Parameter reference exceeds caller's
frame
Problem
Bound-T has identified an SP-relative, register-indirect
operand as a reference to a parameter (not a local).
However, the parameter's offset relative to the SP on
entry to this subprogram is so large that the parameter
cannot reside in the caller's stack frame. This violates
the calling protocol that Bound-T understands.
Reasons
Unknown. Perhaps the program uses a novel calling
protocol, or perhaps Bound-T has computed the local
stack height incorrectly in the caller or the callee.
Solution
Please report this problem to Tidorum for analysis.
Patching is not implemented for this
target
Problem
The command line uses the generic option -patch to
specify a patch file. However, patching is not
implemented for the H8/300.
Reasons
Generic option not implemented for this target.
Solution
Remove the -patch option. If you need patching for the
H8/300, ask Tidorum to implement it.
Return by offset X from stange state S
Problem
In this call, the callee is asserted to return to a point
that is offset by X octets from the normal return point
as offered by the caller, but the control-flow state at
the normal return point is the unexpected state S.
Reasons
Probably an error in Bound-T-
Solution
Please report the problem to Tidorum.
Bound-T for H8/300 Error messages 43