MTD 122-250 User Manual Page 4

  • Download
  • Add to my manuals
  • Print
  • Page
    / 15
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 3
For ee9 V1.9, © 2012 William Findlay
This document is !licensed under a Creative Commons Attribution 3.0 License: http://creativecommons.org/licenses/by-nc-sa/3.0/
4
Output on the KDF9’s monitor console, a Friden Flexowriter, was typed in red; input from the computer operators
was typed in black. This is simulated in ee9 by using ANSI-terminal escape sequences to vary the displayed font colour.
The Windows cmd command-line utility does not implement ANSI-terminal escape sequences, so Flexowriter I/O under
Windows is monochrome.
4: TRACING AND LOGGING
Messages that record the progress of the emulation, and details of any errors that were detected, are written to the
interactive console window, along with interactive diagnostics and output intended for the KDF9 Flexowriter. A selection
of these messages is also written to the file KDF9_log.txt. On completion of a run, the final machine state, any
requested core store areas, and any retrospective traces may be written to the log file and to the console window.
It is possible to request the output of certain areas of the KDF9s core store, in a variety of suitable formats. These
printouts can be taken either before the start of execution; or on termination; or at both times, to allow comparisons.
The tracing of instructions is subject to instruction-count and address-range bounds. Instruction executions within
those bounds are traced; those that fall outside the bounds are not.
In the interrupt trace, which is produced only in boot mode, interrupt requests are listed with the privilege state and
priority of the interrupting device; the elapsed time of occurrence (in µs); and the value of ICR, the Instruction Count
Register, which is a count of the number of instructions executed so far. See, e.g.:
Retrospective trace of interrupt requests.
CPL EL. TIME ICR
Ended #03455/2: EDT D 0 @ 69589893 3376330
After #03555/3: EDT D 0 @ 69589259 3376231
After #03555/3: EDT D 0 @ 69588608 3376134
After #02534/3: FLEX D 0 @ 69578533 3374471
...
After earlier interrupts, whose tracing is now lost.
In the peripheral I/O trace, the events shown are transfer initiations and terminations, busy-buffer and store-access
lockouts, and I/O status test operations. Each is listed with the device name, Q-store parameter, privilege state (P for
problem program state and D for Director state) and priority of the transfer; the elapsed time of occurrence of the event;
and the value of ICR. Transfer operations appear twice, once for the initiation (S) and once for the termination (E).
Lockouts appear once, when they happen. A test operation gives the result of the test as a Boolean. See, e.g.:
Retrospective trace of peripheral I/O events.
CPL EL. TIME ICR
Ended #00021/5: POEQ13 TP0 Q#4/#0/#454 P 0 S 1654305064 306451950
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 E 1654305003 306451936
After #00133/1: E#72235M7Q TP0 Store Lockout at #72235 @ 1654295945 306451936
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 S 1654295913 306451936
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 E 1654295913 306451934
After #00132/5: POBQ14 TR1 Store Lockout at #72235 @ 1654294945 306451934
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 S 1654294913 306451934
After #00157/5: POAQ14 TP0 Q#4/#72235/#72235 P 0 E 1654294913 306451912
After #00132/3: PIBQ15 TP0 Store Lockout at #72235 @ 1654222370 306451932
After #00157/5: POAQ14 TP0 Q#4/#72235/#72235 P 0 S 1654222193 306451912
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 E 3907366 1493
After #00133/1: E#72235M7Q TP0 Store Lockout at #72235 @ 2989908 1493
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 S 2989276 1493
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 E 2989276 1491
After #00132/5: POBQ14 TR1 Store Lockout at #72235 @ 2888908 1491
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 S 2888276 1491
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 E 2881121 145
After #00133/1: E#72235M7Q TP0 Store Lockout at #72235 @ 2808475 145
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 S 2808401 145
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 E 2808401 143
After #00132/5: POBQ14 TR1 Store Lockout at #72235 @ 2800475 143
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 S 2800401 143
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 E 2799816 28
After #00133/1: E#72235M7Q TP0 Store Lockout at #72235 @ 2727170 28
After #00132/5: POBQ14 TP0 Q#4/#72235/#72432 P 0 S 2727096 28
After #00020/0: POEQ13 TP0 Q#4/#0/#454 P 0 E 2727096 16
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 E 8162 27
After #00132/5: POBQ14 TP0 Buffer Lockout @ 236 27
After #00132/3: PIBQ15 TR1 Q#2/#72235/#72432 P 0 S 162 27
After #00020/0: POEQ13 TP0 Q#4/#0/#454 P 0 S 96 16
After #00000/0: #000 TR0 Q#1/#0/#17777 P 0 S 0 1
After the start of traced execution.
Total time waiting for unoverlapped I/O to finish = 3980ms.
Page view 3
1 2 3 4 5 6 7 8 9 ... 14 15

Comments to this Manuals

No comments