VMEBugDoc.tioga
Last edited by Neil Gunther, April 2, 1985 6:14:46 pm PST
VMEBug
CEDAR 5.2 — FOR INTERNAL XEROX USE ONLY
VMEBUG
Provides a simple script interface to assemble Motorola 68000 mnemonics on VMEbus monocomputer boards and the MEX68KECB single board computer.
Neil Gunther
© Copyright 1985 Xerox Corporation. All rights reserved.
VMEBug can be used either interactively in a chat-like mode or more powerfully as a script interpreter. In the script mode, the program reads a prepared text file containing comments, Motorola monitor commands, and Motorola mc68000 assembly mnemonics. These commands and instructions are interpreted or assembled a-line-at-a-time by the monitor ROM on the mc68000 target. All communication is transmitted in upper case independently of the keyboard setting.
Keywords: mc68000, Motorola, VME
XEROX   Xerox Corporation
    Palo Alto Research Center
    3333 Coyote Hill Road
    Palo Alto, California 94304

For Internal Xerox Use Only
Usage
Chat Mode:
This interactive mode is invoked in the same way as with Chat viz. VMEBug dlsName. The currently available remote mc68000 host is identified by the dlsName: LittleWonder. Login, Baud rate setting, and connection sequencing is performed with each instantiation of VMEBug. Individual keystrokes are then transmitted to the mc68000 target via the DLS.

Script Mode: 
This mode. is invoked by the use of the input redirection character < in the command line followed immediately (i.e. no space) by the (arbitrary) script filename. Hence, VMEBug dlsName <File.script will cause the file File.script to be read and transmitted to the remote host via the dls. NOTE: All comment fields, denoted by a leading * in the script, are ignored by VMEBug.


Script Format: 
The allowable content of VMEBug scripts is as follows.

Comments: A line beginning with a * character. Comments are ignored by the program.

Commands: A command line cannot have any leading blanks. A summary of some legal commands is given below.

Instructions: Assembly language instructions must begin with a leading space. Opcodes and operands may be separated by either tabs or spaces.

A sample script is available on:
 /Indigo/CedarHacks5.2/VMEBug/VMEBugSample.script.
Command Summary:
  COMMAND    DESCRIPTION
 
BF <address1> <address2> <word>   Block Memory Fill
BM <address1> <address2> <address3>   Block Memory Move
BR [<address1>]       Set Breakpoint

DF         Display Formatted Registers
DU <address1> <address2>      Dump Memory

GO [<address>]       Begin execution from address(Go)
GT <breakpoint address>      Go until breakpoint is reached

HE      Help (displays commands)

MD <address> <count> [;DI]    Memory Display [disassembled]
MM <address> [;<options>]    Memory Modify [W,L,O,V,N,DI] 


NOBR [<address> <address> ...]   Remove Breakpoints

TR [<count>]      Trace mode

.Rx      Register x; display/set
.A0-.A7      Address Register; display/set
.D0-.D7      Data Register; display/set
.R0-.R6      Rel Offset Register; display/set
.PC      Prgm Counter; display/set
.SR      Status Register; display/set
.SS      Supervisor Stack Pointer
.SU      User Stack Pointer


     
References:
For more detailed information about these and other commands the reader is referred to MEX68KECB User Manual. For further information concerning the mc68000 microprocessor and instruction set see: M68000 Programmer's Reference Manual, 1984