r rst
6
Verify correct operation of the target system.
An example of a target system that requires an additional reset circuit is one that
normally has RAM starting at address 0, but for the first two bus cycles after reset,
maps ROM to this area instead to provide the inital vectors. If this remapping does
not occur, the system will attempt to fetch these vectors out of RAM, which will
fail.
For systems that require additional circuitry to be initialized by reset, a reset output
from the emulation probe (called reset flying lead) is provided. This reset flying
lead can be connected into your target circuitry to eliminate the need for an
additional step to reset circuitry in your target system. This allows the whole reset
procedure to be controlled by the emulator, automatically.
One additional thing to keep in mind is that your target system can initiate a reset
without the knowledge of the emulator. A reset that is initiated by your target
system will reset the emulator. If the emulator was running your target program at
the time of the reset, then when your system releases reset, the emulator will run as
if an r rst command had been issued. If the emulator was executing in the monitor
at the time of the reset, it will return to the monitor when the reset is released.
Another resetting method that may provide more convenience than the first method
requires use of the monitor. This method works well for target systems such as
those in the example above. This method resets the emulator into the monitor
instead of running the target system program immediately. Once in the monitor,
the initial stack pointer and initial PC can be loaded into the appropriate registers,
and then a run of the target program can be initiated. This method will be
illustrated in the next section.
Chapter 18: Connecting the Emulator to a Target System
Installing Emulator Features
636
Summary of Contents for 64783A
Page 30: ...xxx ...
Page 31: ...Part 1 Quick Start Guide 1 ...
Page 33: ...1 Getting Started 3 ...
Page 70: ...40 ...
Page 75: ...Part 2 Using The Emulator 45 ...
Page 140: ...110 ...
Page 141: ...4 Using the Emulator How to control the processor and view system resources 111 ...
Page 227: ...5 Using the Emulation Bus Analyzer How to record program execution in real time 197 ...
Page 290: ...260 ...
Page 331: ...8 Configuring the Emulator 301 ...
Page 382: ...352 ...
Page 383: ...9 Solving Problems What to do when the emulator doesn t behave as expected 353 ...
Page 397: ...Part 3 Reference 367 ...
Page 399: ...10 Using Memory Management Understanding logical and physical emulation and analysis 369 ...
Page 429: ...11 Emulator Commands The command syntax reference for the emulator softkey interface 399 ...
Page 443: ...copy Chapter 11 Emulator Commands copy 413 ...
Page 451: ...display Chapter 11 Emulator Commands display 421 ...
Page 457: ...DISPLAY MEMORY Chapter 11 Emulator Commands DISPLAY MEMORY 427 ...
Page 461: ...DISPLAY MMU Chapter 11 Emulator Commands DISPLAY MMU 431 ...
Page 464: ...DISPLAY TRACE Chapter 11 Emulator Commands DISPLAY TRACE 434 ...
Page 480: ...modify Chapter 11 Emulator Commands modify 450 ...
Page 501: ...set Chapter 11 Emulator Commands set 471 ...
Page 514: ... SYMB Chapter 11 Emulator Commands SYMB 484 ...
Page 582: ...552 ...
Page 583: ...13 Setting X Resources 553 ...
Page 598: ...568 ...
Page 606: ...576 ...
Page 613: ...16 Specifications and Characteristics 583 ...
Page 627: ...Part 4 Concept Guide 597 ...
Page 629: ...17 X Resources and the Graphical User Interface 599 ...
Page 639: ...Part 5 Installation and Service Guide 609 ...
Page 697: ...19 Installation and Service 667 ...
Page 746: ...Chapter 19 Installation and Service Verifying the Installation 716 ...
Page 755: ...20 Installing Updating Emulator Firmware 725 ...
Page 762: ...732 ...
Page 778: ...748 ...
Page 810: ...X server 554 604 X Window System 54 Index 780 ...