PM866K02處理器模塊,ABB使用流程
輸入和調(diào)試程序有多種方法可以將用戶程序輸入到系統(tǒng)內(nèi)存中處決一種方法是使用內(nèi)存修改(MM)創(chuàng)建程序帶有匯編程序/反匯編程序選項(xiàng)的命令。程序由輸入用戶一次只能使用一行源代碼。輸入每個(gè)源行后然后將目標(biāo)代碼加載到內(nèi)存中。請(qǐng)參閱MVME197BUG 197Bug調(diào)試包用戶手冊(cè),了解完整詳細(xì)信息197Bug匯編器/反匯編器。
PM866K02處理器模塊輸入程序的另一種方法是從主機(jī)下載對(duì)象文件系統(tǒng)程序必須采用S記錄格式(如MVME197BUG 197Bug調(diào)試包用戶手冊(cè)),可能已經(jīng)在主機(jī)系統(tǒng)上組裝或編譯?;蛘?,該程序可能具有先前已使用197Bug MM命令創(chuàng)建,如上所述并使用Dump(DU)命令存儲(chǔ)到主機(jī)。通信鏈路主機(jī)系統(tǒng)和MVME197端口1之間必須存在。(硬件配置詳細(xì)信息位于調(diào)試器的安裝和啟動(dòng)部分本指南的一般信息章節(jié))。該文件是從主機(jī)下載的通過Load(LO)命令連接到MVME197LE內(nèi)存。其他方法是使用其中一個(gè)磁盤從磁盤讀取程序命令(BO、BH、IOP),或從遠(yuǎn)程設(shè)備將程序作為文件讀取網(wǎng)絡(luò)上的計(jì)算機(jī),使用網(wǎng)絡(luò)命令之一,如NIOP。一旦目標(biāo)代碼加載到內(nèi)存中,用戶可以設(shè)置如果需要,設(shè)置斷點(diǎn)并運(yùn)行代碼或跟蹤。從用戶程序調(diào)用系統(tǒng)實(shí)用程序一種方便的字符輸入/輸出方法和許多其他有用的
提供了操作,因此用戶不必編寫這些操作將例程轉(zhuǎn)換為目標(biāo)代碼。用戶可以訪問各種197Bug例程通過其中一個(gè)MC88110陷阱指令,使用向量#496。請(qǐng)參閱MVME197BUG 197Bug調(diào)試包用戶手冊(cè)各種陷阱#496實(shí)用程序可用,以及如何從用戶程序。保留調(diào)試器操作環(huán)境本節(jié)介紹了如何避免污染操作環(huán)境調(diào)試器的。197Bug使用某些MVME197LE車載資源此外,非車載系統(tǒng)內(nèi)存還包含臨時(shí)變量,異常向量等。如果用戶干擾197Bug所依賴的資源,則調(diào)試器的功能可能不可靠或根本不起作用。197Bug矢量表和工作空間調(diào)試器和診斷固件位于閃存中。這個(gè)調(diào)試器還使用前64KB的RAM存儲(chǔ)向量表,可執(zhí)行代碼、變量和堆棧
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