PM866K02处理器模块,ABB使用流程
输入和调试程序有多种方法可以将用户程序输入到系统内存中处决一种方法是使用内存修改（MM）创建程序带有汇编程序/反汇编程序选项的命令。程序由输入用户一次只能使用一行源代码。输入每个源行后然后将目标代码加载到内存中。请参阅MVME197BUG 197Bug调试包用户手册，了解完整详细信息197Bug汇编器/反汇编器。
PM866K02处理器模块输入程序的另一种方法是从主机下载对象文件系统程序必须采用S记录格式（如MVME197BUG 197Bug调试包用户手册），可能已经在主机系统上组装或编译。或者，该程序可能具有先前已使用197Bug MM命令创建，如上所述并使用Dump（DU）命令存储到主机。通信链路主机系统和MVME197端口1之间必须存在。（硬件配置详细信息位于调试器的安装和启动部分本指南的一般信息章节）。该文件是从主机下载的通过Load（LO）命令连接到MVME197LE内存。其他方法是使用其中一个磁盘从磁盘读取程序命令（BO、BH、IOP），或从远程设备将程序作为文件读取网络上的计算机，使用网络命令之一，如NIOP。一旦目标代码加载到内存中，用户可以设置如果需要，设置断点并运行代码或跟踪。从用户程序调用系统实用程序一种方便的字符输入/输出方法和许多其他有用的
提供了操作，因此用户不必编写这些操作将例程转换为目标代码。用户可以访问各种197Bug例程通过其中一个MC88110陷阱指令，使用向量#496。请参阅MVME197BUG 197Bug调试包用户手册各种陷阱#496实用程序可用，以及如何从用户程序。保留调试器操作环境本节介绍了如何避免污染操作环境调试器的。197Bug使用某些MVME197LE车载资源此外，非车载系统内存还包含临时变量，异常向量等。如果用户干扰197Bug所依赖的资源，则调试器的功能可能不可靠或根本不起作用。197Bug矢量表和工作空间调试器和诊断固件位于闪存中。这个调试器还使用前64KB的RAM存储向量表，可执行代码、变量和堆栈
Entering and Debugging Programs
There are various ways to enter a user program into system memory for
execution. One way is to create the program using the Memory Modify (MM)
command with the assembler/disassembler option. The program is entered by
the user one source line at a time. After each source line is entered, it is
assembled and the object code is loaded to memory. Refer to the
MVME197BUG 197Bug Debugging Package User’s Manual for complete details
of the 197Bug Assembler/Disassembler.
Another way to enter a program is to download an object file from a host
system. The program must be in S-record format (described in the
MVME197BUG 197Bug Debugging Package User’s Manual) and may have been
assembled or compiled on the host system. Alternately, the program may have
been previously created using the 197Bug MM command as outlined above
and stored to the host using the Dump (DU) command. A communication link
must exist between the host system and the MVME197 port 1. (Hardware
configuration details are in the Installation and Start-up section in the Debugger
General Information chapter of this guide). The file is downloaded from the host
to MVME197LE memory by the Load (LO) command.Other ways are by reading in the program from disk, using one of the disk
commands (BO, BH, IOP), or by reading the program as a file from a remote
computer on a network, using one of the network commands, such as NIOP.
Once the object code has been loaded into memory, the user 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 the user does not have to write these
routines into the target code. The user has access to various 197Bug routines
via one of the MC88110 TRAP instructions, using vector #496. Refer to the
MVME197BUG 197Bug Debugging Package User’s Manual for details on the
various TRAP #496 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. 197Bug uses certain of the MVME197LE onboard resources
and also off-board system memory to contain temporary variables, exception
vectors, etc. If the user disturbs resources upon which 197Bug depends, then
the debugger may function unreliably or not at all.
197Bug Vector Table and Workspace
The debugger and diagnostic firmware resides in the FLASH memory. The
first 64KB of RAM is also used by the debugger for storage of the Vector Table,
executable code, variables, and stack
