
Calling System Utilities from User Programs
5-11
5
A communication link must exist between the host system and the
MVME167 port 1. (Hardware configuration details are provided in
Connecting Peripherals
on page 3-19.) The file is downloaded from
the host to MVME167 memory by the Load (
LO
) command.
Read the Program from Disk
Another way to enter a program is by reading the program from
disk, using one of the disk commands (
BO
,
BH
,
IOP
). Once the
object code has been loaded into memory, you can set breakpoints
if desired and run the code or trace through it.
Calling System Utilities from User Programs
A convenient way of doing character input/output and many other
useful operations has been provided so that you do not have to
write these routines into the target code. You can access various
167Bug routines via one of the MC68040 TRAP instructions, using
vector #15. Refer to the
Debugging Package for Motorola 68K CISC
CPUs User's Manual
for details on the various TRAP #15 utilities
available and how to invoke them from within a user program.
Preserving the Debugger Operating
Environment
This section explains how to avoid contaminating the operating
environment of the debugger. Topics covered include:
❏
167Bug Vector Table and workspace
❏
Hardware functions
❏
Exception vectors used by 167Bug
Summary of Contents for MVME167 Series
Page 1: ...MVME167 Single Board Computer Installation Guide MVME167IG D4 ...
Page 6: ......
Page 106: ...4 28 Debugger General Information 4 ...
Page 132: ...5 26 Using the 167Bug Debugger 5 ...
Page 146: ...A 14 Configure and Environment Commands A ...
Page 152: ...B 6 Disk Tape Controller Data B ...
Page 160: ...D 6 Troubleshooting the MVME167 Solving Startup Problems D ...
Page 168: ...E 8 EIA 232 D Interconnections E ...