// MiscDebug.doc, HGM, 14-Feb-85  1:54:21

Even if the Misc Board is pretty confused, the machine should still Boot, and put something in the MP when you poke the Boot Button. If it doesn't, check the clocks and Init/ logic on pg 6.

CioTest
  This makes sure that all 6 CIO chips talk to the ZBus. Of course, the Multibus has to mostly work.

SccTest
  This makes sure that all 4 SCC chips talk to the ZBus.

DataTest
  This checks a lot of the data ports comming out of the CIO chips. It needs an echo plug on the dialer port.

LatchTest
  This tests all the logic for latching the info when a BUS timeout happens. The CP, the Misc board, and any Mem Boards need P2 connectors.

DESTest
  This is a good test of the internal ZBus. This also tests the word mode interface to the Multibus.

ClockTest

EERomTest
  BEWARE this is a destructive test.
  The first pass writes 0s. (MP 0-2048)
  The second pass wrotes 1s. (MP 2048-4096)
  The third pass writes the address of the word. (MP 4096-6144)
  Then it falls into a loop checking what the third pass wrote. (MP has dots on.)

TTYTest
  Runs all 8 lines at 9600 in TTY mode. Needs 8 echo plugs.
  Stop it after a while and verify that sent* and recv* are all going, and about the same.
  The clocks should all be flapping if you need to scope them.

SDLCTest
  Runs the first 2 lines at 56KB in SDLC mode. Needs 2 echo plugs.
  Use the 56KB echo plugs instead of the normal ones to test the 56KB path.
  .MR 108 is the number of packets sent on line 0.
  .MR 10A is the number of packets received on line 0.
  .MR 118 is the number of packets sent on line 1.
  .MR 11A is the number of packets received on line 1.
  Packets on line 1 are shorter (.MR 214) than packets on line 0 (.MR 204)
    so there should be more packets going through line 1.

From Oscar (use Chat):

PhoneLine Thrash
  This runs all 8 phone lines in SDLC mode. You need 8 echo plugs.
  The first 2 lines run at 56KB. The other 6 run at 9600.
  All 8 lines should receive as many messages as they send (less 1 or 2). (g is Good, B is Bad.)
  If lines 2 through 7 don't work, either the clock is sick, or the 8030 doesn't work in Sync mode. (TTYTest tested the data paths.)

Test Dialers Noisy
  This flaps all 24 RS366 lines. (You need another echo plug.)
  Use the STOP key when the cursor is in the Chat window to quit.
  (Test Dialers Quietly doesn't print anything.)

DES Fixed Pattern Tests, DES Loop ECB and DES Loop CBC
  These are more DES tests. If they don't work, but Burdock's DESTest worked ok, the chip is probably broken.
  
Test Mesa Clocks
  This is a good test of all the hardware, microcode, and software. (It's leftover from chasing some nasty problems.) The first 3 sections sample the clock and printout the numbers and the differences. If the differences in each clump are not very close, something is fishy. The next section (scanning for Hickups) is looking for cases where the clock goes backwards. The last section compares the time of day clock with the waits for one second as determined by the process ticker. The first column is the number of microseconds in each "second" of waiting. It should be quite close. The other columns are the fine print - look at the code. 

Boot Button
  When you are all done, use the "Boot Button" command to test programmed controled booting. Just watch the MP. It should be obvious.