Software breakpoint entry into the background
monitor
The background monitor can also be entered via a software breakpoint. The
emulator will respond to any software breakpoint instruction in the code if
breakpoints are enabled, regardless of whether the breakpoint was inserted by the
emulator or not. Breakpoints are enabled by the following command.
bc -e bp
Set breakpoints only on the initial word of an instruction; otherwise, they will not
be executed, and might alter an instruction, unintentionally. The emulator can
place a breakpoint using one of two methods. By default, the emulator will attempt
to modify memory to insert a breakpoint instruction at the address specified. If the
memory at the address specified is ROM or cannot be modified for some other
reason, special hardware resources on the emulator will interject a breakpoint
instruction when that address is fetched.
b
bp <instruction address>
If you suspect a problem occurred during the setting of the breakpoint, you can use
the analyzer to watch the breakpoint being set. The easiest way to do this is to
store-qualify your trace on the address where you are setting the breakpoint. The
trace list will only contain a cycle or two, but you can see what happened when the
emulator accessed this address.
tg any
tsto addr=<instruction address>
b
bp <instruction address>
Line addr,H 68040 Mnemonic
----- -------- ------------------------------------------
0 00000008 $FFFF---- sdata word read
1 00000008 $FFFF---- sdata word read
2 00000008 $FFFF---- sdata word read
3 00000008 $484F---- sdata word write <- breakpoint write
4 00000008 $FFFF---- sdata word read <- verify
5 00000008 $FFFF---- sdata word read
6
Chapter 18: Connecting the Emulator to a Target System
Installing Emulator Features
646
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 ...