Specifications

2 USING BOUND-T FOR H8/300
2.1 Input formats
Executable file
The target program executable file must be supplied in the standard GCC COFF format, or in
the IAR proprietary UBROF format, or in the standard S-record format. Bound-T can usually
determine the actual file type automatically, by inspecting the file, but the input file type can
also be specified explicitly by means of the command-line options -coff, -srec, or -ubrof.
For COFF files, the "magic number" in the file header is expected to be hexadecimal 8300.
For S-record files, the supported format is defined below in section 2.4. S-record files carry no
symbolic debugging information. To compensate, the addresses of subprograms and variables
can be defined in a separate symbol definition file, introduced with the generic Bound-T option
-symbols [2], or with the H8/300-specific option -sym which (for historical reasons) uses a
slightly different symbol-file format defined in section 2.5 below.
For UBROF files, the last supported version known to work is UBROF 10. Versions before
UBROF 7 may not work well.
Additional code and data file
The command-line option -srec=file can extend the memory image, as defined by the main
target program file, with more code or data from an S-record file. This can be useful if the
running program consists of a fixed ROM part (given in S-record form) and a variable
application program (given as COFF, S-record, or UBROF).
Patch file
Sometimes it is useful to modify or “patch” the target program before analysis. Bound-T
provides the generic option -patch filename that names a file that contains patches to be
applied to the loaded target-program memory image before analysis starts. The format of the
patch file is specific to the target processor. The H8/300 version of Bound-T does not support
patching and thus no patch-file format is defined for patching H8/300 programs.
2.2 Command arguments and options
The generic Bound-T command format, options and arguments apply without modification to
the H8/300 version of Bound-T. Please see the Reference Manual [2] for these.
Bound-T for the H8/300 is usually installed with the name boundt_h8_300, so a typical
command will have the form
boundt_h8_300 <options> <program exe file> <subprogram names>
There are additional H8/300-specific options as explained in the table below, in alphabetical
order. Note that a target-specific option must be written as one string with no embedded
blanks, so the option-name and its numeric or string parameter, if any, are contiguous and
separated only by the equal sign (=) but not by white space. For example, the form
-stack=internal is correct, but -stack = internal is not.
Note that you must always specify the option -device, to choose the H8/300 device (also called
the chip, model or derivative) for which the target program is meant. There is no default
device.
Bound-T for H8/300 Using Bound-T for H8/300 5