DORADOMIDAS MANUAL24 June 1983byEdward R. FialaXerox Palo Alto Research Center3333 Coyote Hill Rd.Palo Alto, CA. 94304Filed on: [Indigo]DoradoMidas.pressSources on: [Indigo]DoradoMidasManual.dmThis manual describes a largely machine-independent loader/debugger for microprocessors originally developedfor the Maxc2 computer and since used for the Dorado, Dolphin, and M68 microprocessors. This manual isspecialized for the Dorado version of Midas.This manual is the property of Xerox Corporation and is to be used solely for evaluative purposes. No partthereof may be reproduced, stored in a retrieval system, transmited, disseminated, or disclosed to others in anyform or by any means without prior written permission of Xerox.ЪН$├ОJ╠pН [ОE≈Т(Н&1О>&qТ└Н)JО9 rН$1О5UТ·НО/УН"jО-ДН")О+рНyО$╗sТП/НyО#$П6НyОHТ▀ПbТ▄ НyОГТ▒П]Т▓ НyО┤ТП,НyО~Т▐ПbТ░НyОТ┐П!Т└ПOНyОҐТП?ЪЖyо8cKabDorado Midas ManualEdward R. Fiala24 June 19832TABLE OF CONTENTS l.Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.Starting and Exiting from Midas . . . . . . . . . . . . . . . . . . . . 5 4.Midas Display and the Mouse . . . . . . . . . . . . . . . . . . . . . . 6 5.Name-Value Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 6.Command Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 8.Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 9.Syntax of Command-file Actions . . . . . . . . . . . . . . . . . . . .1610.Registers and Memories Known to Midas . . . . . . . . . . . . . .1911.The IM Memory and Virtual Addresses . . . . . . . . . . . . . . .2112.Registers and Memories that Contain Microinstructions . . . .2113.Task-Specific Registers . . . . . . . . . . . . . . . . . . . . . . . . . . .2414.BR Addressing Kludge . . . . . . . . . . . . . . . . . . . . . . . . . . .2415.STKX Kludge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2416.Memory System Registers and Memories . . . . . . . . . . . . . .2417.Memories and Registers Associated With the DMux . . . . . . .2618.Interface Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2719.Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2720.SetClk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2721.Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2822.Loading Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3023.Dump and Cmpr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3124.Brk and Unbrk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3125.Go, SS, Proceed, OS, and Call . . . . . . . . . . . . . . . . . . . . .3226.When Registers are Read/WrittenRestrictions on Continuing . . . . . . . . . . . . . . . . . . . . . . . . .3327.Hardware Failure Reporting . . . . . . . . . . . . . . . . . . . . . . . .3528.Hardware Checkout Facilities . . . . . . . . . . . . . . . . . . . . . . .3629.Parity-Error Scanning . . . . . . . . . . . . . . . . . . . . . . . . . . . .3630.Testing Directly From Midas . . . . . . . . . . . . . . . . . . . . . . .3631.LDRtest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3932.Scope Loop Actions: Fields, RepGo, RepSS, RepT2 . . . . . .4033.HWChk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4034.DMux Consistency Checker . . . . . . . . . . . . . . . . . . . . . . . .4135.Poking: T1, T2, and T3 . . . . . . . . . . . . . . . . . . . . . . . . . .4336.Passive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4337.MIRdebug Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4538.Failure Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4539.Baseboard Microcomputer Stuff . . . . . . . . . . . . . . . . . . . . .4540.Command Files Used With "RdCmds" . . . . . . . . . . . . . . . .4941.DMux Signal Assignments . . . . . . . . . . . . . . . . . . . . . . . . .5042.Hardware Read/Write Methods . . . . . . . . . . . . . . . . . . . . .70НЇОf╙uТ─Н!цqН4]Т НHYОfЯuН жО^оtТ÷Н⌡О[─qТ└Н ПRН;СН⌡ОYІН ПLН;СН⌡ОWКН ПGН;СН⌡ОV!Н ПGН;СН⌡ОTVН ПJН;СН⌡ОR▀Н ПLН;СН⌡ОPаН ПRН;СН⌡ОNЖН ПMН;СН⌡ОM,Н ПFН;СН⌡ОKaН ПAН;СН⌡ОI√Н ПAН;СН⌡ОGлН П=Н;СН⌡ОFН ПMН;СН⌡ОD7Н ПJН;СН⌡ОBlН ПMН;СН⌡О@║Н П@Н;СН⌡О>вН П=Н;СН⌡О=Н ПOН;СН⌡О;AН ПTН;СН⌡О9wН ПTН;СН⌡О7╛Н ПUН;СН⌡О5БН ПNН;СН⌡О4Н ПKН;СН⌡О2LН ПMН;СН⌡О0┌Н ПGН;СН⌡О.ЇН Н О-ПLН;СН⌡О+EН ПJН;СН⌡О){Н ПJН;СН⌡О'╟Н ПMН;СН⌡О%ЕН ПIН;СН⌡О$Н ПSН;СН⌡О"PН П<Н;СН⌡О ├Н ПQН;СН⌡О╩Н ПHН;СН⌡ОПН ПKН;СН⌡О&Н ПPН;СН⌡О[Н ПLН;СН⌡О▒Н ПOН;СН⌡ОфН ПGН;СН⌡ОШН П@Н;СН⌡О1Н ПIН;СН⌡ОfН ПEН;С ZЇT1░YЇwDorado Midas ManualEdward R. Fiala24 June 19833LIST OF TABLESTable l:Command Menu Actions . . . . . . . . . . . . . . . . . . . . .10Table 2:Command File Name-Value Actions . . . . . . . . . . . . .15Table 3:Command File Command Actions . . . . . . . . . . . . . . .16Table 4:Memories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Table 5:Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Table 6:Test Data Pattern Actions . . . . . . . . . . . . . . . . . . . . .37Table 7:Test Items in the Name-Value Display . . . . . . . . . . . .38Table 8:Other Test Actions . . . . . . . . . . . . . . . . . . . . . . . . . .39Table 9:Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Table 10:Control Section DMux Signals . . . . . . . . . . . . . . . . . .50Table 11:BaseBoard DMux Signals . . . . . . . . . . . . . . . . . . . . .52Table 12:Processor DMux Signals . . . . . . . . . . . . . . . . . . . . . .53Table 13:MemC DMux Signals . . . . . . . . . . . . . . . . . . . . . . . .56Table 14:MemD DMux Signals . . . . . . . . . . . . . . . . . . . . . . . .58Table 15:MemX DMux Signals . . . . . . . . . . . . . . . . . . . . . . . .60Table 16:Disk Controller DMux Signals . . . . . . . . . . . . . . . . . .64Table 17:Ethernet Controller DMux Signals . . . . . . . . . . . . . . .65Table 18:IFU DMux Signals . . . . . . . . . . . . . . . . . . . . . . . . . .66Table 19:Display Controller DMux Signals . . . . . . . . . . . . . . . .68Table 20:Other DMux Stuff . . . . . . . . . . . . . . . . . . . . . . . . . .69Figure l:Midas DisplayНЇОf╙uТ─Н!цqН4]Т НHYОfЯuН#О^оtТ÷ Н⌡О[─qТ└НП>Н;СН⌡ОYІНП9Н;СН⌡ОWКНП:Н;СН⌡ОV!НПHН;СН⌡ОTVНПKН;СН⌡ОR▀НПCН;СН⌡ОPаНП<Н;СН⌡ОNЖНПFН;СН⌡ОM,НПEН;СН⌡ОKaНП@Н;СН⌡ОI√НП@Н;СН⌡ОGлНПBН;СН⌡ОFНПAН;СН⌡ОD7НПAН;СН⌡ОBlНПAН;СН⌡О@║НП@Н;СН⌡О>вНП>Н;СН⌡О=НПDН;СН⌡О;AНП?Н;СН⌡О9wНПDН;СН⌡О6( НHЇ4:1░3яиDorado Midas ManualEdward R. Fiala24 June 19834l. IntroductionMidas is a loader/debugger that runs on an Alto and controls its target machine remotely. It canload/dump microprograms assembled by Micro, examine and modify storage, and test hardware inan assortment of ways. Versions exist for Maxc2, Dorado, Dolphin, and M68 microprocessors.Midas is coded about 95% in Bcpl and 5% in assembly language. The Maxc2 version wasimplemented by E. R. Fiala and H. E. Sturgis. The Dorado, Dolphin, and M68 versions consist ofmachine-independent modules implemented by E. Fiala (Overlay and LoadRAM packagesimplemented by L. Deutsch and Alto microcode by E. Taft are also used) and machine-dependentsections implemented by E. Fiala for Dorado; D. Swinehart and P. Baudelaire for M68; and D.Charnley, C. Thacker, B. Rosen, C. Hankins, and E. Fiala for Dolphin.An internal description of Midas is available to anyone interested in adapting Midas to a newhardware system (see [Indigo]MidasInternal.Press).2 Storage RequirementsMidas requires about 500 Alto disk pages, using the following files:Midas.Run~350 pagesMidas.Syms ~40 pagesMidas.Errors ~8 pagesError message strings for Midas swat callsMidas.Programs ~2 pages(Discussed below)Midas.UserPrograms ~2 pages(Discussed below)*.Midas ~2 pages eachCommand files for "RunProg" and "RdCmds" actions*.mbAssorted micro-binary files loaded by command filesMidas.RunProg ~31 pagesBuilt by Midas/IMidas.Dtach ~31 pagesBuilt by Midas/IMidas.FixUps ~2 pagesCreated by Midas/I (used when loading .MB files)Midas.Compare ~2 pagesCreated by Midas/I, written when "Cmpr" action failsDorado Midas can be obtained by loading [Indigo]DoradoMidasRun.Dm andretrieving Midas.Programs with Ftp. You must do Midas/I to initialize Midas on yourdisk after retrieving these. Subsequently, new versions of Midas can be retrieved by executing theD1NewMidas.cm command file from the Alto Executive. Midas runs only under Alto OSversions 17 or later.To setup an Alto disk for use in Dorado microcode development or hardware debugging, you caninstall the Alto OS on a blank disk using the long installation dialog and erase the disk. Whenthis finishes, fetch [Indigo]DoradoUnbugDisk.cm and execute this command file fromthe Alto Executive; it will retrieve Midas and a number of other files that are needed when usingan Alto to control Dorado.НЇОf╙uТ─Н!цqН4]Т НHYОfЯuНЇО^оtТ÷НЇО[]qТ▌П<Т▐П%НЇОY⌠Т┐ПYТ└НЇОWхТ╣ПJТІНЇОTVТзПTНЇОR▀Т─ПGТ│НЇОPаТПHТНЇОNЖТ┤П@Т┬НЇОM,ТёП,ТєП/НЇОKaТПEНЇОGОТ╦ПYТ╧НЇОF$ТП>НЇОA≤tНЇО>&qПDН:О:ьsН░Т─ Н:О9T Н░ Н:О7пН░ Н&√П*Н:О6K Н░ЫPЬЪЗЪ Н&√ТЫЬЗН:О4гН░Т─ Н&√ ТН:О3CН░Т─ЫPЬЪЗЪЫЬЗН&√ЫхЬЪЗЪЫЬЗТП)Н:О1©Н&√П3Н:О0;Н░Т─ Н&√Т Н:О.Ї Н░Т─ Н&√Т Н:О-3Н░Т─ Н&√ТП)Н:О+╞Н░Т─ Н&√ТП-НЇО(`qТ;Т<ПAНЇО&√Т│П5Т┌П'НЇО$кТ├ПHТ┤НЇО#ТГП(ТХП*НЇО!6ТНЇОдТ▀П@Т▄НЇОЫТ═Т║ПJНЇО/Т≤П;Т≥НЇОdТ█П[Т▌НЇО Т hЇS<ПQ╦:Dorado Midas ManualEdward R. Fiala24 June 198353. Starting and Exiting from MidasMidas may be started from the Alto Executive in the following ways:midasstart Midas.midas/iinitialize and fire up Midas. This is about 8 seconds slower than anormal start. /i must be used after any Midas files move or changebecause Midas keeps the FP's (File pointers) in its saved state.Changing any files named in Midas.Programs or Midas.UserPrograms,changing the Alto OS, and changing files named Midas.* all require/i.);midas debugstarts Midas and immediately reads commands from the"Debug.Midas" command fileDorado Midas may attach to any of up to 20 machines accessible through its Diablo Printerinterface. If only one machine is accessible, it immediately connects to it; if more than onemachine is there, it first puts up a menu of accessible serial numbers, and then connects to theone selected by the user. After connection, subsequent actions affect only the connected machine.Although Midas itself can deal with up to 20 machines, the hardware is presently limited to less.It was observed that ringing on the communication cable introduced extra clocks when too manymachines were connected, so Midas couldn't communicate reliably with target machines. ThePARC technicians presently observe a limit of about 6 machines, which seems to work. Nohardware fix is likely to be made for this problem.Midas will seize the hardware only if the connected machine is halted; if running, Midas waits forthe machine to halt or for you to execute "Abort" or "Dtach" actions. "Dtach", equivalent toexiting to the Executive and restarting Midas, also appears in the main command menu and in thesubmenu put up by "Go", so you can start a microprogram running with "Go" on one Dorado,then "Dtach", connect Midas to another machine, and do something else (However, if you Dtachand later reattach to a machine, you will have lost the display configuration and address symbols,which might be inconvenient).Note that there are two different arrangements for the initial Midas display. For botharrangements the left-hand display column shows the principal Dorado registers, and the middlecolumn shows several other items. When you initially attach to a machine, the right-hand columnwill show voltage, temperature, and current readings collected by the baseboard microcomputer;after a "RunProg" action, the right-hand column will show items used by Midas hardware testingactions.To exit from Midas type SHIFT-SWAT (i.e., simultaneously depress the left-hand shift key andthe right-most, lowest unmarked key); this will close any open output files prior to exit anddisconnect the Alto from the Dorado it was controlling. Note that on "Dtach" or exit, if theDorado was running, it will not be disturbed, but if halted, Midas first restores the hardware stateas though it were about to continue, so it will be possible later to reattach and continue a programthat was stopped at a breakpoint.НЇОf╙uТ─Н!цqН4]Т НHYОfЯuНЇО^оtП#НЇО[]qПCН:ОWКНПН:ОVDНПТґТўП'НПОT²Т÷П.Т═НПОRУТЧП,ТЪНПОQNТ┼Т▀П5НПОOїТіП(ТїНПОMЪН:ОLXТ─ НПТцП%ТдНПОJ╠ТНЇОG?ТйП>ТкНЇОEtТхПUТиНЇОC╘ТїП$Т╗П<НЇОAъТ┬Т┴ПSНЇО>mТ≤П#Т≥П>НЇО<╒Т≈Т≤П>НЇО:ьТдПKТеНЇО9 ТйПNТк НЇО7BТП3НЇО3пТ┬ПXТ┴ НЇО2ТўП!Т╞П<НЇО0;Т└П'Т┘П8НЇО.qТ²П7Т·П!НЇО,іТ⌠П3Т■П)НЇО*шТ▒Т▓ПYНЇО)ТНЇО%÷Т ПDТНЇО#тТєП^НЇО" Т┬П5Т┴П+НЇО ?Т╙П^НЇОtТ▓ПMТ⌠НЇО╙НЇО8Т╗П8Т╘П$НЇОmТмПEТнНЇОёТ╦ПVТ╧НЇОьТ┼Т▀ПNНЇО Т┐П;Т└П)НЇОCТП! ЇЭ=ПX.Dorado Midas ManualEdward R. Fiala24 June 198364. Midas Display and the MouseThe Midas display is arranged as follows:Blank area at the top (unused);20 lines x 3 columns of name-value menus;Blank line;Program and elapsed time line;Blank line;Two command comment lines;Blank line;Three lines of command menu;Blank line;Input text line;Blank area a the bottom (unused).The program line will show the Midas release date or the name of the last program loaded. Theright-most part of this line will show elapsed time during long-running actions such as "Go" or"Test"; it shows the execution time of Midas initialization, the last command file, or the last actionat other times.Midas uses the two comment lines to report results of actions that it executes.When you move the mouse over a name-value menu or the command menu, the selected item (ifany) inverts black and white. Mouse actions execute when you RELEASE all mouse buttons, soyou can move the mouse with buttons depressed without causing damage. If the mouse hasmoved off of the menu that was selected when the first button went down, nothing will happenwhen the buttons are released.Some menus have additional actions "underneath" the ones normally displayed which will appearwhen you depress appropriate button combinations, as discused below. In other words, when youDEPRESS buttons, the menu may change; when you RELEASE ALL BUTTONS the selectedaction will get executed. On Dorado Midas, only name-value menus have actions underneath theones normally displayed.Since you can neither depress a button combination simultaneously nor release the buttonssimultaneously, Midas accumulates the union of all buttons that go down. This button-uniongoverns the "underneath" menu displayed, if any, and is the argument passed to the actionprocedure when all buttons are finally released.НЇОf╙uТ─Н!цqН4]Т НHYОfЯuНЇО^оtНЇО[]qП)НyОWКНyОV!П)НyОTV НyОR▀НyОPа НyОNЖНyОM, НyОKaНyОI√ НyОGлНyОFП!НЇОB▐Т▓ПYТ⌠НЇО@еТіП3ТїП,НЇО>ЗТ─П,Т│П:НЇО=/ТНЇО9ҐПOНЇО6KТ▄Т█ПQНЇО4│Т≤П$Т≥П7НЇО2ІТфТгПGНЇО0ЛТ═ПHТ║НЇО/!ТНЇО+╞Т▒Т▓ПCНЇО)ДТ┼ПEТ▀НЇО(ТЇТ╦П;НЇО&OТ▐Т░ПDНЇО$┘ТНЇО!ТИТЙПDНЇОHТфП&uqТгНЇО}ТьПRТыНЇОЁТП02Їl<ПL÷яDorado Midas ManualEdward R. Fiala24 June 198375. Name-Value MenusA name-value menu may contain a register or memory address in the name area and its contents inthe value area. A memory address may be specified as the memory name and word number, or asthe name of an address symbol defined in a microprogram you have loaded. The address symbolmay be followed by +/- displacement. If a number (default radix 8) is examined, the memoryname is defaulted to "VM," so examining "1234" will cause "VM 1234" to be displayed.Name-value areas are of different sizes. Smaller menus on the left are already filled in when youfire-up Midas; others are empty. Any item can be put in any menu, but larger menus on theright are better for items with long names or values. If an item overflows its menu, the right-mostcharacters of its name get truncated, then the left-most characters of its value.To display a new item, type its name (which will appear on the input text line), move the mouseover the name field in a name-value menu, and push-and-release the left (top) mouse button.Memory addresses in your microprogram may optionally be followed by a displacement "+n" or"-n"; " n" is the same as "+n". Midas will obtain the value of the item from the hardware anddisplay it.If the command line is empty, the selected menu will be cleared when the button is released.The address and data items in a name-value menu are affected by the radix and display mode forthe item, initially defaulted from a table indexed by the register or memory number. The addressoffset and value radices are always identical--Midas does not allow these to be independentlyspecified. On Dorado, octal radix is the default for everything except the microcomputermemories ($ABSOLUTE and $ABS), where hexadecimal is used. The user may change the radixwith the actions discussed below.The display mode for a value may be either numeric, search, or symbolic.Numeric mode shows the value as a sequence of numbers (in the chosen radix) separatedby blanks; this is the default for almost all items.Search mode shows the value as an address symbol plus offset; this is illegal except forregisters or memories that normally contain pointers into some other memory (e.g., onDorado, search mode for TPC, TLINK, etc. shows the nearest IM address symbol less-than-or-equal to the value plus an offset; for MEMBASE, BR address symbols areshown; for TIOA, DEVICE address symbols are shown.). Search mode is not the defaultfor any memory or register because it is slightly slower than numeric mode due tosymbol table access and because more screen area is required to accommodate longaddress symbols; however, you may find search mode convenient for some of the itemsmentioned above.Symbolic mode results in a special procedure being called to print the value for the item.Symbolic mode is illegal except for the MSTAT memory and the UPTIME andTGLITCH registers on Dorado; for these it is the default; special procedures do not existfor any other items.ЪНЇОf╙uТ─Н!цqН4]Т НHYОfЯuНЇО^оtНЇО[]qТ┌uqu qТ┐НЇОY⌠Т─П9Т│П#НЇОWхТ▀П%Т▄П7НЇОUЩТ║П%Т╒П6НЇОT3ТРТСПCНЇОPаТ▒uqП2Т▓НЇОNЖТўПFТ╞НЇОM,Т┐П6Т└П.НЇОKaТПQНЇОGОТ▓Т⌠П@НЇОF$ТаТбП6u q НЇОDZТ⌠ПEТ■НЇОB▐Т▒ПCТ▓НЇО@еТ НЇО=SТ╧П\НЇО9АТ░Т▒П0uquqНЇО8Т┬Т┴ПNНЇО6KТхП4ТиП)НЇО4│ТТП%ТУП4НЇО2ІТ░П0Т▒П(НЇО0ЛТП!НЇО-zП+uququqНyО*Т┘ПUНyО(=ТП4НyО$кТ²П5Т·П#НyО#ТўТ╞ПIНyО!6ТёП2ТєНyОkТЮП:ТАНyО║Т┐Т└П=НyОжТтП"ТуП/НyОТжПPНyОAТ²ПMТ·НyОvТНyОТ├ПZНyО:ТПGНyОoТ┌Т┐П=НyО ╔ТфЇ ^=ПZґ1Dorado Midas ManualEdward R. Fiala24 June 19838When Midas thinks that the value in a register may have changed, it reads its value from thehardware and updates the display; the times when Midas does this are discussed later. Names aresometimes preceded by *, indicating that the value has changed, or by ~, indicating that Midaswas unable to read the value for some reason (e.g., the machine was running). For an itemmarked with ~, the old value, which might be wrong, is displayed.Once some register or memory address has been put into a name-value menu, various mousebutton combinations over the name or value may be used to modify the way it is displayed,sequence through words in a memory, pretty-print the value on the comment lines, or showaddress equivalences. These are summarized in the table below:ButtonsName-fieldValue-fieldLeftExamineChange valueMiddleAlternate printoutPretty-print value on comment linesRightA+1, A-1 menuAppend value to input lineLeft+MiddleRadix menuRadix menuMiddle+RightFill column menuDisplay mode menuWhen a button combination selects an alternate menu, the alternate menu will replace thestandard menu while the mouse buttons are depressed; if you release the buttons over an alternatemenu item, it will be executed; if you are outside the menu when the buttons are released, thestandard menu will be restored and nothing will happen.The "A+1", "A-1" menu appears for memory addresses, but not for registers; these increment ordecrement the memory address in the menu, displaying the successor or predecessor. The "FillC"menu allows you to examine successors (A+1, A+2, etc.) in the menus below the selected one;the whole column is filled with successors, if the input text line is blank; otherwise, the input textline is evaluated to a number N, and N lines are filled in with successors. The last addressexamined is left on the input text line, so you can iterate the examine and fill column actions toachieve scrolling.Releasing the left button over a value stores the value of the input text (or 0 if no text typed) inthe selected register. For memories and registers whose values are displayed as several fields, theinput text must also be divided into fields; omitted fields are zeroed. Each field may consist ofnumbers or memory addresses separated by +/-; expressions are evaluated using the radix for theitem.Note: On Dolphin and Dorado, IM memory words show an absolute address with each value; it isimpossible to modify this address from Midas--the correspondence between virtual and absolute addressescan only be established by loading a microprogram. Several other items also have read-only fields thatcannot be written, as discussed later.Provision is made for special input evaluation based upon the register or memory; whenever theinput text cannot be evaluated as a sequence of fields, the special input procedure (if any) iscalled. At the present time, special input procedures are implemented for registers and memoriesthat contain microinstructions (MIR, IM, IMX, IMBD, and LDR on Dorado) and for 16-bitregisters. These are discussed later.НЇОf╙uТ─Н!цqН4]Т НHYОfЯuНЇО_qТІП2ТЇП*НЇО]KТ┤ПNТ┬НЇО[─ТіП6ТїП(НЇОYІТцП%ТдП5НЇОWКТПAНЇОTyТбПQТцНЇОR╞ТдП*ТеП/НЇОPДТоП:ТпНЇОOТП?НKОK╗uНЁ Н-y НKОH÷qНЁН-yНKОFуНЁТ─Н-yТНKОE НЁТ─Н-yТНKОC@ НЁТ─ Н-yТНKОAuНЁТ─Н-yТ НЇО>ТКПGТЛНЇО<8Т└ПaНЇО:nТіП@ТїНЇО8ёТП7НЇО51Т█П7Т▌П&НЇО3gТ┬П_НЇО1°Т÷ Т═ПPНЇО/яТ▀Т▄ПLНЇО.ТцПLТдНЇО,<Т≤Т≥ПKНЇО*rТНЇО'Т≈ u qП4Т≤НЇО%5Т▓ПdНЇО#jТ÷Т═ПSНЇО!═Т├ПGТ┤НЇОуНyОsТпПJТяНyОЁТ╙Т╚ПSНyОRТў Т╞П\НyОЯТП&НЇОёqТєТ╔ uqП0НЇОьТ©ТюПKНЇО Т░Т▒ПDНЇОCТрП7ТсНЇОxТП&Ъ$Ї1<ПYзIDorado Midas ManualEdward R. Fiala24 June 19839Releasing the middle button over a value pretty-prints the value on the command comment lines.The alternate for registers that normally hold IM addresses is the nearest IM address tag less-equalto the value+offset. Registers and memories that contain microinstructions may also be printedsymbolically. Other pretty-print information is detailed later.Releasing the right button over a value item appends the text of the value to the input text line.This is primarily used in command files to move values from one register to another or to displaya memory address that is pointed to by the value in some other register.6. Command MenuThe command menu holds a list of actions that Midas can execute. The basic menu is modifiedunder some conditions. For example, the "Dump" menu item only appears after you have done a"Ld". During execution, some actions show alternate menus.For almost all actions in the command menu, mouse buttons are equivalent. On Dorado, the"Go" and "SS" actions are an exception; executing one of these with the right button isinterpreted as "proceed," left button as "new go." The "DMux" action is also an exception.Many common actions may alternatively be initated by keyboard command characters, as given inthe action table below.ЪНЇОf╙uТ─Н!цqН4]Т НHYОfЯuНЇО_qТ≥ uqП%Т НЇО]KТ┌П1Т┐П3НЇО[─Т═Т║ПKНЇОYІТП@НЇОVDТ⌡ uqП0Т°НЇОTyТ▀ПVТ▄ НЇОR╞ТПHНЇОMOtНЇОIщqТ≈Т≤ uqП4НЇОHТ┐ПFТ└НЇОFHТП;НЇОBжТ╦ПUТ╧НЇОAТПП1ТЯП&НЇО?AТдП-ТеП.НЇО;оТ∙П5uqНЇО:ТЪЇ9Ґ=П.N▒Dorado Midas ManualEdward R. Fiala24 June 198310Table 1: Command Menu ActionsInputCharMenu ItemCommentsActions (potentially) available on all implementations of Midas[File]RunProgReset symbol table and display, then do RdCmds.[File]RdCmdsExecutes command file (def. ext. ".Midas") on input text line or fromsubmenu.ShowCmdsShows command file text for selected menu items.FileWrtCmdsWrite subsequent commands on File.Files;LLdLoads .MB files (names separated by ",").FilesLdSymsLoads only addresses from .MB files.[File];DDump# Dumps compacted .MB file using the .MB file(s) of the previous loadto control what's dumped.[File];CCmpr# Compares hardware data to that in .MB file.Addr=Prints value of an address (illegal in com-file)IMaddr;BBrkInserts break point.[IMaddr];KUnBrkRemoves breakpoint (default address = last break).[IMaddr];GGo* Start at address (continue if nothing typed).[IMaddr];PProceed* Start at address without IOReset or control section reset (continue frombreak if nothing typed).[IMaddr]:SSSingle-step at address (continue-step if nothing typed).IMaddr)--Call subroutine with args (e.g., "FOO(A1,A2)").ResetReset the machine; assorted options from a submenu.TestTest register, memory, or other test with data pattern and item selectedfrom submenus.TestAllTest everything.IMaddr;RRepGo* Go at address, repeatedly restart after halts.IMaddr;SRepSS* Repeatedly SS at address.PEscanScan local memories for parity errors (IMX, IFUM, RM, STK,CACHEA, and CACHED on Dorado).FieldsFor scoping.LDRaddrLDRtest* Manually-constructed test sequences.VirtChanges IM address interpretation to be virtual.AbsChanges IM address interpretation to be absolute.Actions peculiar to Dorado MidasSetClkSet the clock speed from a submenu.T1Clocks MIR through t1, reads the DMux, then clocks through t2 andrestores MIR (so display shows DMux values read after t1).T2Clocks MIR through t2, reads the DMux, and restores MIR (so displayshows DMux values read after t2).T3Clocks MIR through t3, reads the DMux, then clocks through t4 andrestores MIR (so display shows DMux values read after t3).RepT2* Repeatedly does t2 (for scope loops).DtachDisconnects Midas and repeats the connection procedure.ConfigModify board configuration, cache, map, storage, and IM parametersfrom submenus and adapt Midas to these.DMuxModify display of DMux items as discussed later.[IMaddr]OS* "Opcode step" = SS program until a halt condition occurs or anIFUJump has been executed.[IMaddr]SimGo* Like "Go" invoking the DMux checker after each step.SimTest* Random instruction test using MIR and the DMux checker.HWChkDisplays submenu of tests and scope loops for hardware checkout.ActiveActive, PrePassive, and Passive modes discussed later.UpdateRead registers and display new values (used while passive)* = requires preceding "TimeOut" action in command file# = requires confirmation with , "Y", or "." (or by preceding "Confirm" command in com-file)[...] = optional input textЪНЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuНО_vТ▓НЇО\TwНKwНAwТ─Н"щwНЇОZ xТП?НЇОWКsНAН"щП/НЇОV┼НAН"щТ╛ТґП*Н"щОU*НAОSиН"щТП0НЇОRhНAН"щП"НЇОQНKНAН"щП)НЇОOїНAН"щП$НЇОNFНKНAН"щТ┤П3Т┬Н"щОLЕТНЇОK└НKНAН"щП-НЇОJ#НKН"щП0НЇОHцНKНAН"щНЇОGbНKНAН"щП2НЇОFНKНAН"щП/НЇОD═НKНAН"щТ┌ Т┐П@Н"щОC@ТНЇОAъНKНAН"щП8НЇО@~НKНAН"щП/НAО?Н"щП3НAО=╪Н"щТ·П.Т÷Н"щО<\Т НAО:ШН"щНЇО9 НKНAН"щП0НЇО89НKНAН"щНAО6ыН"щТТП#Н"щО5xТНAО4Н"щНЇО2ІНAН"щП&НAО1UН"щП0НAО/УН"щП1НЇО-юxНAО+▄sН"щП#НAО*+Н"щТЁТЄП+Н"щО(йТП:НAО'iН"щТ°ПCН"щО& ТП!НAО$╗Н"щТЁТЄП+Н"щО#GТП:НAО!ФН"щП'НAО ├Н"щП7НAО%Н"щТжП0ТвН"щОдТП'НAОcН"щП0НЇОНAН"щТбТцП1Н"щО╒ТНЇОAНAН"щП6НAОЮН"щП9НAОН"щТЛТМП'НAОН"щТП6НAОЎН"щП:НЇО П7НЇО©П`НЇО ^▄Ї ;<ПZпцDorado Midas ManualEdward R. Fiala24 June 198311Some actions in the preceding table are replaced with complementary actions after execution;these are ShowCmds by StopShow, WrtCmds by StopWrt, Virt by Abs. The Active, PrePassive,and Passive actions are in a "ring"; the current hardware mode is shown in the menu; bugging itwill change to the next mode. The DMux action will be displayed as "DMux", "OldDMux","DWrong", or "DChk" according to which DMux table is currently displayed. All of theseactions are discussed later.General philosophy on mixing keyboard and mouse button control is that, when possible, acommand involving some typing is carried out completely at the keyboard, whereas commandsinvolving mouse buttons are carried out completely with the mouse.For example, to start a microprogram at some address, you normally type an address; then youcould bug "Go" in the command menu, but probably "address;G" is more convenient becauseyou won't have to lift your hand from the keyboard; ";G" are the command characters equivalentto bugging "Go".Many commands are executed in overlays. When these get executed, the register display will turnoff (The code for overlays resides where the display bit buffers would otherwise be.). Duringloading or execution of command files, the display is turned off to make the machine run faster.Long-running commands normally display an "Abort" menu item. When this is bugged or whencontrol-C is typed, the action terminates.7. Keyboard"=", "+", "-", "#", and "!" are legal symbol constituents in microprograms but will causetrouble for Midas if they appear in address symbols. "=" is an action character that willprettyprint the memory name and offset and the nearest address symbol less-than-or-equal to thevalue of the string on the input text line. "+" and "-" have their usual sum and differencemeanings in evaluating input expressions. "#" (octal), "!" (decimal), and "%" (hexadecimal) maybe inserted anywhere in a number to overrule the default radix; e.g., "#123" or "123#" willforce the evaluation of the number "123" to be in octal. The default input/output radix foralmost everything on Dorado Midas is 8 (octal).Exceptions are UPTIME and TGLITCH, which show hr:min:sec in decimal and the $ABS and$ABSOLUTE memories, which use hexadecimal for both the address and value.Lower case typein is converted to upper case by Midas, so avoid lower case characters inmicroprogram address symbols. You should either write microprograms with the shift-lock keydepressed or assemble them with the convert-to-upper-case assembly switch.Typing ahead is legal until the character you type would cause execution of an action. After that,Midas will flush input and blink at you until the current action finishes.At the end of an action, input text typed for that action is displayed on the input text line. Thistext remains valid and can be used as the arg for another mouse action. However, if you type anycharacter (except control-A or backspace), the old input will be flushed before inserting the newcharacter.ЪНЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuНЇО_qТхТиПIНЇО]KТ⌠П4Т■П&НЇО[─Т░ Т▒ПTНЇОYІТ╧П.Т╨П(НЇОWКТпТяПDНЇОV!ТНЇОR╞ТыП6ТзП"НЇОPДТЇП:Т╦НЇОOТПBНЇОK╗ТїПJТ╗НЇОIщТ╟ Т╠ПIНЇОHТ┬П3Т┴П+НЇОFHТНЇОBжТ┤Т┬ПCНЇОAТЇП8Т╦П&НЇО?AТ≤П&Т≥П:НЇО;оТ▒П=Т▓НЇО:ТП*НЇО4єtНЇО12qТмПSТнНЇО/hТщП5ТчП%НЇО-²Т≤П>Т≥П!НЇО+рТ╪ТҐПPНЇО*Т┼П`НЇО(=Т╦ Т╧ПPНЇО&sТаТбПSНЇО$╗ТП/НyО!ФsТ ТПFНyО ├ТПIНЇО7qТИПEТЙНЇОlТ╟ПXТ╠НЇО╒ТПJНЇО0Т┴Т┼ПTНЇОeТПJНЇОСТ▓ПFТ⌠НЇО)Т┌Т┐ПKНЇО ^Т÷П8Т═П)НЇО⌠ ЭЇL<П\©%Dorado Midas ManualEdward R. Fiala24 June 198312Keyboard editing characters are as follows:control-Adelete last characterbackspacedelete last charactercontrol-Qclear text linedelclear text lineOther special keyboard characters are as follows:control-Cabort the current action--equivalent to bugging the "Abort" command (only defined foractions that display "Abort")control-Zabort all command files in progressescaperepeat previous action (special for "Test" and "TestAll")returnspecial following "Test" or "TestAll"control-Dturns on the display (used during command files)control-Oturns off the display (used during command files)shift-swatexit cleanly from MidasThe interrupt characters above are ineffective during loading, dumping, or comparing, whichtypically take between 2 and 20 seconds. Indefinite duration commands, such as "Go", "Test",etc. always monitor the keyboard, so control-C can be used to terminate them.Control-Z, control-D, and control-O are intended for use during command files. However, thesecharacters do not take effect until the command file executes a command such as "Go" whichmonitors the keyboard. There is no way to abort a command file and give control back to Midassafely except during a "Go" or other long-running command. This is not expected to be aproblem because commands are executed quickly.After interrupting a "Go" with control-C or control-Z, proceeding with ";P" or ";G" will succeedexcept when you have smashed the machine state by writing a register or in some other way orhave interrupted an instruction from which continuation is impossible.Although command menu items "SS", "Go", "Brk", "UnBrk", "RepSS", and "RepGo" areprovided, the keyboard characters equivalent to these are usually more convenient.8. Command FilesCommand files (default extension ".Midas") are normally executed either by typing "Midasfilename" to the Executive or by bugging a file name in the subsidiary menus put up by"RunProg" or "RdCmds". Alternatively, you may type a file name first, then bug one of theseactions (If you type a file name after the subsidiary menu is put up and then bug "Abort", thecommand file will also be executed; it is not clear whether this is a bug or a feature.).File names in these sub-menus are contained in the files Midas.Programs and Midas.UserPrograms, each ofwhich has a list of file names separated by blanks, commas, or carriage-returns. Midas.Programs is part ofthe standard Midas release; Midas.UserPrograms is an optional file that a user of Midas can prepare withhis own stuff. The names must be UPPER-CASE. These lists serve two purposes: building file FP's tospeed OpenFile, and preparing the menu items for "RunProg" and "RdCmds".If the file name contains no extension, then hint FP's will be built for both name.MB andname.MIDAS and name will be put in the "RunProg" menu. (However, the hint FP's are notbuilt unless the file exists, and the file name will not be put in the "RunProg" menu unlessname.MIDAS exists).НЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuНЇО_qП+Н:О[ЙsН░Н:ОZ┼Н░Н:ОY)Н░Н:ОWхН░НЇОTyqП1Н:ОQNsН░Т▄П$Т█П1Н░ОOМТН:ОN▄Н░П#Н:ОM,Н░П9Н:ОKкН░П%Н:ОJjН░П0Н:ОI Н░П1Н:ОG╗ Н░НЇОDZqТзП[НЇОB▐Т╘Т╙ПEНЇО@еТПMНЇО=SТ≥Т ПIНЇО;┬ТЁП#ТЄП7НЇО9ҐТ▄П^НЇО7СТнПCТоНЇО6(ТП.НЇО2ІТ▌ПNТ▐НЇО0ЛТ╒П;ТёП!НЇО/!ТПFНЇО+╞ТКПPНЇО)ДТПRНЇО%XtНЇО!ФqТЙПQТКНЇО ТДТЕПJНЇОQТёП\НЇО┤ТєП^НЇО╪ТВПCТЬНyОЗsТ■ПdТ∙НyО Т▓П;Т⌠П0НyО9Т°Т²П\НyОьТ≤ Т≥ПWНyОwТПHН;ОыТ╩П;Т╪Н;ОxТ√Т≈ПDН;О Т╚П8Т╛П$Н;ОЇТЄЇ■<П\w*Dorado Midas ManualEdward R. Fiala24 June 198313If the name ends in "*", a quick OpenFile table entry is made for name.midas and the namewill appear in the "RdCmds" menu.If the file name contains an extension, then it will be put in the quick OpenFile table, but won'tappear in the "RunProg" or "RdCmds" menus.Since Midas builds a table of file FP's during initialization, when you edit a command file or modify a .MBfile, you should reinitialize Midas by typing "Midas/I". When you add new command files or .MB filesyou should update the "Midas.UserPrograms" file appropriately and do "Midas/I"."RdCmds" executes the actions stored in the command file; it is frequently used to modify thedisplay in various ways by executing command files that show collections of items that are ofinterest."RunProg" first clears the symbol table and restores the display to its initial arrangement; then itexecutes the actions in the selected command file; "RunProg" is used to completely changecontexts--to run a new microprogram, for example.Generally, there is one "RunProg" command file for each hardware diagnostic, with the same name as thediagnostic, e.g.:dgbasic.mbthe diagnostic;dgbasic.midasthe command file.A command file following this convention loads the diagnostic into the microprocessor and displays variousregisters of interest when the microprogram is in use.The command-file facility is actually a (awkward and limited) programming language. Thecollection of actions discussed below is being developed so that command files can monitordiagnostic microprograms, collect and report error information on an output file, or direct thesequence of diagnostic microprograms according to hardware failures that are observed.For system microcode, command-files can be used to control auto-restart and failure diagnosis.Command files can be nested with "RunProg" and "RdCmds" subject to the followingRESTRICTIONS:(1) [Maxc2 only] "AltIO" terminates command files (i.e., upon return to Midas from AltIO thecommand file will not be continued).(2) Nesting is limited to 8 levels (a parameter that could be increased if more levels are needed).(3) Command file names appearing in the "RdCmds" or "RunProg" menus must not duplicateany other action names used by Midas. If this happens inadvertently, command file interpretationwill be substituted for the intended action whenever that action is executed from a command file.Fortunately, interactive execution of the duplicated action is unaffected. Midas does not detectthis.(4) Midas is tight on storage when running the simulator (SimGo and SimTest actions), andavailable space might become exhausted. Three separate storage resources are husbanded byMidas: stack, sysZone, and other. Some sysZone is consumed by each open file, and thesimulator puts one overlay there. If command, output, and WrtCmds files are simultaneouslyopen when SimTest or SimGo is executed from a command file, I think sysZone will overflow,ЪНЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuН;О_9sТ÷П/Т═П*Н;О]ьТП!Н;О[єТ┘ПQТ├Н;ОZCТП*НyОW╔Т┐ПkНyОVDТ÷ПFТ═НyОTЦТПOНЇОQ■qТ╗П'Т╘П6НЇОOйТҐПQТЎНЇОMЪНЇОJ█Т■П\Т∙НЇОHцТэПYНЇОFЬТП1НyОCмsТ■П7Т∙П/НyОBlТН:О?н НПН:О>mНПНyО;оТ⌠П.Т■П<НyО:nТП6НЇО7qТФПSТГНЇО5UТэТщПEНЇО3┼Т©ПQТю НЇО1©ТПVНЇО.MТ╦П:Т╧П$НЇО*шТПBТ НЇО)НЇО%÷ТёП$ТєП9НЇО#тТП$НЇО bТ█П#Т▌ПAНЇОПТ╟ПVНЇО&Т├П)Т┤П8НЇО[Т▐П[Т░НЇО▒ТґП;ТўП&НЇОфНЇОTТоП.ТпП+НЇО┴ТоПIТпНЇО©ТГПRТХНЇОТТ©П:ТюП!НЇО*ТїТ╗ПQЪ≤Ї Ц=П]("Dorado Midas ManualEdward R. Fiala24 June 198314but there should be enough sysZone storage for two open files plus the overlay.Note that even when command files are nested to several levels, Midas only keeps open thecurrent command file, so nesting command files does not affect the storage requirement.The simulator also steals space from the stack for one overlay, and it is conceivable that runningSimGo from a command file and then aborting from the keyboard will exhaust the stack.However, if Midas is properly checked out, then this should not happen.Finally, unused storage and the name-value menu bit buffers are used for the rest of thesimulator. Since this storage is consumed by file handles and name strings which you add toMidas.Programs and Midas.UserPrograms, this storage might become too small for the simulator.If this happens, you will fall into Swat with an "Out of storage" message when you try to run thesimulator.(5) There are other size limits you must observe. First, the number of RdCmds and RunProgactions you may add to the ones already in Midas.Programs is limited to about 25 (on 24 June1983). This limit is imposed by the table storage reserved for these actions when Midas is built.If you exceed this limit, the submenu for the "Test" action cannot be shown, and Midas will fallinto Swat during Midas/i initialization with a message indicating the number of excess actions.The limit applies not to the number of names in Midas.Programs and Midas.UserPrograms, butrather to the number of these names which exist on your disk. So to recover from this overflow,you can either prune the number of names in Midas.Programs or Midas.UserPrograms, or you candelete some of the *.Midas files from your disk.Secondly, the list of names in the RdCmds or in the RunProg menu must not overflow commandmenu space. If one of these lists overflows, Midas will fall into Swat during its Midas/iinitialization with a message telling you by how many characters you have exceeded the limit.Here again, you recover from the overflow by either pruning names or deleting *.Midas files. Oryou can continue from the Swat call; if you continue, Midas will simply truncate the names whichwon't fit when it displays the menu.(6) Some actions occur in command overlays where a sequence of menu items must be buggedbefore the action is specified. For example, on "Test", you must specify the data pattern (e.g.,"Random"), then a "TimeOut", and finally the register or memory to be tested (e.g., "RM"). It isillegal to start a nested command file before the subsidiary actions are specified; if you try to dothis, Midas will give an error message.(7) Some actions require a preceding "TimeOut" action. The command file must have two actionsafter the "TimeOut" before terminating.ЪНЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuНЇО_qПOНЇО[єТйПPТкНЇОYыТПWНЇОVgТ≥ПCТ НЇОT²ТИП0ТЙП%НЇОRрТПGНЇОO`ТКП?ТЛНЇОM∙Т╧П\НЇОKкТ²ПJТ·НЇОJТ┼Т▀ПZНЇОH6 НЇОDдТ╟Т╠ПBНЇОBЫТ╗ПGТ╘НЇОA.Т ПXТ⌡ НЇО?dТ∙П4Т√П,НЇО=≥Т╣ПOТІНЇО;оТ╘П,Т╙П.НЇО:Т░Т▒ПSНЇО89Т└Т┘ПUНЇО6oТП0НЇО2ЩТ▀П)Т▄П1НЇО12ТЙП-ТКП-НЇО/hТ╩Т╪ПHНЇО-²Т█Т▌П@НЇО+рТ├Т┤ПGНЇО*ТП$НЇО&√Т╙ПNТ╚ НЇО$кТ╙ПaНЇО#Т└ПZТ┘НЇО!6Т≈ПDТ≤НЇОkТП'НЇОЫТ┌П.Т┐П0НЇО/ТП'Ъ ФЇХ=ПN#Dorado Midas ManualEdward R. Fiala24 June 198315A number of actions, some of which cannot be given interactively, are useful in command files.These, not given in the table earlier, are shown below. The first table is for actions that operateon name-value menus (A0 ... C19); the second table for command menu (X) actions.Table 2: Command File Name-Value ActionsText ArgActionCommentsAddressAddrButton actions as discussed earlier.ValueValButton actions as discussed earlier.A+1Increment memory address, as discussed earlier.A-1Decrement memory address, as discussed earlier.NColsFillCFill name-value menus beneath the one selected with consecutive addresses starting atthe address contained in the selected menu.OctDisplay address offset and value in octal.DecDisplay address offset and value in decimal.HexDisplay address offset and value in hexadecimal.NumDisplay value numerically.SymDisplay value symbolically.SearchDisplay value as an address symbol plus offset in the appropriate memory.ValueSkipESkip the next command if the input text evaluates equal to the contents of theregister or memory word displayed. The input text is evaluated exactly as though itwere to be stored into the register displayed in that name-value menu, so if thevalue displayed has several fields, the input text must also have several fields. Thecommand file must have at least one more action after the SkipE.ValueSkipGSkip if input text greater than the contents of the item in the name-value menu(unsigned compare).ValueSkipLSkip if input text less than name-value item.ValueSkipNESkip if input text unequal to name-value item.ValueSkipLESkip if input text less than or equal name-value item.ValueSkipGESkip if input text greater than or equal to name-value item.ЪНЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuНЇО_qТєПAТ╔НЇО]KТ≤ПKТ≥НЇО[─ТПPНґОV┼vТ▓П)НЇОS_wТ─НKНПНЇОPаsНKНПТП$НЇОO`НKНПП$НKОMЪНПП/НKОL·НПП/НЇОK>НKНПТ│Т┌П8НПОIщТП+НKОH|НПП*НKОGНПП,НKОE╩НПП0НKОDZНПНKОBЫНПНKОA≤НППIНЇО@7НKНПТ╪ТҐПFНПО>вТ▄ПJТ█ НПО=vТ╣ТІП:НПО<Т∙П2Т√П$НПО:ЄТП@НЇО9TНKНПТ╡ТЁПHНПО7СТНЇО6▓НKНПП-НЇО51НKНПП.НЇО3пНKНПП6НЇО2pНKНПП<зЇ2M=П5ЎКDorado Midas ManualEdward R. Fiala24 June 198316Table 3: Command File Command ActionsText ArgActionCommentsOctal no.SkipSkip N following actions, where N is the value of the input text. An error occurs ifthe command file does not specify at least N more actions after the Skip..TagSkipSkip following actions until one is encountered with the label ".Tag". An erroroccurs if ".Tag" is not found.Octal no.BackSkip.TagBackSkipReset to byte 1 of the command file, then skip.Octal no.ReturnReturn out of current command file, then skip (".Tag" form is illegal for Return.).DisplayOnTurn on the display, so that effects of subsequent commands can be observed. Thedisplay is initially off for a command file. This can also be done with control-D.DisplayOffTurn off the display. This can also be done with control-O.Octal no.TimeOutInput text is evaluated to a 32-bit octal number of msec at which to abort theimmediately following command, if it has not finished by then. This is intended foruse before "Go" and other commands which might hang indefinitely. If the timeoutoccurs, Midas will skip the command after the "Go". TimeOut also turns on thedisplay, necessary because the machinery which checks for timeout is only active withthe display on. Note that TimeOut is required before the actions *'ed in the tableon page 4 and is illegal before other commands; Midas will complain if you do notuse TimeOut appropriately. The command file should include at least two moreactions after the TimeOut. Command files written by WrtCmds will includenecessary TimeOuts with a default of 30000 (~12 seconds); you will generally haveto replace this default value with something more appropriate.ConfirmSupplies confirmation for the command which follows (which should be one of thecommands requiring confirmation). If you omit a confirm in a command file, theuser is queried for confirmation.File nameOpenOutputOpens an output file (default extension ".Report") on which text can be written.File nameAppendOutputAppend to an output file (default extension ".Report")CloseOutputCloses the output file.[text]WriteMessageWrites the contents of the input text buffer on the output file. Note that if any textfollows the WriteMessage, that text up to but not including the is what getswritten. However, if immediately follows WriteMessage, then the contents ofthe input text buffer left by the previous command get written. "~" is translatedinto and "\" into a blank.WriteDTAppends the current date and time to the output file.textShowErrorDisplays the text arg on the command line, turns on the display if it was off, andqueries with "Abort" and "Continue" menu items. Aborting will terminate all nestedcommand files back to the top level.--DumpDisplayWrites the current display image on the output file.textPrettyPrintEvaluates text to a memory address, register name, or memory name; writes thisname on the output file; then pretty-prints the value on the output file exactly as itwould be pretty-printed on the comment lines if the item were displayed in one ofthe name-value menus and middle-buttoned.File nameWriteStateUsed by Midas initialization to create the Midas.Dtach and Midas.RunProg files--users shouldn't use this action.9. Syntax of Command-file ActionsThe syntax of a command-file action is as follows:[["."]$" "]$" "$" "[$" "][";"]where the "[]" denote that the ".tag", input text, and ";comment" are optional. $" " denotes asequence of one or more blanks or tabs (any characters with Ascii codes less than 408 exceptcarriage return are equivalent to blanks). The sequence of characters excluding the comment mustnot exceed 99 characters.НЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuН_О_vТ▓П&НЇО[ЙwТ─НKНПНЇОYLsНKНПТ┘ПRТ├НПОWКТЖП,ТВНЇОV┼НKНПТ╧П4Т╨НПОU*ТНЇОSиТ─НKНЇОRhНKНПТП/НЇОQТ─НKНПТ²Т·П0НKОOїНПТ▌ПMТ▐НПОNFТ╒П2ТёП!НKОLЕ НПТП<НЇОK└Т─НKНПТҐТЎПDНПОJ#Т┤Т┬П?НПОHцТ┘ПBТ├НПОGbТєТ╔ПAНПОFТ┌ПUНПОD═Т П&xsТ⌡ НПОC@Т▌xsП2Т▐НПОAъТ╣ПHТІНПО@~ТИТЙП8НПО?Т°ПBТ²НПО=╪ТП>НKО<\НПТ Т⌡П2НПО:ШТ╒ПEТё НПО9 ТП!НЇО89Т─НK НПТЇП"Т╦П)НЇО6ыТ─НKНПТП0НKО5x НПНЇО4НKНПТ┐ПFТ└НПО2ІТ√Т≈П8НПО1UТ░П&Т▒П+НПО/УТ╒ТёП8НПО.■ТНKО-3НПП5НЇО+рНKНПТ°П?Т²НПО*rТ─П#Т│П0НПО)ТП$НЇО'╟НK НПП4НЇО&OНK НПТ╧ПBТ╨НПО$НТ█Т▌П>НПО#▌Т√Т≈П:НПО"-ТП)НЇО лТ─НK НПТ╦П2Т╧НПОkТНЇО/tП"НЇОҐqП2НyОnsПMНЇО qТ╔ТіПEНЇОUТҐТЎПEО хsОUqНЇО┼Т┐ПFТ└НЇО юТ┬Ї y<П]▓дDorado Midas ManualEdward R. Fiala24 June 198317If the first character on the line is a ".", then the characters after that are a label or tag which maybe used as the argument for the "Skip" or "BackSkip" actions given in the table earlier. may be any combination of the letters "L" (left-button), "M" (middle-button), and"R" (right-button); these are the buttons released to execute the action. These may appear in anyorder. is the menu name in which the action is executed ("X" for the command menu,"A0"..."A19", "B0"..."B19", and "C0"..."C19" for name-value menus). is the text name for one of the actions (upper/lower case must match the definition). is the text typed on the command line, which may be anything except a ";".Note that if a single blank terminates and if no input text argument is given, then input text left-over from the preceding action will be used. This allows text from a right-button action over a value to beused in a following action (e.g., in WriteMessage or to store the value into another reigster). However, oneor more extra blanks will reset the input text, so the action is executed with null input text.";" begins a comment, which may be omitted. (carriage-return) terminates the action.I think Midas will report all command file syntax errors intelligibly. Error handling worksapproximately as follows: Whenever Midas is watching the keyboard (which only happens duringlong-running actions such as "Go" or "Test"), control-Z will abort the current and all nestedcommand files; the ShowError action in a command file also aborts all command files. If Midasdetects an error while executing an action and queries, then "Continue" will abort the action inprogress and continue with the next command file action. "Abort" will terminate the currentcommand file, but not higher command files. However, a syntax error in the command file itselfalways aborts the current command file.To find out what text should be put in command files, you can bug "ShowCmds" in thecommand menu. This will cause the command file text for each command to be displayed on thecommand comment line as the mouse selects it (You don't have to execute the command to seethe equivalent text.). This text is complete except that the mouse button which executes thecommand isn't shown unless you depress the mouse button. To terminate "ShowCmds", bug"StopShow" (which appears only when "ShowCmds" is in progress.).You can prepare a command file (default extension ".Midas") by typing a file name and bugging"WrtCmds". This causes text for subsequent commands to be put on the file. When you aredone with this, bug "StopWrt" to close the file. ("StopWrt" is in the command menu only whena command file is being written.). Exiting from Midas also closes the output file.You will probably want to edit out your goofs with Bravo after the command file is written.In addition, you will have to insert "Confirm" before actions which require confirmation andmodify the "TimeOut" stuff which Midas uses to surround actions which might hang indefinitely(See the table given earlier for the actions that require this.).ЪНЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuНЇО_qТ│П@Т┌П(НЇО]KТРПOТСНЇОYыТўПFТ╞НЇОXТ┬ПTТ┴ НЇОVDНЇОRрТрП+ТсП'НЇОQТПCНЇОM∙Т²Т·ПEНЇОJ#ТПQНyОFЬsТ│xsПLТ┌НyОE≈Т├П&Т┤ПFНyОD7Т┼ПmНyОBжТП_НЇО?┤qП+НЇО<П-НЇО8ёТэТщПOНЇО6ыТ┴Т┼ПMНЇО5ТфП]НЇО3CТ■П0Т∙П.НЇО1yТ╔П`НЇО/ўТЎПFТ©НЇО-ДТ░П>Т▒П!НЇО,ТП'НЇО(їТДТЕПLНЇО&эТ┤ПEТ┬НЇО%Т÷П1Т═П)НЇО#GТфПPТгНЇО!}ТаТбПCНЇО╡ТП@НЇО@Т▓П]НЇОuТўТ╞ПBНЇО╚Т▐ПXТ░НЇОЮТПSНЇОnТцП>ТдНЇОЭТфП\НЇО2Т√П&Т≈П7НЇОgТПAЪbЇ <П[КDorado Midas ManualEdward R. Fiala24 June 198318Here is a sample command file:L X Ld dg1;Equivalent to typing "dg1" and bugging "Ld" in the command menuL A0 Addr TASK;Examine the "TASK" register in name-value menu A0L A0 Val 0;Change the value in TASK to 0L A1 Addr RTEMP;Examine the address "RTEMP" in menu A1L A1 SkipE FOO+3;Skip the next command if RTEMP contains the value FOO+3L X ShowError RTEMP not loaded correctlyL A2 TLINK 0;Examine the Link register for task 0 in menu A2L X TimeOut 2000;Abort the following command if it hasn't finished in 1.024 sec.L X Go START;Begin microprogram execution at address "START"L X Skip 1;Skip the next command if "Go" halts before timeoutL X ShowError START;G failed;Show an error messageЪНЇОf╙uТ─Н!цqН4]Т НG╘ОfЯuНЇО_qНxО[ЙsТ─ Н! ТДТЕП!НxОZ┼Т─Н!ТП*НxОY)Т─ Н!ТНxОWхТ─Н!ТНxОVgТ─Н!ТП3НxОUП(НxОSіТ─Н!ТП(НxОREТ─Н!ТП:НxОPДТ─Н!ТП*НxОO┐Т─ Н!ТП.НxОN#Т─Н!ТчЇN9/└Dorado Midas ManualEdward R. Fiala24 June 19831910. Registers and Memories Known to MidasTable 4: MemoriesMemoryWidthLengthNotesComments(octal)(octal)IMBD44100004,5,6Control store (via mufflers, manifold ops.--fortesting only)IMX44100006,7Control store (absolute).IM10010000Control store (virtual).TPC20 201,2,6,7Shows CIA for current task.TLINK20 201,2,6,7Shows Link for selected task.OLINK20 201,2,3,9Shows address of last call (if any).ALUFM10 206,70 and 16 smashed and restored by Midas.RM20 4006,7STK20 4006,7STKX20 77= STK[STKP-address]T20 201,6,7Waystation for A or Mar registers.RBASE 4 201,6,7Used in read-write of RM.TIOA10 201,6,7MEMBASE 5 201,6,7MD20 201,9PIPE40 208,9Shows Pipe0 to Pipe5 (all signals high true)BR30 406,7,11BRX30 411Shows 4 BR words pointed at by MemBXROW-- 10011Shows 4 cols and Victim/NextV of a cache rowCACHEA23 4006,7,11Length is 2000 with 16k cacheCACHED20100006,7,11Length is 40000 with 16k cacheMAP20 2166,11Length is 216 or 218 with larger map ic'sVM20 2286,11IFUM40 20006,7,10DMUX20 2004,9DHIST54 403,4Discussed in the "DMux" section.VH40 403,4,9Discussed in the "DMux" section.$ABSOLUTE10 216Includes all state of microcomputer.$ABS20 215$ABSOLUTE shown in 20 bit unitsMSTAT40 249Low words of $ABSOLUTE shown symbolicallyLDR44 2003Holds microinstructions used by Midas.MDATAund. 103BITS-CHECKED etc. for testing.MADDR40 143LOOP-COUNT etc. for testing.TASKN 0 203Symbolic task definitionsDEVICE 0 4003Symbolic device address definitions1.Task-specific2.Virtual/absolute stuff applies3.Fake memory--artifact of stuff in Midas4.Readout via DMux, so value shown is correct in passive mode.5.Resets the control section, so "Continue" from b.p. illegal.6.Appears in Test menu.7.Appears in TestAll menu.8.SRN addressed.9.Read-only to Midas.10.Resets the IFU, so "Continue" from b.p. illegal.11.Smashes the fault task pipe entry to access the item, so "Continue" from task 17 b.p. illegal.НЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНЇОaвrП*Н#≥О^esТ▓Н:О[:tН/Н╠Н&∙Н-yН/ОYыН╠Н:ОW;uНЮН╠Н&∙Н-yТ5П/Н-zОUзТН:ОTyНЮН╠Н&∙Н-yН:ОSНЮН╠Н-yН:ОQ╦НЮН╠Т─Н&∙Н-yТН:ОPWНЮН╠Т─Н&∙Н-yТН:ОNЖНЮН╠Т─Н&∙Н-yТН:ОLбНЮН╠Т─Н&∙Н-yТП&Н:ОKaНЮН╠Т─Н&∙Н:ОJНЮН╠Н&∙Н:ОH÷НЮН╠Н-yТН:ОG?НЮН╠Т─Н&∙Н-y ТН:ОEчНЮТ─Н╠Н&∙Н-yТН:ОD}НЮН╠Т─Н&∙Н:ОCНЮН╠Н&∙Н:О@ХНЮН╠Н&∙Н:О?┤НЮН╠Н&∙Н-yТП,Н:О>&НЮН╠Т─Н&∙Н:О<фНЮН╠Н&∙Н-yТП$Н:О;eНЮН╠Т─Н&∙Н-yТлТмН:О:НЮН╠Т─Н&∙Н-yТН:О8ёНЮН╠Н&∙Н-yН:О6ЭНЮН╠Т─О7┴Н&∙О6ЭН-yТО7┴О6ЭО7┴О6ЭН:О5UНЮН╠Т─О5БН&∙О5UН:О3 НЮН╠Н&∙Н:О0ЛНЮН╠Н&∙Н:О/▀НЮН╠Н&∙Н-yТН:О.*НЮН╠Т─Н&∙Н-yТН:О+ЖНЮН╠Т─О,┐Н-yО+ЖТН:О*NНЮН╠Т─О*шН-yО*NТН:О(ННЮН╠Т─Н&∙Н-yТТТУН:О&╧НЮН╠Т─Н&∙Н-yТП!Н:О%XНЮН╠Т─Н&∙Н-yТН:О#ЬНЮН╠Т─Н&∙Н-y ТН:О"≈НЮТ─Н╠Н&∙Н-yТН:О!6НЮТ─Н╠Н&∙Н-yТН:О≤НKН:О7НKН:ОжНKП'Н:ОuНKП<Н:ОНKП<Н:ОЄНKН:ОSНKН:ОРНK Н:О▒НKН:О1НKП0Н:ОпНKТБПMТЦІЇґ7mW^aDorado Midas ManualEdward R. Fiala24 June 198320Table 5: RegistersRegisterWidthNotesComments(octal)CPREG202,3Alto-baseboard interface register, freely smashed by Midas except inpassive mode.MIR442,3,6Microinstruction register, used ubiquitously by Midas.IMOUT441,6Direct IM outputsTASK 45Discussed in the "Task-Specific Register" section.Q202,3Waystation for write of registers on external BMux.CNT202,3SHC202,3Special tests for RF_, WF_, and FF-controlled shifts.MEMBX 22,3STKP102,3PROCSRN 42,3,6Must be 0 on a "Go" to operate memory system normally.MCR202,3,6Several bits are not testable; smashed and restored for memory stuff.CONFIG201TESTSYN107Must be 200 (error correction on) or 0 (error correction off) to operatestorage normallyPCX201,2,3INSSET 52,3Shows the _Id count and instruction set (only the instruction set iswriteable)UPTIME601Time since boot-button pushed from microcomputerTGLITCH601Time of worst power glitch seen by microcomputerSTROBE205,7Discussed in the "Passive Mode" section.D1OUT205,7Discussed in the "Passive Mode" section.EVCNTA201EventCntA registerEVCNTB202,3EventCntB registerESTAT202,6Read-write error halt enables, read error conditionsAATOVA205Translate absolute address to virtual1.Read-only to Midas.2.Appears in Test menu.3.Appears in TestAll menu.4.Virtual/absolute stuff applies5.Fake register--artifact of stuff in Midas6.Readout via DMux, so value shown is correct in passive mode.7.Write-onlyMost registers and memories listed above correspond to ones discussed in the "Dorado HardwareManual". Others are discussed in the sections which follow.MDATA and MADDR memories contain words used to report or control the activity of the"Test" and "TestAll" actions discussed later. MADDR also contains DWATCH (used to controlthe DMux address for scoping), MIR-PES (error-reporting), and COM-ERRS (error-reporting),which will be discussed later.TASKN and DEVICE are fake memories used to pass symbolic information from the assembler toMidas in the .mb file, as discussed in the "Dorado Microassembler" document. Their onlypurpose is to provide symbolic equivalents to task and device numbers for ease of debugging.For approximately all registers and memories that contain 16-bit quantities, Midas will evaluateinput of the form "m,,n", storing the value of "m" into bits 0:7 of the word and the value of "n"into bits 8:15.On Dorado, the items that accept "m,,n" are RM, Q, CNT, SHC, EVCNTB, T, STK, STKX, CACHED,VM, DMUX, and $ABS.ЪНЇОf╙pТ─Н!цqН4]Т НG?ОfЯpН#тОbsТ▓Н:О^РtНнНPН#сНнО]▓Н:ОZСuН/НPН#сТюП:Та Н#тОY⌠ТН:ОX2Н/НPН#сП6Н:ОVяН/НPН#сН:ОUpН/Т─НPН#сТП)Н:ОTН/НPН#сП3Н:ОR╞Н/НPН:ОQNН/НPН#сП5Н:ОOМН/Т─НPН:ОN▄Н/НPН:ОM,Н/НPН#сtТП6Н:ОKкuН/НPН#сТіП3ТїН:ОJjН/НPН:ОI Н/НPН#сtТ°ПHН#тОG╗ТН:ОFHuН/НPН:ОDГН/Т─НPН#сТ╣ТІП7Н#тОC├ Н:ОB%Н/НPН#сТП0Н:О@еН/НPН#сП0Н:О?dН/НPН#сП(Н:О>Н/НPН#сП(Н:О<╒Н/НPН#сН:О;AН/НPН#сН:О9АН/НPН#сП4Н:О8─Н/НPН#сП%Н:О5БНKН:О4│НKН:О3 НKН:О1©НKН:О0_НKП)Н:О.ЧНKП<Н:О-²НK НЇО(їqТ■Т∙ПBНЇО&эТП<НЇО#jТиТйП4НЇО!═Т П-Т⌡П-НЇОуТцП&ТдП3НЇОТНЇО≥Т│ПMТ┌НЇОнТьПMТы НЇОТ╩Т╪ПOНЇО▒Т╟Т╠ПOНЇОгТ▀П%Т▄П<НЇОЭТНyО ;uТ╒ПZНyОзТЪ іЇЇ<П\T╣Dorado Midas ManualEdward R. Fiala24 June 19832111. The IM Memory and Virtual AddressesBecause the placement transformations performed by MicroD make it difficult to correlatemicrostore locations with positions in microprogram source files, the Dorado and Dolphin Midasimplementations use a map to transform virtual addresses produced by Micro into absolutemicrostore locations produced by MicroD.Two memories, IMX and IM, each show the microstore. IMX is absolutely addressed; IM,virtually addressed. When you fire up Midas, IM is "empty"; when you load a microprogram, IMis filled with consecutive instructions from your source file, irrespective of where MicroD decidesto place these; the value displayed for an IM address includes both the absolute address assignedto it, the microinstruction, and some other information discussed in the next section.In other words, if your microprogram is 10 words long, the meaningful part of IM is only 10 words long.In this case, if you examine IM addresses greater than 7, the printout will show an absolute address of 7777and zeroes for the rest of the value.Midas will not allow you to modify the mapping between virtual and absolute addresses interactively--youcan only do this by loading a microprogram.To facilitate dealing with virtual/absolute correspondences, Midas has a mode switch that controlsthe way in which registers and memories that normally contain microstore addresses are handled.When you fire up Midas, the display is in absolute mode and the "Abs" action appears in thecommand menu; when you load a microprogram, the display switches to virtual mode and the"Virt" action appears in the command menu. Test actions will switch to absolute mode. Thecurrent mode always appears in the command menu.In virtual mode, the display shows the virtual equivalent for the value in any register thatnormally contains a microstore address. When the value is outside the virtual memory, it prints as7777. To find the absolute value in this case, you have to switch to absolute mode.On Dorado the registers affected by this are CIA, CIAINC, TNIA, BNPC, TPC, TLINK, and OLINK.A fake register called AATOVA converts absolute addresses to virtual. For example, copying thevalue in some RM word into AATOVA will show the virtual equivalent; this is useful whenreturn links are saved in RM words.The general idea is that, if you suspect a hardware problem in the control section, you might workin absolute mode, but in all other situations when a program is loaded you will work in virtualmode, and the complications created by scrambled instruction placement will be concealed.12. Registers and Memories that Contain MicroinstructionsThe MIR and IMOUT registers and the IMBD, IMX, IM, and LDR memories all containmicroinstructions. A middle-button action over the value will print these symbolically on thecomment lines.The value for an IM address is shown as five fields on the display:two PE bits (PE020 and PE2141);Undef and Emu bits;ЪНЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНЇОaвrП'НЇО^eqТЫ ТЗПMНЇО\⌡Т·ПAТ÷НЇОZпТГПXНЇОYТП(НЇОU■ТуПUНЇОSиТ┌П]НЇОQЧТ√П1Т≈П2НЇОP4Т■ПPТ∙НЇОNiТПVНyОK>uТ∙П0Т√П7НyОIщТ┘ПlНyОH|ТП%НyОEчТ· Т÷ПZНyОD}ТП+НЇОA.qТ▐ПbНЇО?dТ≈П'Т≤П8НЇО=≥ТґП7ТўП$НЇО;оТ╡П@ТЁНЇО:Т╡ТЁПFНЇО89pqТП)НЇО4гТАТБПLНЇО2ЩТ┐ПBТ└П!НЇО12ТПTНyО.uТЄП9Т╣П#НЇО*╦qТ▓ПJТ⌠НЇО(НТфТгПBНЇО'#ТП#НЇО#╠Т┐П>Т└П$НЇО!ФТ╔П"ТіП=НЇО ТППNТЯ НЇО░rТП:НЇОqТАП2ТБНЇОSТдП>ТеНЇО┬Т НЇОПCНyО ╔НyОp╟Ї)=П\БDorado Midas ManualEdward R. Fiala24 June 198322148-bit absolute address;bits 0-218 of microinstruction (RSTK, ALUF, BSEL, LC, ASEL);bits 228-418 of microinstruction (BLOCK, FF, JCN).A "1" in PE020 indicates a parity error in bits 08-208 of the value; a "1" in the second bit meansPE in 218-418. Both bits "1" normally indicates a breakpoint. Midas will store the data with badparity, if you request it. Note that these are parity-bad bits; on a write, Midas will computecorrect parity for each half of the microinstruction and xor that with the parity-bad bit; on a read,Midas will determine whether or not the location has correct parity and report accordingly.The "Undef" bit is set when no absolute address is assigned to this virtual address--in this case theabsolute address should print as 7777. The "Emu" bit tells the pretty-print routine to show theinstruction as though it were being executed by the emulator (task 0).IMX, IMBD, MIR, IMOUT, and LDR have a three-field printout in which the two PE bits areleft-most followed by the left and right halves of the microinstruction.IMX and IMBD each address the microstore absolutely and differ only in the way data is readand written. IMX is read and written by executing multi-cycle microinstructions that write themicrostore from the BMux and read the data into Link. This requires that both ContA andContB boards be present (plus ProcH and ProcL to compute parity). IMBD uses manifoldoperations to address and directly write the microstore and uses the muffler system to read out themicrostore; this requires only ContB; however, the addressing method for IMBD makescontinuation from a break impossible, so users should normally display IMX in preference toIMBD.The IMOUT register contains the 448 DMux signals which are the direct outputs of themicrostore, as addressed by the complicated stuff in the control section. At a breakpoint (t0)IMOUT shows the bits that will be loaded into MIR at t2, provided that the state of the branchcondition does not change at t1.The LDR memory is an array in Alto core that contains microinstructions used by Midas whenoperating the hardware; it should ordinarily be of no interest to users, although the "LDRtest"action allows use of instructions stored in this memory for low-level hardware debugging.Note that a bit pattern in LDR identical to one in IMX, IM, or IMOUT in general is not the sameinstruction because the ALUFM memory may contain different contents when the LDRinstruction is executed. The pretty-print procedures account for this difference and show differentstuff for these two cases. However, if you copy an LDR instruction into IM or IMX, watch out!In debugging regular microcode (i.e., any microcode that doesn't test ALUFM itself), thisincompatibility is usually avoided because ALUFM 0 and 16 are assembled with the "B" and"NOT A" alu operations, which are identical to the operations used by Midas.Also note that the microinstruction pretty-print procedure does not have available all of theinformation that the microassembler had when you assembled your program, so the printout is notalways beautiful. The following are deficiencies you should be aware of:From the hardware manual, you will remember that the interpretation of the BLOCK bitdepends upon whether or not the task executing the instruction is the emulator, andmemory references are interpreted differently for the fault and emulator tasks than for ioЪНЇОgpТ─Н!цqН4]Т НG?ОfЯpНyОbqОa▒uОbqНyО` О_─uО` qП2НyО]ШО]nuО]ШqО]nuО]ШqП&НЇОZґТ▌П1ОZ uОZґqОZ uОZґqП"Т▐ НЇОXБТ▀ОXUuОXБqОXUuОXБqТ▄ПEНЇОWТҐП:ТЎП%НЇОUMТ┤ПUТ┬НЇОS┌ТъП0ТЮП+НЇОPТ┌ПaТ┐НЇОNFТ╒П?ТёП!НЇОL{ТПFНЇОI Т║П:Т╒НЇОG?ТПHНЇОCмТ╘ПVТ╙НЇОBТ╞П>Т╟П!НЇО@7ТдПXНЇО>mТьПUНЇО<╒Т┐ПLТ└НЇО:ьТТПCНЇО9 ТеПMТф НЇО7BНЇО3пТЩТЧО3CuО3пqП1НЇО2ТюПIТаО1yuО2qНЇО0;Т⌡П6О/ўuО0;q Т°НЇО.qТО-ДuО.qqНЇО+"ТіП,ТїП.НЇО)WТўП>Т╞П!НЇО'█ТЧПYНЇО$Т│ПSpТ┌НЇО"P qТТП=НЇО ├Т┬ПFТ┴НЇО╩Т⌠ПKТ■НЇОПТЭПEТЩНЇО&ТЎПPТ©НЇО[ТПLНЇОИТыП?ТзНЇОТ┐ПOТ└НЇОTТПHНyОБТ├ПPТ┤НyО ТдТеП?НyОMТ┴П1Т┼П)Ъ xЇ=П](sDorado Midas ManualEdward R. Fiala24 June 198323tasks, so Midas will disassemble this stuff correctly only when it is able to deduce thetask that executes the microinstruction. Midas does have available the Emu bit forinstructions in IM, and if you pretty-print an IM address or an IMX or IMBD addressthat also appears in IM, Midas will be able to distinguish between emulator and non-emulator instructions; however, Midas cannot distinguish fault task microinstructionsfrom other non-emulator instructions, so fault-task memory references will be pretty-printed erroneously. However, Midas very cleverly deduces the task for microinstructionsin MIR and IMOUT in most cases, so the pretty-print will usually be correct for these.Midas is not clever enough to figure out what will be in RBASE when an instruction isexecuted, so RM addresses from your program are not normally pretty-printed; Midasinstead uses the generated names R0 to R17 for RM references.There are many possible assembler macros that you might use to generate constants tocontrol the shifter; for an instruction that does this, Midas will pick one of the forms,probably not the one you used in the source file.Midas sometimes pretty-prints control clauses differently from the assembler. IFUJump'sand IM/TPC read-write clauses are the same; the decision to print Return or CoReturn,LocBr or LocCall, LongBr or LongCall, GBr or GCall is dependent upon Midasdeducing the virtual location for the instruction being printed and finding .+1 in thevirtual space at .+1 in the absolute space, so this might be wrong sometimes.Conditional branches are always printed like "LocBr[addr1,addr2,BC]".Modifying IM words in octal is inconvenient, so you will normally want to use the symbolicmethod below for patching IM.Writeable registers and memories that contain microinstructions (MIR, IM, IMX, IMBD, andLDR) evaluate a special form of input as follows: The first character on the input text line shouldbe "(" to change the values of several fields in the instruction without clobbering other fields, or"[" to reconstruct the value beginning with a no-op microinstruction. This is followed by anumber of clauses of the form "Field_integer" separated by blanks and/or commas. The legalfield names are RSTK, ALUF, BSEL, LC, ASEL, BLOCK, FF, JCN, PE020, PE2141, andEMUL. EMUL, the emulator mode bit affecting pretty-printing of the microinstruction is onlydefined for IM.In addition to "field_value" clauses, Midas interprets the standalone clause RETURN, and severalother items with "[]" enclosing a following argument. GO[va] (local branch), LONGGO[va] (longbranch), and GCALL[va] (global branch) evaluate the argument enclosed in brackets and treat thisas a virtual address in virtual mode or an absolute address in absolute mode; then they store abranch of the selected type in the JCN field of the microinstruction; IFUJUMP[n] evaluates nwhich should result a number in the range 0 to 3, and stores an IFUJump instruction in JCN.When you modify a microstore word (IM, IMX, or IMBD memories), Midas will error-check thatthe target for GO is, in fact, on the same page; Midas will always error-check that the argumentof a GCALL is at a global address. Arguments to GO, LONGGO, and GCALL will usually besimple integers in absolute mode but may be expressions such as FOO+3, where FOO is an IMaddress, in virtual mode.ЪНЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНyОbqТўПEТ╞НyО`SТсПCТтНyО^┴Т║Т╒П9НyО\ЎТ╟П&Т╠П.НyОZСТГТХП?НyОY)ТоП3ТпП"НyОW^Т┌П$Т┐П5НyОU■Т²П&Т·П0НyОR"Т≈Т≤П8НyОPWТЁТЄП4НyОN▄ТП=НyОKТ╘Т╙П=НyОIPТ╛ТґПAНyОG┘ТП1НyОDТ┘Т├ПIНyОBIТ▓ Т⌠ПKНyО@~ТЫТЗПBНyО>ЁТ╦ПKТ╧ НyО<ИТП.ТНyО;ТПEНЇО7╛ТфТгП?НЇО5БТНЇО2pТпТяПEНЇО0╔Т─Т│ПUНЇО.зТ≈Т≤П^НЇО-ТоП+ТпП1НЇО+EТ╘Т╙ПGНЇО){ТЦТДП?НЇО'╟Т╚П\НЇО%ЕТНЇО"sТ┘П6Т├П*НЇО ╘Т█ Т▌ПSНЇОчТ└Т┘ПJНЇОТ╗Т╘ПSНЇОIТ╣ПEТІНЇО~Т╚Т╛ПOНЇОЄТ▄П&Т█П4НЇОИТ≥П6Т П*НЇОТ≤П#Т≥П3НЇОTТ≈ПLТ≤НЇО┴Т :ЇB=ПWиEDorado Midas ManualEdward R. Fiala24 June 19832413. Task-Specific RegistersMidas treats all task-specific registers (T, RBASE, TLINK, OLINK, TPC, TIOA, MEMBASE, andMD) as 20-word memories. In other words, "T 6" is the T-register for task 6.In addition, a special kludge allows you to display the 21st word (i.e., "T 20", "RBASE 20", etc.)and have that be interpreted as the register for the currently selected task. The currently selectedtask is the value in TASK; the TASK register is an artifact of Midas that is initialized to CTASK(i.e., to the "current task") at breakpoints.In other words, when a microprogram halts at a breakpoint or because of a mouse-abort, CTASKis read from the DMux--suppose that it contains 6. This value is copied into TASK. If "T 20","TLINK 20", etc. appear on the display, these will show values for task 6. The idea is that youcan change the display for all eight task-specific registers by storing a new value into TASK. Thetask selected by TASK is also the one started by "Go", "SS", etc. as discussed later.The hardware's LINK register, suppressed by Midas, is shown as the current task's TLINK word.The OLINK memory shows the absolute value in TLINK less 1. When microstore addresses aredisplayed in absolute mode, this is useless. However, in virtual mode OLINK will usually showthe location that last did a CALL. This is useful in diagnostics which do BRANCH[ERROR],where ERROR is at a global call location. After one of these branches, OLINK shows thelocation that made the error branch, while TLINK shows an unrelated location.14. BR Addressing KludgesBR 40 is another addressing kludge used to represent the "currently selected" base register, or BRMEMBASE[TASK] (i.e., the BR location pointed at by MEMBASE for the currently selectedtask).The BRX memory is another addressing kludge that allows the 4 BR words pointed at by MemBXto be displayed.15. STKX KludgeIn debugging emulators, it is frequently desirable to view the STK entries relative to STKP ratherthan relative to STK 0 (i.e., relative to the top-of-stack rather than the bottom-of-stack). To aid inthis, Midas defines STKX as an alternate memory for STK. STKX[n] shows STK[STKP-n], wherevalid values for n are 0 to STKP-1; hence, the top stack entries are STKX 0, STKX 1, etc.STKX does not allow you to view entries on the wrong side of the stack pointer, and the displaywill preface those names with "~", indicating unreadable, if they appear on the display.16. Memory System Registers and MemoriesThe cache, map, and storage arrangement may vary from one Dorado to another but Midas candeduce the configuration by reading the mufflers and looking at the CONFIG register; Midasdoes this automatically when you attach to a new machine or when you execute the "Config"action. Midas adjusts to the configuration by varying the lengths of its ROW, CACHEA,CACHED, and MAP memories and adapting its algorithms for reading and writing these.ЪНЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНЇОaвrНЇО^eqТ├П(Т┤П1НЇО\⌡ТПMНЇОY)Т▓П<Т⌠П&НЇОW^П5pqТ■НЇОU■Т▌П[Т▐НЇОSиТП-НЇОPWТ▌ПIТ▐НЇОN▄Т√П8Т≈П'НЇОLбТ≥ПOТ НЇОJВТ┼ПGТ▀НЇОI-ТПUНЇОE╩Т▒П>Т▓НЇОCПТ⌠ПYНЇОB%Т·П^НЇО@[Т╟П(Т╠П1НЇО>░Тм ТнПLНЇО<фТПMНЇО89rНЇО4гqТ┴П\Т┼НЇО2ЩТхТиП:НЇО12НЇО-юТ│ПFТ┌НЇО+ЖТНЇО'irНЇО#ЬqТ▀П[Т▄НЇО"-Т┐ПAТ└П&НЇО bТ│Т┌ПBНЇО≤ТхПLТиНЇО&Т▒Т▓ПVНЇО[ТПXНЇОоrП)НЇО]qТ═П0Т║П)НЇО▓Т╩П0Т╪П*НЇО хТ╧П,Т╨П-НЇОЩТИП:ТЙНЇО 3ТВП4ТЬЪ▌Ї Л=П^Dorado Midas ManualEdward R. Fiala24 June 198325Midas always uses task 17 (the fault task) and srn 1 (the fault task srn) to access BR, ROW,CACHEA, CACHED, MAP, and VM. Consequently, pipe entry 1 is smashed and (for CACHEDand VM) MD is smashed, which may prevent continuing from a breakpoint, as discussed later.ROW shows the cache flags and address bits in each of the four columns of a cache row and thevictim and next-victim for the row on five consecutive lines of a display column. The length ofthe ROW memory is adjusted to the number of rows in the cache. Displaying an address inROW is normally the most convenient way to view the cache; you can prettyprint the cache flagsand address bits for each column independently, and this also shows the 16 data words in theassociated munch (if any).CACHEA is a memory of length equal to 4 times the number of cache rows; it shows the cacheflags and address bits for a single entry in the cache. In a 100-row cache, the entries for the fourcolumns in row i are CACHEA i, CACHEA i+100, CACHEA i+200, and CACHEA i+300.CACHEA is intended primarily for the "Test" and "TestAll" actions; on the display, it willusually be more convenient to look at ROW.CACHED is a memory containing all the data words in the cache; word m in the munch for rowr and column c is at CACHED 208*nrows*c + 208*r + m. CACHED is intended primarily for"Test" and "TestAll".Addresses in the MAP memory are displayed with the MapPE and PgFault bits in a 2-bit fieldfollowed by wp, dirty, and ref bits in a 3-bit field followed by the 16-bit ra field on the display.When a MAP address is written, ref is zeroed and map parity is always written correctly; dirtyb(the copy of dirty) and MapParity are not readable (they appear in CONFIG in other situations).VM accesses the virtual memory using Fetch_ and Store_ with the current contents of the mapand cache; map and data error faults are not detected or indicated in any way, and the"RunRefresh" and "EnRefreshPeriod" clock enables must be true for storage to work properly.Midas sets the length of VM to the largest limit imposed by the map and cache geometries.Although VM appears in the "Test" menu, the user must setup the cache and map reasonably andselect a suitably small sub-range of addresses in LOW-ADDR, HIGH-ADDR, and ADDR-INCbefore attempting to test VM. Midas uses a user-settable base register called VMBASE, initially 0,to offset the address specified by the user. VMBASE is an address in the fake MADDR memory.In looking at VM, it is sometimes desirable to determine the MAP and ROW entries throughwhich a VM word is accessed; if you middle-button any VM address, these will be displayed onthe comment lines.Midas does not provide any direct method of accessing storage; the user has to setup CACHEAand MAP with appropriate values and then use VM to do this.Note: The code for accessing CACHEA and CACHED is complicated and unlikely to workunless the memory system is functional; these can be tested with "Test" and "TestAll" but themore basic "ProcVA" test, which exercises VA paths in the memory system, may be more helpfulin isolating problems.НЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНЇОbqТЎПWТ©НЇО`SТ┤Т┬П6НЇО^┴ТўП3Т╞П'НЇО[Т░Т▒П@НЇОYLТ²ПIТ·НЇОW│Т╧Т╨П;НЇОUЇТ▐П#Т░П;НЇОSЛТЄТ╣ПHНЇОR"ТНЇОN╟Т≤ПPТ≥ НЇОLЕТ▄Т█ПOНЇОKТ© ТюpqpqpqpqpqНЇОIPТтТуПHНЇОG┘ТП*НЇОDТ▌ПDpqТ▐ НЇОBIpqТ∙pqОA╪uОBIqpqОA╪uОBIqpqТ√pqП#НЇО@~ТНЇО=Т╔П2ТіpqpqНЇО;AТ·pqpqpq Т÷П$pqНЇО9wТ⌡pqП+Т°pНЇО7╛qТ⌠pqТ■pqП>НЇО4:Т÷ПSТ═НЇО2pТТТУП?НЇО0╔Т╞ПLТ╟НЇО.зТхПGТиНЇО-Т└П\НЇО+EТ╞Т╟ПKНЇО){Т┐П>Т└П%НЇО'╟Т┤ПEТ┬НЇО$>Т╧П+Т╨П-НЇО"sТ°ПYТ²НЇО ╘ТНЇО7Т═П+Т║П0НЇОlТП;НЇОЗТфП>ТгНЇО0Т╞ПGТ╟НЇОeТ▐П*pqП0НЇО⌡ТDЇT=ПUЇ_Dorado Midas ManualEdward R. Fiala24 June 19832617. Memories and Registers Associated With the DMuxAt those times discussed later, the 40008 DMux signals (or mufflers) are read from the hardwareand stored in the first 2008 words of a table. These are arranged so that hardware DMux address0 corresponds to bit 0 of word 0 in Midas' DMUX memory, hardware address 178 to bit 178 ofword 0, .., up to hardware address 37778 in bit 178 of word 1778. Then the value on the BMuxand the error status, which can also be read passively, are appended to the table. Finally, tabledata is rearranged, so that the DMUX memory looks as shown in the tables later.Inside Midas associated with the DMUX memory are four separate tables, named as follows:DMuxTabcurrent DMux readoutOldDMuxTabprevious DMux readout when running the simulatorDChecksignals checked by the simulatorDWrongerrors detected during simulationThe last three tables are only significant when the DMux simulator is used by the "SimGo" and"SimTest" actions, as discussed later. In other words, when one of these actions halts,OldDMuxTab holds the t0 DMux readout, DMuxTab the t2 readout, and DWrong the errors thatwere detected in DMuxTab. DCheck is initialized by Midas to values that are reasonable for theboards that are plugged in, and the "Config" action also initializes DCheck to reasonable values;the user may manually modify DCheck, as discussed below, in order to disable checking of signalsthat are incorrectly simulated (This won't be particularly useful after the simulator is thoroughlydebugged).Normally, DMux addresses and registers derived directly from DMux readout (i.e., MIR,IMOUT, MCR, IMBD, DHIST, VH) show values taken from DMuxTab. However, the user mayexecute the "DMux" action with various button combinations to view the other three tables; thename printed for this action in the command menu will be "DMux", "DWrong", "DChk", or"OldDTab" according to which table is currently viewed. When the action is executed with theright (bottom) mouse button, OldDMuxTab values are viewed; both left and right buttons showsDCheck; middle button shows DWrong. The symbolic names of the first 11 errors in DWrongwill also be printed on the comment lines when the middle button is released.DMUX prettyprinting (middle button over value) of regular (DMuxTab or OldDMuxTab) valuesworks differently from DWrong and DCheck pretty-printing. Regular printout of single-bit itemsshows symbolic names of "true" signals; "false" signals are not printed. In other words, low-truesignals are printed when 0, high-true when 1. Multi-bit items (e.g., foo.0, foo.1, foo.2) are alwaysprinted (e.g., foo=3).You should note that modified printout of DMUX also affects registers whose values are obtainedby reading the DMux; this includes MIR, MCR, and IMOUT (but not IMBD). The DMUXmemory itself and IMOUT are read-only except when DCheck is being shown. MIR and MCRare writeable when DMuxTab is viewed but read-only when OldDMuxTab or DWrong is viewed;writing modifies DCheck when DCheck is viewed.The DHIST memory contains a DMUX bit address in bits 408 to 538 (displayed left-most byMidas) and a history of the last 408 values read from the DMux in bits 0 to 378 (displayed as thetwo right-hand fields by Midas). This memory may be useful in checkout of multi-state stuff inthe memory and IFU sections of the machine when the DMux simulator is unable to detectЪНЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНЇОaвrП4НЇО^eqТ≤П(О]ьО^eТ≥П)НЇО\wТ┴О[ЙО\wТ┼П2НЇОZ┼Т П#Т⌡П(ОYЩОZ┼ ОYЩОZ┼НЇОX°Т■П'ОXОX°Т∙ ОXОX°ОXОX°НЇОVўТ║ПRТ╒НЇОTЦТПOНЇОQqТхП0ТиП(НyОMЪН░ТНyОL5 Н░П0НyОJjН░НyОH÷Н░П!НЇОE-Т≥Т ПUНЇОCcТ П*ТП.НЇОA≤Т▐ОAuОA≤qОAuОA≤qП$НЇО?нТ▒П_НЇО>Т≥ Т ПVНЇО<8Т┘П;Т├П%НЇО:nТєПUТ╔ НЇО8ё НЇО51ТЖПIТВНЇО3gТ┼Т▀П7НЇО1°Т²Т·ПLНЇО/яТ╧П@Т╨НЇО.Т═П/Т║П.НЇО,НЇО!═Т⌠ПbНЇОуТ░П^Т▒НЇОТНЇО≥Т┬П&Т┴П9НЇОнТ╦П"Т╧П.НЇОТ⌡П8Т°НЇО9Т▀П7Т▄НЇОnТП.НЇОЭТ╨П7ОoОЭОoОЭТ╩НЇОТ┴П#О │ОТ┼О │ОНЇО Т°ПVТ²НЇО VТх ТиПHЪ dЇ <П]ЭDorado Midas ManualEdward R. Fiala24 June 198327problems. Each time the DMux is read the 408-bit data field of each word in DHIST is left-shifted 1 and the new value brought into the low bit.The VH memory provides another view of DHIST. Word 0 in VHIST shows the 408 DHISTsignals at t0, word 1 at t-1, word 2 at t-2, etc.When it is done reading the mufflers or done with a manifold operation, Midas loads the DMuxaddress register with the value contained in DWATCH, an address in the MADDR memory. Thismeans that during a "Go" or when Midas is not reading the mufflers, a scope probe attached tothe DMux data line on the backpanel will show the DMux signal selected by the low-order 11 bitsof DWATCH. However, if DWATCH contains 0, Midas will be turning control of themuffler/manifold system over to the baseboard at regular intervals, and the microcomputer willsmash the DMux address.18. Interface RegistersCPREG is one of the central interface registers used by the Alto in loading information intoDorado. It can be tested, but should not otherwise be of interest except in passive mode. Midasfreely smashes the value in this register.MIR is also special. It is loaded directly from the Alto and read via the DMux; Midas faithfullyrestores MIR after executing instructions.19.ConfigMidas automatically determines the hardware configuration when it connects to a particulardorado by means of DMux signals that it can read from each board. The configuration consists ofthe following parameters:which boards are plugged in--debugging is frequently carried out with some boards disconnected;Map ic size;storage ic size;cache size (4K words or 16K words);whether the 16th bit in a cache entry is used as a parity bit or an address bit;number of storage modules.Midas automatically adjusts its length parameters for VM, CACHEA, CACHED, ROW, MAP,etc., enables and disables various tests in the Test and TestAll actions, and modifies the behaviorof SimTest and SimGo according to which boards are plugged in.The automatic determination of the hardware configuration should not fail, but if it does, theConfig action can be executed to manually set the configuration by means of actions in asubsidiary menu. Manually controlling the configuration may also be useful when testing withSimTest or SimGo.20.SetClkThe baseboard microcomputer presently initializes the clock to a 30 nsec period (= 60 nsecinstruction cycle) when the boot button is pushed. The current clock period can be determined bypretty-printing the value of the CLKRUN DMux word which normally appears on the MidasНЇОgpТ─Н!цqН4]Т НG?ОfЯpНЇОbqТ╟П,Оa▒ОbТ╠П*НЇО`0ТП5НЇО\ЎТ╞П#Т╟П(О\1О\ЎНЇОZпТОZCuОZпqОZCuОZпqНЇОW│Т∙Т√ПMНЇОUЇТ│П,Т┌П.НЇОSЛТ≥П9Т П$НЇОR"Т┌П(Т┐П7НЇОPWТП@ТНЇОN▄ТўПKТ╞НЇОLбТНЇОH6rНЇОDдqТдП/ТеП-НЇОBЫТ▐П[Т░НЇОA.ТП*НЇО=╪Т▓ПVТ⌠ НЇО;РТП*НЇО7frН2НЇО3ТqТКПZНЇО2)Т┌П]Т┐НЇО0_ТНyО-²uП_НyО,НyО*∙НyО)П#НyО'█ПPНyО& НЇО"╨qТЎТ©П4НЇО ОТ≈Т≤ПRНЇО%ТП>НЇОЁТЎТ©ПQНЇОХТЕП-ТФП+НЇОТЁП<ТЄП!НЇОSТНЇОгrН2НЇОUqТяП%ТрП5НЇО┼Т─П*Т│П7НЇО юТЎТ©П5 Ї y<П]╣"Dorado Midas ManualEdward R. Fiala24 June 198328display.The "SetClk" action allows the clock period of the mainframe to be specified from a subsidiarymenu. You will probably be able to continue from a break after changing the clock speed, butMidas warns you that continuation is impossible.21. ResetThe "Reset" action shows an elaborate subsidiary menu with many options. The options are: runenables for different stuff; parity-error enables for the different data paths that are parity-checked;and initialization of memories.The general ideas that determined exactly how "Reset" is implemented are as follows: First,memories and registers should be reset only if they have to be for some reason. For example,memories that are parity-checked, such as T, RM, and STK, have to be reset to prevent parityerrors when you start running a program; TIOA has to be reset in case some io device has variantbehavior when TIOA contains its device number (building an io device that did this would be apoor idea); it is desirable to reset IMX and IFUM before loading a program, so that run-awaybranches and out-of-control programs will be trapped. However, other memories and registerssuch as RBASE, MEMBASE, Q, CNT, etc. need not be reset--your microprogram should containcode to initialize these, so Midas doesn't have to.Next, memories that require a long time to initialize, such as MAP (9 seconds now, 35 or 140seconds with larger ic's in the Map), should be optionally reset so that you won't have to wait fortheir initialization unnecessarily.Also, memories loaded by a microprogram (IM, IFUM, RM, ALUFM, and STK) should beoptionally reset, if at all; if they are optional, you will be able to reset other parts of the machinewithout smashing your program. However, there does not seem to be any advantage in initializingALUFM, so this memory is never initialized.Each option is of an on-off form. The current state of the option is shown on the comment lines,while the other state appears in the command menu. The options as originally chosen arereasonable for a total reset, such as you would carry out at the onset of a "RunProg" commandfile; you may also want to turn on MAP initialization.To carry out a reset, you bug the sequence of options you want, then bug the "Do-It" menu item.When you bug "Do-It", initialization is carried out as follows (not exactly in this sequence sincesome initialization is done twice):Run enables (RunRefresh and EnRefreshPeriod) are set as chosen;Parity-error halt enables and MIRDebug are set as chosen; Midas remembers the halt enable settings so thatthey can be simulated for "SimGO" (discussed later) and remembers the setting of MIRDebug, so that itcan warn against continue after breaks with MIRDebug true;Manifold stuff used for testing IMBD is cleared;Midas error counters MIR-PES and COMM-ERRS are cleared;Hold and task simulators are cleared;ALUFM 0 and ALUFM 16 are loaded with the "B" and "NOT A" alu controls needed by Midas;ЪНЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНЇОbqНЇО^╛ТєПBТ╔НЇО\АТ║ПLТ╒НЇО[ТП0НЇОV┼r НЇОSqТ┐ПHТ└НЇОQNТ├П5Т┤П2НЇОO┐ТНЇОLТцП)ТдП3НЇОJGТ╙Т╚ПGНЇОH|ТґПMТўНЇОF╡Т┤ПXТ┬НЇОDГТ°Т²П>НЇОCТ╚ Т╛ПNНЇОARТ╧ПNТ╨ НЇО?┤Т⌠ Т■ПJНЇО=╪ТП3НЇО:KТ╠П"Т╡П:НЇО8─Т░П0pqТ▒П#НЇО6╣ТП#НЇО3CТяТрП6НЇО1ypТ▓qПKТ⌠НЇО/ўТ┌П3Т┐П-НЇО-ДТП+НЇО*rТ┬ПRТ┴НЇО(їТшП7ТэП!НЇО&эТ÷Т═ПGНЇО%ТП6НЇО!═Т├П5Т┤П*НЇО.Т·ПCТ÷НЇОcТП#НyО╒uП?НyОmТ└П1Т┘П9НyОТ·П3Т÷П2НyО╛ТП:НyОwП0НyОCП7НyОП%НyОзТиПEТйЪіЇЇ<П\T$Dorado Midas ManualEdward R. Fiala24 June 198329The IFU is reset;TestSyndrome is loaded for normal error-correction;Several IOFetch_'es are done in task 2 to make sure that Asrn is .ge. 2 after power up;Tasking is turned on;Junk io, the fault task, and io devices are reset;If MAP initialization is selected, each MAP address is loaded with Dirty and a pointer to the correspondingabsolute page;If MD initialization is selected, then CACHEA is loaded to map the first 4k (or 16k) of virtual memory, BRand CACHED are zeroed, and, for each task, the MD tag is reset, T and TIOA are zeroed, TLINK andTPC are loaded with 7777;RM and STK are optionally zeroed;If IM initialization is selected, then absolute mode is selected, IM is made empty, and every IMX address isloaded with "Branch[.], Breakpoint" except that 7776 is loaded with "Return, FreezeBC, Breakpoint" for the"Call" action;If IFUM initialization is selected, then the Reschedule condition is turned off, and each IFUM address isloaded with the descriptor for a two-byte regular opcode with no operand, using MemBase 0 and RBase 1,starting at IMX 0.MCR is loaded with NoRef and ProcSRN with 0;The test control stuff BITS-CHECKED, LOW-ADDR, HIGH-ADDR, ADDR-INC are reinitialized;After the reset is complete, Midas reads the DMux and checks the run-enable initialization, mostof the control section initialization, and halt-enable initialization; if any failures are found, theerrors are reported on the comment lines.The "Go" action performs a subset of "Reset" prior to starting at a new address, as discussedlater; parity-error halt enables can be modified without resetting anything else by writing an octalnumber into the ESTAT register.ЪНЇОf╙pТ─Н!цqН4]Т НG?ОfЯpНyОbAuНyО` П3НyО]ьПWНyО[єНyОYoП2НyОW;Т┬Т┴ПVНyОUзТ НyОSіТ│П&Т┌ПDНyОREТ²ПEТ·НyОPДТНyОN╟П!НyОL{Т┘П7Т├П5НyОKТ▀П7Т▄П3НyОI╨Т НyОG┘Т²ПKТ·НyОF$Т▐Т░ПLНyОDдТНyОB▐П,НyО@[ПUНЇО=qТ≈П(Т≤П8НЇО;AТ╩ Т╪ПWНЇО9wТП)НЇО6Т╣П2ТІП+НЇО4:Т░П0Т▒П4НЇО2pТєЇ2)<П5Б╟Dorado Midas ManualEdward R. Fiala24 June 19833022. Loading ProgramsThe "Ld", "LdSyms", and "LdData" actions are used to load micro-binary files into the machine.These actions are executed by first typing a list of file names (default extension ".mb") separatedby commas, then bugging "Ld" or "LdSyms" (typing ";L" is equivalent to bugging "Ld"). Theseactions require confirmation by , "Y", or "." iff a previously-loaded program is beingoverwritten; in a command file where it is not known whether or not another program is beingoverwritten, a "Confirm" action should precede the load action, as discussed earlier."Ld" loads the entire .mb file--symbols into the Midas symbol table and data into the hardware."LdSyms" loads only the address symbols and IM mapping table from the .mb file. This may beuseful when reattaching Midas to a machine that is already running a microprogram."LdData", (in command files but not available interactively), loads only the data blocks from the.mb file. "LdData" is provided so that a microprogram can be loaded without cluttering thesymbol table--this is primarily for Midas initialization and should not be of frequent use to users.On Dorado, the DMUX, MADDR, MDATA, $ABSOLUTE, $ABS, and MSTAT memories are treated asexceptions by "LdData"--symbols for these are loaded anyway.Midas uses several 1024-word core buffers (about 8 on Dorado Midas) and the Swatee file tomanage its symbol table and virtual memory mapping information; the largest existing programsuse 10 buffers for VM information and about 25 more (out of 64 available on Swatee) forsymbols. For nearly all symbol and VM accesses, Midas will reference only one or two symbolblocks, so there should be no appreciable slow down when handling large programs.The symbol table management algorithm used by Midas is an extremely fast merge that works well whenthe symbol table is nearly empty at the onset of a load but suffers somewhat from block fragmentationwhen the initial symbol table has many items.To avoid fragmentation, don't load one microprogram on top of another--use "RunProg" to reset the symboltable, then do the "Ld". It is also a good idea to assemble microprograms as a single .MB file. AlthoughMidas can load multiple .MB files (typed as a list separated by commas), this will fragment the symbol tableand cause extra thrashing.These recommendations follow because Midas takes advantage of alphabetical address ordering in .MB filesto pack its symbol buffers nearly full. But when subsequent files are loaded, the symbol buffers willfragment to about half-full, symbol buffer swapping will result, and symbol searches will be longer.Midas uses the symbol table in two ways: looking up the value of a symbol, requiring at most one diskaccess; and searching for the symbol in a particular memory which best matches a value, requiring at mostone access for RM, BR, DEVICE, and TASK address symbols, or at most two accesses for IM addresssymbols; the best matching value for addresses in all other memories is determined by scanning every block.Searching every block requires about (.22 seconds * no. symbol blocks) - (.15 seconds * no. blocks in core)or about 4.7 seconds for the largest program thus far. However, since best matches for the five mostimportant memories are obtained quickly, it will rarely be necessary to wait for a search.In most situations where a "Ld" is going to be done, many other actions will also be carried outto setup the display appropriately for the program and to initialize the hardware by doing "Reset"or whatever. For this reason, you will ordinarily want to define a command file that does all theseother actions as well as the "Ld" and you will ordinarily do "RunProg" on this command file;direct use of "Ld" in the command menu will be rare.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrНЇО^eqТ▌ПLТ▐НЇО\⌡Т∙П#Т√П@НЇОZпТ▀П8Т▄П$НЇОYТвПZНЇОW;Т╔П\НЇОUpТПUНЇОQЧТ Т⌡ПQНЇОN▄Т▀Т▄ПIНЇОLбТПRНЇОIPТ√Т≈ПFНЇОG┘ТбП6ТцП%НЇОE╩Т▓ПdНyОBЫsТ╔П3ТіП"НyОA≤ТП<НЇО>JqТ╪П<ТҐНЇО<Т╒ПCТёНЇО:ЄТвПHТьНЇО8ЙТёП\НЇО7ТПQНyО4^sТ²П-Т·П6НyО2ЩТ╚Т╛ПKНyО1°ТП-НyО.ЧТ└ПTТ┘НyО-²Т▄П`Т█ НyО,<Т│ПHТ┌П$НyО*шТНyО(=Т■ПJТ∙НyО&эТ╩ПNТ╪НyО%|ТзП#ТшПAНyО"щТ ПfНyО!}Т░ПFТ▒П#НyО ТўТ╞ПMНyО╩Т└П^Т┘НyОZТ█ПMТ▌НyОЫТІП`ТЇНyО≥ТПZНЇОJqТ≈П+Т≤П5НЇОТ┤П&Т┬П<НЇО╣Т─ПAТ│П#НЇОЙТ╛П%ТґП7НЇО ТП4ЪчЇы=ПX2BDorado Midas ManualEdward R. Fiala24 June 19833123. Dump and CmprBoth "Dump" and "Cmpr" require confimation by , Y, or "." They accept the name of amicroprogram (default extension ".mb") on the input text line. If the input text line is empty,then the file name is defaulted to the name of the program last loaded."Dump" deletes forward reference fixups left by Micro (which never occur on Dorado or Dolphinbecause MicroD does these) and compacts both data and addresses to use less disk space and loadmore quickly later.Also, if undumped .MB files contain forward references, they cannot be used with "Cmpr" (noproblem on Dorado or Dolphin).Note that only memory words loaded by Load are dumped--you cannot patch unused locations,dump the program, and expect the patches to survive. (Suggestion: assemble extra locations as apatch area with your microprogram, so that you can patch and dump during debugging.)"Cmpr" compares data currently in storage against data in the file and reports differences on theMidas.Compare file.In microprograms, avoid loading initial values into memory words modified during execution. Theusefulness of "Cmpr" is enhanced when programs are clean, because no fictitious errors will be reported.For diagnostics, "Cmpr" can report what has been smashed when something goes off the deep end--this hasfrequently been helpful.Following system microcode crashes, "Cmpr" may provide the only clue about the nature of an intermittentstorage failure.24. Brk and UnBrkOn Dorado breakpoints are created by deliberately storing bad parity in both halves of amicroinstruction. Since double parity failures are highly unlikely, there is usually no ambiguitybetween deliberately set breakpoints and hardware failures.Since Dorado does not halt until t2 of the instruction containing a parity failure, the break willoccur after the instruction containing it has been executed.Since the two parity-bad bits are part of the value displayed for an instruction, it would bepossible to insert or remove a breakpoint by examining an instruction and storing 3 or 0 into theparity-bad field; however breakpoints are inserted and removed often enough to warrant an easiermethod for doing this. The "Brk" and "UnBrk" actions are provided for this purpose."Brk" inserts a breakpoint in the IM or IMX address typed on the input text line. The addressmust be typed--there is no default break address. You will normally find it faster to type"address;B" to insert a breakpoint."UnBrk" removes a breakpoint. If no text is typed, the address defaults to the breakpoint thatcaused the last program halt or to the address of the last breakpoint inserted. You will normallyfind it faster to type "address;K" or ";K" to remove a breakpoint.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrНЇО^eqТ∙П9Т√НЇО\⌡Т╚ПFТ╛НЇОZпТПGНЇОW^Т├ПRТ┤ НЇОU■Т┬П_НЇОSиТНЇОPWТ╚ПCТ╛НЇОN▄ТНЇОKТб pП+qТцНЇОIPТ▄ПCТ█НЇОG┘ТЫП"ТЗП2НЇОDТ√ПBТ≈НЇОBIТНyО?┤sТЕП`НyО>&ТєП^Т╔ НyО;┬Т┬ПPТ┴НyО:'ТНyО7┴Т▀П[Т▄НyО6(ТНЇО1©rНЇО.MqТЯПSТРНЇО,┐Т╚Т╛ПJНЇО*╦ТП;НЇО'FТ╘П"О&╧sО'FqП0Т╙НЇО%|ТpqП1НЇО" ТнТоПTНЇО ?Т▓Т⌠ПOНЇОtТ▀П2Т▄П.НЇО╙ТПTНЇО8Т°П3Т²П+НЇОmТшП;ТэНЇОёТП#НЇО1ТїПOТ╗НЇОfТ■ПOТ∙НЇО⌡ТПB юЇT<ПYЇDorado Midas ManualEdward R. Fiala24 June 19833225. Go, SS, Proceed, OS, and CallThese are actions that result in the microprocessor executing instructions from the control storestarting at the selected address; "SimGo", which will be discussed later, also does this. Each ofthese accepts an input argument (optional except on "Call") that must evaluate to an IM or IMXaddress; a simple number is defaulted to an IMX address in absolute mode or an IM address invirtual mode. If the optional argument is omitted, Midas will continue from the last break.When you start at a new address, the value in TASK (lower left-hand corner of the normaldisplay) is the task activated. TASK is initialized to the value in CTASK (i.e., to the task forwhich an instruction was about to be executed) when Dorado halts or when you abort. You mustchange TASK on the display to initiate execution for a different task.The distinctions among these actions are as follows:"Go" and "Proceed" will start the machine running and wait either for it to halt or foryou execute the "Abort" or "Dtach" actions which are displayed during the "Go".When going or proceeding at a new address (as opposed to continuing from the lastbreak), "Go" will reset io devices and the control section, while "Proceed" does not dothis; in other respects these actions are identical."SS" (single-step) executes one microinstruction.Although "Go" and "SS" (single-step) appear in the command menu, you will probably discoverthat it is faster to type "address;G" to Midas, an alternative to "Go", or "address:", analternative to "SS"; "Proceed" is only executable by typing "address;P." Similarly, ":" isequivalent to a continue-"SS" and ";G" or ";P" (proceed) to a continue-"Go"."OS" (opcode-step) keeps single-stepping the machine until either you execute the"Abort" action, a halt condition occurs, or an IFUJump has been executed. In otherwords, it simulates a "Go" with repeated single-steps, but stops after the next IFUJump.This is intended to facilitate debugging emulators that use the IFU.There are some hardware restrictions on single-stepping discussed in the next section. The mostserious of these is that it is illegal to single-step across an instruction that does Fetch_ and _Md.Since this is expected to be common in emulators, there will be many times when OS doesn'twork."Call" allows a microprogrammed subroutine to be called with an optional argumentpassed in T. By convention both the microassembler and the "Reset" action plant a"FreezeBC, Breakpoint, Return" microinstruction at IMX 7776. A call is initiated bytyping "SUBR(ARG)" or "SUBR()". This causes ARG (if any) to be evaluated andstored in T; LINK is loaded with 7776; then "SUBR;G" is done. If the subroutinereturns (to 7776) Midas prints an appropriate message.Note that subroutines called this way need not start at "call" locations in the microstore becauseLink is loaded prior to jumping to the starting address."SimGo" (simulated-go) is a variation of single-step that keeps single-stepping themachine until either a halt condition occurs or the DMux consistency checker finds anerror, as discussed later.Before stepping or going at a new address (as opposed to continuing or proceeding), Midas carriesНЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrП"НЇО^eqТ╞ПSТ╟ НЇО\⌡Т╒ПNТёНЇОZпТ▒Т▓П?НЇОYТ П\НЇОW;ТнПLТоНЇОSиТйТкПAНЇОQЧТ╟П4Т╠П-НЇОP4Т┤Т┬ПIНЇОNiТПFНЇОJВП4НyОG┘Т⌡Т°П@НyОE╩ТАПEТБ НyОCПТаПQНyОB%Т═ПWНyО@[ТП4НyО<ИП1Н:О:'sТ█П:Т▌П!Н:О8фТш ТэПOН:О7fТжПTТвН:О6ТПLНyО2ІqТТТУП?НyО0ЛТ╣П?ТІНyО/!Т▓ПJТ⌠ НyО-VТПDН:О*∙sТ▒ПDТ▓Н:О)4Т┌Т┐ПGН:О'сТ═П<Т║Н:О&sНyО#$qТфП*ТгП'НyО!YТҐТЎПIНyО▐Т╩П2Т╪П"НyОдТюТаП-НyОЫТЎТ©П?НyО/ТП6Н;ОmsТ▌Т▐ПMН;ОТП8НyОЎqТШП(ТЭП+НyОСТ╗Т╘ПAНyО)ТНЇОЇТ├Т┤ПRЄЇp<П\⌡3Dorado Midas ManualEdward R. Fiala24 June 198333out an extensive reset sequence, as follows:IO devices and fault task are reset.Ready flipflops, CTASK, CTD, etc. are cleared by executing "TaskingOn", "No-op", andthen "Goto[7777], Block" for each task. Your microprogram should probably load IMX7777 with some instruction to handle bogus task wakeups.TPC is set to 7777 for every task except the one being started.Memory "tag" mechanism is NOT reset.The IFU and Reschedule condition are NOT reset.When the microprocessor halts after a breakpoint, due to an error, or because you aborted, Midasprints the location of and reason for the halt and saves the information that it needs to continue.The form of the printout is "task:address". Subsequently, if you attempt to continue, Midasrestores the hardware as nearly as possible to its state at the break before continuing.The primary error indicators for a break are in ESTAT; Midas analyzes these and other DMuxsignals such as "Task2Back", "Task3Back", "_MDSaved", etc. and pretty-prints a message aboutthe reason for halting and the task that executed the instruction that caused the halt.There are many complications surrounding Midas' ability to restore the state of the program, afterdoing other things, so that continuation is possible. These are discussed in the next section.When these complications are insurmountable, "passive mode" may be used as discussed later.26. When Registers are Read/Written--Restrictions on ContinuingWhen a microprogram halts at a breakpoint or due to a mouse-halt, Midas has two objectives: toread the contents of registers and memory addresses so that they may be shown to the user, and tobe able to continue from the interrupt or breakpoint. The methods for reading machine state aredetailed in the "Dorado Debugging Interface" document and outlined here.Midas first reads the DMux (which includes MIR, MCR, and some other items), BMUX, andESTAT (error status); these are read first to capture their values before they change. Since all ofthese items are readable without issuing any clocks to the Dorado microprocessor, Midas can stillcontinue execution of the microprogram in ordinary situations. In passive mode (discussed later),these are the only items which Midas reads from the hardware.In active (i.e., normal) mode, Midas next executes a no-op, clears the hold and task simulator,does 30 no-op's, and then saves values of (current task) registers as follows: LINK, T, Q, TIOA,STKP, ALUFM 0, ALUFM 16, RBASE, MEMBASE, PROCSRN, and RM 0; these might getsmashed while reading registers that the user has put or will put on the display.Finally, Midas reads all registers displayed going top-to-bottom through the name-value menulines and left-to-right through the columns within each line. In passive mode, only those itemswhose values were obtained passively will be updated; others will be marked with a "~"indicating that Midas couldn't obtain the current value. In active mode, many microinstructionswill be executed to correctly address each item, route its value onto BMux, where Midas can readit, and then restore registers smashed while doing this.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОbqП,НxО^╛П$НxО[єТ┤ПGТ┬НxОYыТ∙ПAТ√НxОXТП8НxОUП?НxОQЧП$НxОNЖП/НЇОK└Т▀ПBТ▄НЇОI╨Т■Т∙ПPНЇОGОТхП:ТиП"НЇОF$ТПXНЇОB╡Т╗П(Т╘П2НЇО@ХТ╒П\НЇО?ТПWНЇО;╚Т┼ПLТ▀НЇО9АТкПJТлНЇО8Т╨ПJТ╩НЇО3┼rТП@НЇО0qТ┴Т┼ПFНЇО.MТ─ПGТ│НЇО,┐Т▌П:Т▐П&НЇО*╦ТПHНЇО'FТ╧П8Т╨НЇО%|Т▐П$Т░П@НЇО#╠Т∙ПQТ√НЇО!ФТ▒П)Т▓П9НЇО ТП=НЇО╙ТЄП2Т╣П-НЇОъТ⌠ПUТ■НЇОТ╡ПGТЁНЇОJТПQНЇОьТгП\НЇО Т╗П#Т╘П=НЇОCТСП,ТТП*НЇОxТ║П%Т╒П;НЇОўТ▄Т█ПYНЇО ЦТП8ЪXЇ °=П]oDorado Midas ManualEdward R. Fiala24 June 198334When Dorado is not running, Midas loads ALUFM 0 and 16 with the "B" and "NOT A" aluoperations, and TPC (i.e., CIA) is always in a smashed state. If one of these three items isdisplayed, the value in the Alto static is read; if written, the static is written. The value in thestatic is not written into the hardware until either a "Go", "SS", "OS", etc. action occurs or the"Dtach" or "RunProg" actions are executed. ALUFM 0 and 16 are effectively untestable fromMidas (sorry). TPC will get read for the new task and restored for the old task whenever Midashas to do a SelectTask, as discussed in the "Dorado Debugging Interface" document. Midas hasno trouble testing TPC, but if you examine a particular TPC register several times on the display,there is no guarantee that the values displayed will be ones independently read from the hardware.With the exception of these three items and the DMux, Midas always reads values from thehardware--other saved values are only used for restoration purposes. In other words, if "SHC" isdisplayed 10 times, it will be read 10 times from the hardware.MIR, MCR, Q, T, RBASE, MEMBASE, TLINK, STKP, RM 0, and PROCSRN are smashed andrestored while reading other stuff; these are read from the hardware independently each time theyappear on the display, but Midas might rewrite these registers from the saved values, so if one ofthese isn't working correctly, the exact nature of the failure may be obscured.Several memories and registers are "always updated" when they appear on the display, whichmeans that they will be reread at frequent intervals by the Midas main loop, and if the value haschanged the display will be updated. The UPTIME and TGLITCH registers and the MSTATmemory, which show items continuously recomputed by the baseboard microcomputer, are treatedthis way; and COMM-ERRS and MIR-PES (in the fake MADDR memory), which report errorsdetected by the Midas hardware interface, are always updated.Values in other registers and memories are only reexamined when you do some "dirty" action.When you write a value into some register on the display, for example, Midas tries to restore anyother registers and memories that were clobbered as a side effect; then it rereads the DMux andall registers on the display.There are a number of situations that may prevent continuation from a breakpoint or interrupt;Midas warns you about some of these when you try to continue but does not warn you aboutothers. Some of the ones that Midas does not warn you about are as follows:The machine stopped at t2 of an instruction that both started a new fetch and either read Md onto A or Bor used Md in a shift-and-mask operation; the value of Md for the new fetch will be erroneously used incompleting the Md read.The break occurred at t2 of an instruction doing a dispatch.The break occurred immediately after an IM or TPC read instruction--the value read will be garbage if youcontinue;You were using the hold simulator--Midas resets the hold simulator at breakpoints;Your microprogram was using the muffler/manifold system--Midas smashes the DMux address and resetssome of the manifold stuff at breakpoints;Input/output tasks were not serviced properly due to the delay at the breakpoint, so these are not continuedcorrectly;Your microprogram is relying upon the exact timing of the memory system to write the cache flags for areference--the moment will have passed when continuation occurs (There are probably other situations whenthe memory system is operated in unusual ways that will prevent continuation.).НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОbqТґТўП8НЇО`SТгП>ТхНЇО^┴ТіТїПJНЇО\ЎТ÷Т═ПUНЇОZСТ╙П1Т╚П)НЇОY)Т∙ПKТ√НЇОW^Т≤П+Т≥П2НЇОU■Т▌ПDТ▐НЇОSиТ│ПTТ┌ НЇОPWТиП'ТйП1НЇОN▄Т▒ПUТ▓НЇОLбТП?НЇОIPТ┴П/Т┼НЇОG┘Т┤ Т┬ПSНЇОE╩Т░ПMТ▒НЇОCПТПOНЇО@~ТбП*ТцП0НЇО>ЁТ░ПPТ▒НЇО<ИТЄТ╣П9НЇО;Т┬П\НЇО9TТ²П?Т·НЇО7┴ТП=НЇО4Т╟Т╠ПLНЇО2LТ▌П=Т▐П$НЇО0┌Т≥Т ПPНЇО.ЇТНЇО+EТ╔П^НЇО){Т╟П#Т╠П5НЇО'╟ТПLНyО$НsТ┬О$aО$НПMТ┴НyО#GТ■П3Т∙П4НyО!ФТНyОHО╩ОHП$НyО╙Т┴П1Т┼П8НyОIНyО╚ТПRНyОТ╛ПWТґ НyО╛ТП*НyО Т└ПlНyОґ НyОТ⌡П9Т°П-НyОўТ▄ПSТ█НyОMТПOЪЇ*=П\АHDorado Midas ManualEdward R. Fiala24 June 198335Some situations that Midas does warn you about are as follows:You have displayed some address in BR, BRX, ROW, CACHEA, CACHED, MAP, or VM; Midas will usetask 17 and pipe entry 1 to access these, and if the break occurred in task 17, Midas will warn you thatcontinuation is impossible because Pipe entry 1 and (for CACHED and VM) task 17 MD are smashed.Some address in IFUM is displayed; Midas has to reset the IFU to read IFUM and will warn you thatcontinuation from a breakpoint is impossible.Some address in IMBD is displayed; Midas has to reset some of the control section to access IMBD.You broke on or single-stepped across an instruction that did both a Fetch_ and either a T_Md orRM/Stk_Md; if you continue, data from the new fetch rather than data from the preceding fetch will beused to complete the T_Md or RM/Stk_Md operation.A breakpoint on or single-step through an instruction that does NewPC_ is illegal (??).27. Hardware Failure ReportingMidas checks for several kinds of hardware errors and reports them in MIR-PES and COMM-ERRS, which are addresses in the MADDR memory; these are shown in the upper right-handname-value menus by the normal Midas display. MIR-PES is shown on the display as two 16-bitfields; the first field counts parity errors detected in MIR[0:20] and the second, parity errors inMIR[21:41]. MIR-PE's is zeroed when you start Midas, "Dtach", or "Reset", or when you start a"Ld". Whenever Midas loads a microinstruction into MIR, it checks for good parity in MIRbefore executing it and counts MIR-PES if the parity is no good; however, even if the parity isbad, Midas goes ahead and executes the microinstruction. If any MIR parity errors occur during aload, the message "**MIR-PE's occurred**" is printed on the comment lines after the load;however, except for that message, Midas does not print any special messages after these errors--theuser will have to notice when MIR-PES changes at other times.COMM-ERRS is also shown as two 16-bit fields. The first field counts glitches in the "Stopped"line, which Midas samples repeatedly during "Go" (The serial 1 Dorado seemed to report"Stopped" when the microprocessor did not have any reason for stopping, so some glitch detectionsoftware was added to Midas to detect this situation.); the second field counts microcomputertimeouts. Midas initializes these error counters to 0 after initially connecting to a Dorado, during"Reset", and during "Dtach". Midas allows about 2 msec for the baseboard microcomputer toservice interrupt requests; if this timeout is exceeded, the right-hand field of COMM-ERRS iscounted.Midas also shows a number of hardware conditions collected by the baseboard microcomputer;these include power supply information summarized in PROBLEMS, OUTOFSPEC,BADSUPPLYSPEC, and TGLITCH as discussed later.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОbqП>НyО_\sТ▄П"Т█П9НyО]ШТ°Т²ПPНyО\⌡ТўТ╞ПEНyОYЭТёП@ТєП!НyОX°ТП-НyОUЩТ╪П"ТҐП?НyОS_ТцП%ТдП;НyОQЧТ≥ПDТ П!НyОP·ТП1НyОMЪПWНЇОI√rНЇОF$qТ╟ПWНЇОDZТ╠ПVНЇОB▐Т▄ПBТ█НЇО@еТ╙Т╚ПRНЇО>ЗТ▄ПMТ█НЇО=/ТҐПFТЎНЇО;eТ╒П:ТёП%НЇО9 Т─П&Т│П;НЇО7пТжПSТвНЇО6Т└ПcНЇО4:ТП=НЇО0хТ▐ПUТ░ НЇО.ЧТЛТМПEНЇО-3Т─Т│ПNНЇО+iТбТцПBНЇО)·Т▐П"Т░ПCНЇО'сТўП2Т╞П(НЇО& Т╨ПPТ╩НЇО$>НЇО лТ╡ТЁПHНЇОТ≈ПIНЇО7ТП.Ъ.ЇП<ПKDorado Midas ManualEdward R. Fiala24 June 19833628. Hardware Checkout FacilitiesMidas checkout facilities fall into the following categories:ObservationObserve registers and signals invisible to the microprogrammer (DMuxstuff, print routines, passive mode).PokingTrying out elementary actions to observe what happens (T1, T2, T3,Poke stuff).TestingExercise various hardware sections, verifying that they work correctly orreporting the nature of failures (Test, TestAll, SimGo, SimTest,LDRtest).Scope loopsRepeatedly do something to observe failures with the scope (RepGo,RepSS, RepT2, Fields, HWChk, test actions).DiagnosisRelate failures to particular hardware components (SimGo, SimTest).The LDRtest action must be preceded by the "Debug" command file (in the "RunProg"submenu), which loads the LDR memory addresses needed for LDRtest. The "Debug" commandfile should not be needed in any other cases.With diagnostic microprograms, you can use the PROC, CONTROL, MMC, MMD, MMX,IFUD, DSKETH, and DSP command files (in the submenu put up by RdCmds) to display DMuxaddresses for various hardware sections.29. Parity-Error ScanningThe "PEscan" action scans memories and reports parity errors. It presents a submenu consistingof "Scan-and-report" and "Scan-for-totals" actions followed by the names of the memories thatcan be scanned for errors. The user interacts with the submenu, selecting and deselectingmemories to be scanned; then he bugs either "Scan-and-report" or "Scan-for-totals".On Dorado, the memories that can be parity scanned are IMX, RM, STK, IFUM, CACHEA, CACHED,and MAP."Scan-and-report" will sequence through all the words in the selected memories, reporting on thecomment lines the first 20 addresses that have parity errors and the total number of parity errorsfor each memory. "Scan-for-totals" reports only the parity error count for each memory.In general, very long memories such as main storage are not included in the "PEscan" submenubecause Midas cannot scan them fast enough to report results in a reasonable time.30. Testing Directly From Midas"Test" and "TestAll" allow the target machine to be tested directly from Midas. Althoughdiagnostic firmware can test faster and more thoroughly than is practical from Midas, Midas directtesting permits the hardware to be checked out well enough to get basic diagnostics loaded andstarted. On Maxc1, which had no direct testing in Midas, many hardware failures of the "nothingworks" variety were harder to fix than on Maxc2 and Dorado, where Midas test software isНЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrП!НЇО]▓qП=НxОZ НнТіП'ТїНнОXUТП%НxОUMНнТйТкП"НнОS┌ТНxОPzНнТ▒П#Т▓П&НнОN╟Т9Т:П,НнОLЕНxОIщТ─ Нн ТфП*Тг НнОHТП+НxОE НнТжП9Тв НЇОA≤ТЗП:ТШНЇО?нТ┤ПCТ┬НЇО>ТП-НЇО:▒ТФП*ТГП"НЇО8фТ┌Т┐П@НЇО6ЭТП(НЇО2prНЇО.ЧqТ Т⌡ПLНЇО-3Т╠Т╡ПEНЇО+iТГПNТХНЇО)·ТПSНyО&эsТ╒П;ТёНyО%|ТНЇО"-qТ┬П(Т┴П9НЇО bТ∙Т√ПQНЇО≤ТЖП;ТВНЇО&Т·П7Т÷П%НЇО[ТПRНЇОоrНЇО]qТшПCТэНЇО▓Т┘П,Т├П6НЇО хТїПGТ╗НЇОЩТ┬ПPТ┴НЇО 3ТпПGТяЪ ПЇ Л<П^Dorado Midas ManualEdward R. Fiala24 June 198337available. However, on Dolphin and M68 implementations of Midas, the test features in Midasare of doubtful usefulness because the hardware is accessed through communication with a small"kernel" microprogram that only works when most of the hardware is functional.Data patterns for test actions are determined from the first subsidiary menu, as follows:Table 6: Test Data Pattern ActionsZEROESAll-zeroes dataONESAll-ones dataSHOULD-BEConstant test pattern equal to value in SHOULD-BECYC1Vector of the same size as the register containing zeroes with a single one-bit cycled leftone position each iterationCYC0Cycled zero in vector of onesRANDOMRandom numbersSEQUENTIAL0, 1, ..., sequential numbersALTZOAlternating all-ones and all-zeroes patternsALT-SHOULD-BEAlternating contents of SHOULD-BE with its ones-complementThe CYC0, CYC1, and SEQUENTIAL patterns vary according to the size and arrangement of thedata vector for the item being tested. CYC0, for example, starts off with leading 1's and a 0 inthe right-most bit of the data vector. The 0 is shifted left (bringing in 1's to its right) eachiteration; when the 0 is shifted out of the left-most bit in the data vector, the vector is reinitializedto leading 1's and a 0 in the right-most bit. The CYC1 pattern is like CYC0 with 1's and 0'sinterchanged. The SEQUENTIAL pattern is initialized to 0 and is incremented by 1 in the right-most bit of the data vector each iteration.This treatment of CYC0, CYC1, and SEQUENTIAL patterns is conceptually correct for items thatare described inside Midas by dense, left-justified data vectors whose bits are displayed left-to-right on the screen. Most, but not all, items are handled this way.On Dorado, the exceptions are as follows: IMX, IMBD, and MIR have the parity-bad bits displayed left-most but stored internally right-most in the data vectors. The parity bits do not participate in determiningthe data pattern for CYC0, CYC1, and SEQUENTIAL patterns; i.e., the two parity-bad bits will always betested with 1's (i.e., bad parity) for CYC0 or always with 0's (i.e., good parity) for CYC1 andSEQUENTIAL patterns.ALUFM, CACHEA, MAP, BR, and MCR have holes between bit 0 and the right-most bit of the datavector. The CYC0, CYC1, and SEQUENTIAL patterns for these are generated as though these holes didn'texist. I.e., ALUFM has an 8-bit data vector in which bits 1:2 are unused; CACHEA has flags in bits 0:3and VA[4:n] in subsequent bits, but the leading bits of VA are not actually stored in the address section formost cache configurations, so the unstored bits are a hole; MAP has RP in bits 16:31 of the data vector andvarious flags in bits 12:15, so bits 0:11 are a hole; BR uses 4:31 of the data vector, so bits 0:3 are a hole;and MCR uses 0:15 with several unused bits in its interior. Testing is controlled/described by 12 addresses on the display as follows:НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОbqТє Т╔ПQНЇО`SТ Т⌡ПOНЇО^┴ТПNНЇО[ПYНzОW╔tТ▓П#НxОTysН░ТНxОSН░НxОQ╦Н░П1НxОPWН░Т│П[Н░ОNЖТНxОM∙Н░НxОL5Н░ НxОJт Н░НxОIsН░П,НxОHН░П:НЇОDдqТ┘ПBТ├НЇОBЫТ·П\Т÷НЇОA.ТцПQТдНЇО?dТ└П'Т┘ПBНЇО=≥ТґПBТўНЇО;оТ▄ПXТ█НЇО:ТП+НЇО6▓Т└П,Т┘П0НЇО4гТ╣ТІПUНЇО2ЩТПDНyО/яsТ■ Т∙П\НyО.qТ▒П:Т▓П3НyО-Т▒П/Т▓П7НyО+╞ТТПRТУНyО*NТНyО'FТґП2ТўП)НyО%ЕТ└Т┘ПYНyО$┘Т⌠ПBТ■П%НyО#$Т┘П>Т├П/НyО!цТ─ Т│ПaНyО bТ█ПbТ▌НyОТП<НЇОЁqПJЪnЇl<ПL÷Dorado Midas ManualEdward R. Fiala24 June 198338Table 7: Test Items in the Name-Value DisplaySHOULD-BEOn a failure, the correct data; after control-C or Abort, the next pattern.DATA-WASOn a failure, what the data was; after control-C or Abort, the data read last time.BITS-CHECKEDMask of bits checked (see below).BITS-PICKEDUnion of bits that should have been 0 but were erroneously 1 during testing. Thisaccumulates failure information when you continue a Test using or .BITS-DROPPEDUnion of bits that should have been 1 but were erroneously 0.LOOP-COUNT32-bit iteration count at which failure occurred or after which the test was aborted.NFAILURES32-bit count of test failures.Memory tests onlyLOW-ADDRHIGH-ADDRCURRENT-ADDRADDR-INC32-bit addresses: If ADDR-INC (normally 1) is positive, the test starts at LOW-ADDRand advances through the memory in steps of ADDR-INC until CURRENT-ADDR isgreater than HIGH-ADDR. If ADDR-INC is negative, the test starts at HIGH-ADDRand goes by steps of ADDR-INC until CURRENT-ADDR is below LOW-ADDR.CURRENT-ADDR contains the last address tested.ADDR-INTERSIntersection of address bits where failures were detected.ADDR-UNIONUnion of address bits where failures were detected.SHOULD-BE, DATA-WAS, BITS-CHECKED, BITS-PICKED, and BITS-DROPPED areaddresses in the MDATA memory; LOOP-COUNT, NFAILURES, LOW-ADDR, etc. areaddresses in the MADDR memory. These two memories (which are tables in Alto storage) existon all versions of Midas that implement the test actions.The handling of the MDATA memory is complicated by the fact that items in this memory haveto be shown in the same format as the memory or register being tested. This is accomplished asfollows: When the selected test item is different from the last, the width and print-format ofMDATA are set to be identical to the new item; in this case BITS-CHECKED is initialized to testall bits in the new item. Then when the test is aborted or halts due to a failure, the display ofBITS-CHECKED, etc. is identical to that of the item tested. The user may then modify BITS-CHECKED and continue, restart, or free-run the test, as discussed below; in this case the itemtested is identical to the last item tested, so BITS-CHECKED is not reset.The handling of MADDR is also tricky. ADDR-INC is allowed to be any value except 0; if it is0, Midas will reset it to 1 before testing. When HIGH-ADDR is initially greater than the largestlegal address in the memory, it is reset to memlength-1 prior to testing. Then if LOW-ADDR isgreater than HIGH-ADDR, it is reset to 0 before testing. When the selected memory differs fromthe last item tested, and when the length of the memory is less-than-or-equal to 100008 wordslong, Midas will reset LOW-ADDR to 0 and HIGH-ADDR to memlength-1 prior to testing. Thisis done because a common operational error is failure to reset the address range when switchingfrom one memory test to another. However, Midas does not reset the address range for very longmemories because they are normally tested with small address ranges that cannot be predicted inadvance--full-length testing of long memories from the Alto is so slow as to be impractical."Test", after showing the data-pattern menu, shows a menu of register and memory names andother test names, and executes a test of the one you select until the test fails or you halt the testfrom the keyboard.The testable registers and memories appear in the second sub-menu for the "Test" action. ThisЪНЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНкОbtТ▓П.НxО^РsН░ТПKНxО]▓Н░ТЇП:Т╦НxО\1Н░ТП!НxОZп Н░Т╙П<Т╚Н░ОYoТ⌡П1Т°НxОXН░ТП=НxОU Н░Т╣ТІП6НxОSіН░ТНxОP·uНxОM∙sНxОL5НxОJтНxОIsН░Т░П7Т▒Н░ОHТ∙Т√П6Н░ОF╡Т▀Т▄П6Н░ОEQТй ТкП8Н░ОCПТП.НxОB▐ Н░П:НxОA. Н░П3НЇО=ЮqТ_Т`П0НЇО<ТТП*НЇО:KТ≈Т≤П=НЇО8─ТП9НЇО5Т⌠Т■ПAНЇО3CТ∙ПLТ√НЇО1yТ╧П%Т╨П:НЇО/ўТ┐Т└ПBНЇО-ДТ÷Т═ПOНЇО,ТіПEТїНЇО*NТ╚ПHТ╛НЇО(└ТПJНЇО%Т█П:Т▌П#НЇО#GТ▓ПYТ⌠НЇО!}Т■ПRТ∙НЇО╡Т└П/Т┘П0НЇОГТІТЇП=ОZsОГqНЇОТ└П5Т┘П$НЇОRТ·П8Т÷П'НЇО┤Т┤ПKТ┬НЇОҐТ≤П<Т≥П#НЇОРТзП;ТшП!НЇО─Т╚ПEТ╛НЇОІТ√П%Т≈П@НЇО КТНЇО yТ╒ПXТёЪ ═Ї 2<П]ыkDorado Midas ManualEdward R. Fiala24 June 198339menu also includes several other machine-dependent test programs.On Dorado, the additional tests are as follows:Table 8: Other Test ActionsShmvTests the output of the shift-control ROM's on the ProcH and ProcL boards againstcorrect values.WFTests loading ShC via WF_RFTests loading ShC via RF_ProcVATests BR+Mar via DummyRef_ will continue a register or memory test that has halted; it restarts an OtherTest that hashalted. will continue a register or memory test that has halted but will free-run the test rather thanhalting on the next failure. While free-running, LOOP-COUNT and NFAILURES are reportedcontinuously on the display, and BITS-DROPPED, BITS-PICKED, ADDR-INTERS, and ADDR-UNION accumulate failure information. When you stop the test by bugging "Abort" or typingcontrol-C, the accumulated failure information is displayed in these registers."TestAll" automatically loads BITS-CHECKED with a full-sized comparison mask prior to testingeach item; memories are tested with LOW-ADDR = 0, HIGH-ADDR = memory length-1, andADDR-INC = 1. It tests each register 200 times and makes 4 passes through each memory andeach OtherTest. It is a good idea to run "TestAll" whenever the hardware is in a suspicious state.31. LDRtestOn Dorado and Maxc2, the "LDRtest" action should only be used when the "DEBUG" commandfile has been executed. This requires a sophisticated understanding of the hardware and of theinnards of Midas and is not recommended for novices.Dorado Midas stores many microinstructions in a fake memory called LDR (see LOADER.MC). These areused by various actions to operate the hardware. "LDRtest" allows these to be executed in non-standardsequences to beat on particular hardware problems."LDRtest" accepts a list of LDR addresses separated by commas as input text. If only one LDR address istyped, the CPREG register is loaded once with the selected data pattern, then the LDR instruction isrepeatedly executed with UseCPReg true for a scope loop.When two, three, etc., up to five LDR addresses are typed, a test loop occurs whereby CPREG is loadedwith the next data pattern, the first instruction is executed with UseCPReg true, then the rest of theinstructions are executed, and then the BMux is read back and compared against the original data undercontrol of BITS-CHECKED. The loop stops when (data-read-back xor data-sent-out) & BITS-CHECKED isnon-zero.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОbqПAНЇО^╛П/Н ЄО[:tТ▓Н:ОXsН░Т╚П+Т╛П&Н░ОVўТН:ОUMН░Н:ОSЛН░Н:ОR▀Н░НЇОO=qТ║П-Т╒П3НЇОMrНЇОJТ┘ПEТ├НЇОH6Т║Т╒П;НЇОFkТ┬Т┴П6НЇОD═ТєП4Т╔П&НЇОBжТПOНЇО?dТ▌П/Т▐П.НЇО=≥Т≈Т≤П?НЇО;оТ⌠Т■ПMНЇО:Т┤Т┬ПMНЇО5xrТНЇО2qТ┌ПBТ┐НЇО0;Т╗Т╘ПGНЇО.qТП4НyО+EsТ▄П/Т█П3НyО)ДТ÷П0Т═П7НyО(└ТП2НyО%ЕТ├Т┤ПPНyО$┘ТЎПQТ©НyО#$ТП8НyО ├Т ПeНyО%ТбПfНyОдТєПNТ╔НyОcТ┘П"Т├П@НyОЪ ▌Їъ<ПM,ЭDorado Midas ManualEdward R. Fiala24 June 19834032. Scope Loop Actions: Fields, RepGo, RepSS, RepT2The "Fields" action exercises signal decoding for particular fields of the microinstruction for scopeloops. A microinstruction is fabricated from a no-op microinstruction in which the field selectedfrom the first sub-menu is replaced by various values. The second subsidiary menu allows thevalue in the selected field to be incremented, decremented, and shifted."RepGo" starts the microprocessor at the address typed on the command line, waits for it to haltat a breakpoint or parity error, then restarts it at the original address."RepSS" repeatedly single-steps the microprocessor at the address typed on the command line.On Dorado, the task for the original Go or SS is taken from the TASK register; subsequent restarts do notreselect the task. The control section's Ready register is reset before the first Go or SS, but is not reseteach time through the loop.On Dorado, "RepT2" endlessly executes the instruction in MIR and reloads that value into MIR.Unlike "RepSS", "RepT2" doesn't issue extraneous clocks while looping, so it is ordinarily moreconvenient for scoping.33. HWChkThe "HWChk" action puts up a submenu that contains several test and scope loop actions. Oncestarted, one of these actions runs until you abort it; the iteration count will be in LOOP-COUNTwhen the test is aborted. The HWChk submenu currently contains the following actions:"Read-DMux-Signal" requires a non-zero value in DWATCH; a scope loop is generated in whichthe DMux address selected by DWATCH is strobed out to the hardware and then the value read.A count of the number of times the value is 0 and the number of times it is 1 are showed on thecomment lines. Microcomputer DMux reading is disabled during this action."Read-All-DMux" repeats the following sequence indefinitely: (1) Execute an almost-randommicroinstruction as in SimTest; (2) Read all 40008 DMux signals three times, accumulating inDWrong the union of signals which had inconsistent readout. A count of the number ofinconsistent signals is displayed. Microcomputer DMux reading is disabled during this action.Also, signals which legitimately may change value (primarily Ethernet and Disk signals) are notreported as inconsistencies. This action can be used to test the reliability of the DMux and strobedata paths, which are known to become unreliable for sufficiently long Midas cables. It can alsobe used as a scope loop for observing DMux data paths. If this action reports no inconsistencies,then one can be fairly confident that the simulator will report Dorado hardware failures ratherthan failures in the Midas communication data paths."Connect-Disconnect" first evaluates the input text line, which must contain a valid Dorado serialnumber (0 to 3778). A scope loop is generated in which Midas alternately connects to the selectedserial number and to that serial number xor 3778 (= disconnects). A count of successful andunsuccessful connects is displayed on the comment lines."Alto/MC-control" generates a scope loop in which the Alto and the microcomputer alternatelyare given control of the muffler/manifold system.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrП5НЇО^eqТ├П1Т┤П4НЇО\⌡Т≥ПIТ НЇОZпТўП&Т╞П7НЇОYТПHНЇОU■Т▓П=Т⌠П#НЇОSиТПJНЇОPWТІП9ТЇП#НyОM,sТ┬Т┴ПRНyОKкТ·ПLТ÷П!НyОJjТНЇОGqТ▓ПSТ⌠ НЇОEQТ²ПFТ·НЇОC├ТНЇО>Зr НЇО;┬qТ▄ Т█ПRНЇО9ҐТ▌Т▐ПCНЇО7СТРПVНЇО4│Т▄ПGТ█НЇО2ІТ▀П5Т▄П&НЇО0ЛТ▀П1Т▄П.НЇО/!ТПJНЇО+╞ТЦПHТДНЇО)ДТаТбО)WsО)ДqП*НЇО(ТГТХП:НЇО&OТ©П#ТюП;НЇО$┘Т╛П1ТґП.НЇО"╨Т┤Т┬ПHНЇО ОТ∙ Т√ПVНЇО%Т▐ПbНЇОZТ╡П?ТЁНЇО░ТП4НЇОТ▐П.Т░П4НЇОSТ┐ОфsОSqТ└П>НЇО┬Т╣ТІОШsО┬qП,НЇОЎТП8НЇОLТ╘П+Т╙П1НЇО │ТП1|Ї :=ПZя4Dorado Midas ManualEdward R. Fiala24 June 19834134. DMux Consistency CheckerThe DMux consistency checker, or simulator, used with the "SimGo" and "SimTest" actionsexamines all of the DMux signals (or mufflers), checking for inconsistencies. The simulationverifies consistency of signals from the previous readout (call this "t0") to the current readout (callthis "t2").In all cases, only passively-accessible DMux signals and BMUX and ESTAT are involved in thesimulation--registers that can be read only by issuing clocks to the hardware are not checked.The simulation subroutine behaves differently based upon the time at which the DMux was read(t even or t odd) and upon whether or not the DMux readout at tn-2 is available. Currently, thesimulator is only called by "SimGo" and "SimTest", and for these the simulation subroutine isalways called with the t0 and t2 DMux tables. The operation of the simulator is reported in and controlled by five tables, each containing one bitfor every DMux signal:OldDMuxTabDMux readout for t0.DMuxTabDMux readout for t2.DCheckmask of bits whose simulated values are to be checked for errors.DWrongmask of signals whose DMuxTab values do not agree with thesimulation and whose mask in DCheck is 1.Setup for the simulator begins during initialization, when the "Config" action is executed. At thattime, DCheck is initialized to reasonable values for the hardware configuration. In other words, ifa particular section of the machine is not in the chasis, then the signals in that section cannot bechecked, so they are zeroed in DCheck. In addition, other signals whose simulated values dependupon signals from the missing section cannot be checked. "Config" sets up DCheck so that onlysignals which can be checked will be examined for error. Finally, "Config" also zeroes theDCheck bits for signals known to be simulated incorrectly.A simulation step consists of the following parts:1) Copy DMuxTab into OldDMuxTab.2) Single-step the Dorado; then read the DMux into DMuxTab.3) Copy DMuxTab into DWrong.4) Execute the simulation program which will predict many signals as functions of valuesin OldDMuxTab and DMuxTab. The predicted values overwrite values in DWrong.Unsimulated signals are not modified in DWrong.5) DWrong _ (DWrong xor DMuxTab) & DCheck.6) Stop and report failures if any bits in DWrong .ne. 0."SimTest" is executed with IOReset, RunRefresh, and EnRefreshPeriod false. It loads MIR witha randomly chosen microinstruction (except that some illegal microinstructions are weeded out--presently, the Output_, UseDMD, MidasStrobe_, and IFUTest_ functions are illegal; also, theBlock bit in the next microinstruction is chosen to equal whatever was coming from IMX justЪНЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrНЇО^eqТрТсП:НЇО\⌡ТйПMТкНЇОZпТ┤Т┬П(ОZCsОZпqНЇОYТОXxsОYqНЇОUЇТ╙pqТ╚НЇОSЛТбТцПDНЇОPzТ≈П8Т≤П$НЇОN╟Т▓П?ОN#sОN╟qТ⌠НЇОLбТўП6Т╞П'НЇОJВТОJjsОJВqОJjsОJВqНЇОG╗Т┌П*Т┐П:НЇОEчТНxОBl Н░ОAъsОBlqНxО@7Н░О?╙sО@7qНxО>Н░ТЙП-ТКНxО;╚Н░Т#Т$Н░О9АТП)НЇО6oТ├ПQТ┤НЇО4єТ├Т┤ПXНЇО2зТ√Т≈ПXНЇО1Т┴ПRТ┼ НЇО/DТ⌠Т■ПIНЇО-zТрП-ТсП.НЇО+╞ТП:НЇО(=П2НyО%÷НyО#П;НyО bНyОдТ▀ПAТ▄НyОЫТхТиП-НyО/ТП/НyО▒П*НyОРП9НЇО─Т∙П]НЇОІТ╛П_НЇО КТ╡ТЁПDНЇО ТЇПBТ╦ ╗Їы<П\25Dorado Midas ManualEdward R. Fiala24 June 198342before t2 of the last microinstruction to avoid screwing up the control section); then it reads theDMux and steps the microinstruction through t2. This is repeated, and after each repetition theprevious and current DMux readout are checked for consistency."SimGo" is similar, but a microprogram stored in IM is executed one step at-a-time rather thanrandom microinstructions; there are no illegal microinstructions for SimGo. When a diagnostic orother microprogram is known to fail, it can be run full speed up to a breakpoint a little before thesequence that fails; then the program can be continued with "SimGo" which might pinpoint thehardware failure. However, since RunRefresh and EnRefreshPeriod are false during "SimGo",any microprogram that uses Storage or the Map might not run correctly. "SimGo" continues untileither a simulation error is detected or ESTAT contains a halt condition; the halt conditions for"SimGo" are identical to those for "Go" (The halt conditions can be modified by the user withthe "Reset" action.).For the most part, mufflered signals in the different hardware sections relate to control pathsrather than to data paths, so the consistency checker will be less effective in finding failures indata paths. However, Midas register and memory tests and diagnostic firmware can usuallypinpoint data failures, so this limitation is not too serious.The ContA/B, ProcH/L, MemC/D/X, and IFU sections are presently simulated.How to Interpret Simulator FailuresWhen the simulator detects one or more failures, it reports a message like "2 DMux errors". Youcan find out which signals are believed inconsistent by executing the "DMux" action in thecommand menu with the middle button. When the middle button is released, the names of thefirst 11 signals that were incorrect are printed on the comment lines; each name is followed by asuffix such as "/A" indicating the section in which the error was detected; possible suffices are:/B BaseboardNo signals are currently simulated./A ContA/B ContB/L ProcL/H ProcH/I IFU/C MemC/D MemD/X MemX/K Disk controllerNo signals are currently simulated./E Ethernet controllerNo signals are currently simulated./V Display controllerNo signals are currently simulated.The next step is to display the DMux words associated with one of the hardware sections thatfailed; this is done by executing the "RdCmds" action and selecting the command file thatdisplays that section (PROC, CONTROL, MMC, MMD, MMX, IFUD, DSKETH, or DSP).Then find the source for a signal that failed in the hardware drawings; you will probably be ableto deduce its dependency upon other DMux signals and can then determine where the failureoccurred. You can view the signals relevant to the simulation by viewing the OldDMuxTab orDMuxTab signals on the display, as was discussed in the "Memories and Registers AssociatedЪНЇОgpТ─Н"sqН5 Т НG?ОfЯpНЇОbqТ÷Оa▒sОbqТ═П:НЇО`SП-О_фsО`SqП2НЇО^┴ТП>НЇО[Т═П-Т║П1НЇОYLТ┬ПLТ┴НЇОW│Т┐П=Т└П'НЇОUЇТ²ПOТ·НЇОSЛТЇПZНЇОR"Т│ПOТ┌НЇОPWТ╒П]ТёНЇОN▄Т═Т║ПHНЇОLбТНЇОIPТцП$ТдП;НЇОG┘Тґ ТўПXНЇОE╩ТыП/ТзП*НЇОCПТП>НЇО@~ПIНЇО<8pП#НЇО8фqТ┤ПMТ┬НЇО6ЭТтТуПNНЇО51Т²П.Т·П,НЇО3gТ∙П7Т√П*НЇО1°Т╒ТёПOНyО.ЧТ─Н"sТП!НyО-3НyО+iНyО)·НyО'сНyО& НyО$>НyО"sНyО ╘НyОчТ─Н"sТП!НyОТ─Н"sТП!НyОIТ─Н"sТП!НЇОвТ╡ТЁПAНЇОТшПGТэНЇОBТщПEТчНЇОпТ▓ПKТ⌠НЇОТ╧П8Т╨П!НЇО ;Т╘П3Т╙П(НЇОpТЎП7Т©П#ЪXЇ)<П]=Dorado Midas ManualEdward R. Fiala24 June 198343With the DMux" section.Normally, DMux addresses and registers derived directly from DMux readout (i.e., MIR, IMOUT,MCR, IMBD, DHIST, VH) show values taken from DMuxTab. However, the user may executethe "DMux" action with various button combinations to view the other three tables; the nameprinted for this action in the command menu will then show the selected memory. The buttoncombinations for this are as follows:DWrongmiddle buttonDCheckleft and right buttonsOldDMuxright buttonDMuxleft buttonOnly when DCheck is displayed is it legal to write words in the DMux memory; the other formsare read-only. DCheck can be modified to remove signals from the checking process (or to addthem back).35. Poking: T1, T2, and T3The "T1", "T2", and "T3" actions allow the instruction currently in MIR to be executed exactly asthough it were spliced into the execution flow of the program. The DMux is read after t1, t2, ort3 of the instruction, then, for "t1" and "t3", the machine is clocked once more (to t2 or t4). MIRis restored after execution.36. Passive ModePassive mode suppresses automatic readout of registers that require clocks to be issued by Midas.This allows scope observation without interference from automatic parts of Midas.Midas implements three "states" called active, prepassive, and passive. The command menualways prints the current state; bugging "active" will change the state to "prepassive"; bugging"prepassive" will change to "passive"; and bugging "passive" will change to "active"--in otherwords, these three states are sequenced through in a "ring."In active mode, Midas will jam instructions into MIR and execute them to obtain the contents ofvarious Dorado register or memory words or to restore registers incidentally smashed while doingsomething else; as discussed earlier, there are some situations when continuation is impossibleafter doing this, and some hardware problems are difficult to observe when Midas is interfering tothis extent.PrePassive mode is identical to active mode, but if you start the machine with "Go," "SS,","SimGo", "SimTest", or whatever, then Midas will automatically flip into passive mode the nexttime the machine halts.When you enter passive mode from the keyboard action, the state of the hardware is restored asthough it were about to continue from a step or breakpoint and TASK is restored to its value atthe last step or breakpoint. After this, no further clocks are given to the hardware except thoseexplicitly initiated by the user.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОbqНЇО^╛Т┘П7Т├П%НЇО\АТ П5Т⌡НЇО[ТЁТЄПJНЇОYLТ╔ПTТіНЇОW│ТП%НyОTН"sНyОREН"sНyОPzН"sНyОN╟Н"s НЇОK>Т▓Т⌠П?НЇОIsТ°Т²ПCНЇОG╗Т НЇОCrНЇО?╙qТ│ПJТ┌НЇО=ЮТ⌠ПKТ■О=SsО=ЮqО=SsО=ЮqНЇО<О;┬sО<qТ█П'Т▌П-О;┬sО<qО;┬sО<qНЇО:KТНЇО5ЎrНЇО2LqТ■П6Т∙П+НЇО0┌ТПQНЇО-ТуП&ТжП3НЇО+EТ╣ТІПSНЇО){ТбПAТцНЇО'╟ТП<НЇО$>Т▒Т▓ПEНЇО"sТ⌠ПTТ■НЇО ╘ТдПQТе НЇОчТ├ Т┤ПWНЇОТНЇО╒ТнТоП?НЇОвТ·ПPТ÷ НЇОТНЇО⌡Т Т⌡П>НЇОпТ√Т≈ПKНЇОТ═П,Т║П6НЇО ;ТП!Ъ ЖЇТ=П[*Dorado Midas ManualEdward R. Fiala24 June 198344After becoming passive, Midas doesn't update registers on the display unless their values can beread without issuing clocks. Since only DMux locations (includes MIR, IMOUT, IMBD, MCR,TESTSYN, PROCSRN, TASK) can be read without clocks, only their values change whilepassive.Further, if you display a new non-passive register on the display, its value will not be read fromthe hardware and garbage will be displayed as the value.Items on the display for which the displayed value is doubtful will be flagged with a "~" asdiscussed earlier.Similarly, only registers whose values can be modified without issuing clocks may be written whilepassive--these are MIR, CPREG, STROBE, and D1OUT (plus the artificial registers andmemories). Midas rejects attempts to modify other registers on the display. Of the writableregisters, only MIR, CPREG, and IMBD can be read, and only MIR can be read passively.Consequently, if you write into CPREG, STROBE, or D1OUT by clicking the mouse over itsvalue, it will be written but the display will show the contents of a static, not something read fromthe hardware--since other parts of Midas don't update the statics, the value displayed only meanssomething immediately after the write.The command menu is drastically altered while passive; only actions which can be executed whilepassive are shown."Update" reads the machine state actively and then becomes passive again.While passive, "SS" and "Go" at new addresses work as usual, so extra clocks are issued to dothese. However, "SS" and "Go" to continue a program do not issue any extraneous clocks--all ofthe setup to continue took place at the time passive mode was entered; or after a step orbreakpoint, no clocks are issued to readout the machine state, so it is possible to continue simplyby modifying Stop, SetRun, and SetSS.To do the most primitive kind of debugging while passive, it is expected that users will work asfollows: First, the POKE command file will be executed to become prepassive and displaySTROBE, D1OUT, and CPREG, not ordinarily on the display. The user will then either do a Goor SS, becoming passive at the break, or will bug prepassive to become passive immediately.Next, MIR and CPREG will be written by modifying the displayed value. Then the Clock andControl registers and Strobe can be manipulated by storing values into STROBE and D1OUT.STROBE is displayed as two fields and D1OUT as three fields; when storing into these, you mustpartition the input into fields as well. For STROBE the two fields are the address field (3 bits)and data field (9 bits). Storing into STROBE will give a three-step strobing sequence using thevalue of address and data you have selected. For D1OUT the three fields are the Strobe bit,address, and data. (Note: The DMux will be read after writing MIR, but it is not read afterwriting CPREG, STROBE, or D1OUT, used for lowest level debugging of the Midascommunication interface.).ЪНЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОbqТ║Т╒ПIНЇО`SТёПFТєНЇО^┴ТИТЙП;НЇО\ЎНЇОYLТ ПbНЇОW│ТП8НЇОTТЎТ©ПPНЇОREТНЇОNсТ┤ПTТ┬ НЇОMТТПAНЇОK>ТфПPТгНЇОIsТмП:ТнНЇОG╗Т╨Т╩ПFНЇОEчТ└П)Т┘П<НЇОDТ√П[Т≈НЇОBIТП&НЇО>вТ▄П'Т█П8НЇО=ТНЇО9 ПIНЇО6(Ті ТїПOНЇО4^Т▀П*Т▄П5НЇО2⌠ТщТчПPНЇО0хТ∙ПPТ√НЇО.ЧТП%НЇО+▄Т÷ПSТ═НЇО)аТжП7ТвП!НЇО'ВТ└П[НЇО&,ТйП[НЇО$aТ═ПYНЇО"≈ТЄПFТ╣НЇО%Т┬ПYТ┴НЇОZТ·ПCТ÷НЇО░Т║П!Т╒П?НЇОеТ╣ТІПHНЇОЗТ╞Т╟pqПDНЇО0Т2ПGТ3НЇОeТЪ╙Ї=ПSМDorado Midas ManualEdward R. Fiala24 June 19834537. MIRdebug FeatureDuring ordinary operation, an IMX parity error or breakpoint halts Dorado after t2 of theinstruction affected by the parity error. Since MIR is loaded at t2, the MIR value with bad parityhas been overwritten when the machine stops, so if the path between the microstore and MIR isexperiencing intermittent failures, it will be difficult to diagnose what has gone wrong.To aid checkout in this case, the control section has a debugging aid called MIRdebug, which willdisable the clock to MIR at t2 of an instruction with bad parity. When this aid is enabled, MIRwill still contain the bad data after the error-halt. This feature can be invoked by enabling"MIRdebug" in the sub-menu put up by the "Reset" action. If a parity error halt occurs whileMIRdebug is enabled, then Midas will print the value read from IMX[CIA] so that you cancompare this with the value in MIR on the display to find out which bits are not propagatingfrom IMX into MIR.The liability of this debugging aid is that you will not be able to continue from a breakpoint orIMX parity error halt, so you should not enable MIRdebug unless you are searching for this typeof hardware failure.38. Failure DiagnosisSome actions to analyze test failures and report the hardware components involved have beenconsidered, and are likely to be implemented for IMBD, IMX, IFUM, RM, and STK.Storage, Map, and cache failure analysis programs are essential, but should be provided outsideMidas.39. Baseboard Microcomputer StuffThe Alto can communicate directly with the Baseboard section of any Dorado connected to itthrough its Diablo Printer interface as detailed in the "Dorado Debugging Interface" document.It can:(a) Select any one of the connected Dorados;(b) Control the muffler/manifold system or give control to the baseboard microcomputer(c) Interrupt the baseboard microcomputer;(d) Pass information to the microcomputer through CPREG; and(e) Read 8 bits of information from the microcomputer through the DoradoInmechanism.Midas does (a) and (b) during initialization and during the "Dtach" action, as discussed in the"Starting Midas" section; Midas uses (c), (d), and (e) together with a large set of communicationconventions to exchange information with a program running on the baseboard microcomputer.$ABSOLUTE is the fundamental microcomputer memory, 8 bits wide. It contains all informationother than mufflers which Midas can access on the baseboard. This memory is divided into aRAM (addresses 0 to 7778 or 0 to 1FF16) and a ROM (addresses 1000008 to 1777778 or 800016 toFFFF16). The amount of ROM is adjustable; current Dorados have storage only for addresses1400008 to 1777778. The microcomputer stores its internal registers and other information ofЪНЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrНЇО^eqТБПIТЦО]ьsО^eqНЇО\⌡Т┤Т┬П(О\sО\⌡qНЇОZпТ≥ПCТ НЇОYТПYНЇОU■Т┬Т┴ПOНЇОSиТ∙ОSвТ┬Т┴ПDНЇО=ТПDНЇО9 Т5ПOНЇО7пТ╚ПLНЇО6ТНЇО2⌠ТмПFТнНЇО0хТҐП'ТЎП6НЇО.ЧТьТыП@НЇО-3ТПQНЇО)аТ∙Т√ПHНЇО'ВТ©П;ТюНЇО&,ТОТППCНЇО$aТ∙П$Т√П;НЇО"≈Т├Т┤П[НЇО лТёpqТєНЇОТ┬ Т┴ПRНЇО7ТПQНЇОеТ∙Т√ПHНЇОЗТҐТЎП@НЇО0Т┬ПIТ┴НЇОeТП5НyОСП-НyО)П/НyО ^ПCНyО⌠П8 ╨ЇL=П\Б=Dorado Midas ManualEdward R. Fiala24 June 198347load and execute Dorado boot microcode, which loads and starts the system microcode.During this sequence and afterwards, the microcomputer reports what is happening on its statuslight, which will repeat a sequence of blinks followed by a pause during any problem condition.The light sequences are interpreted as follows (the light blink information is also in PROBLEMSon the Midas display):1 blinkboot in progressWait for disk, power supplies, stable clock, etc. This isnormal during a power-on or 3-push boot sequence, asdiscussed below.2 blinksboot failedTried to boot Dorado microcode but didn't get theappropriate handshake.3 blinkstransient power problemPower supply voltages went bad, now good again (details inBADSUPPLYSPEC on display; TGLITCH shows the timewhen this transient ended; MAXVOLTS or MINVOLTSreveals the magnitude of the transient). Presently, onlyvoltage variations cause this condition, but eventuallyamperage variations may also cause it (MAXAMPS andMINAMPS on the display).4 blinkspower problemVoltages are now out-of-spec (details in OUTOFSPEC andVOLTS on the display); eventually amperages may alsocause this condition (AMPS on the display).5 blinkspowered downGet this after powering down with a seven button-pushsequence (see below).6 blinksover temperaturePowered down because the temperature on some board wentover 60o C (MAXTEMP, MAXTEMP+1, andMAXTEMP+2 show details).7 blinkscan't get CP controlCan't get muffler/manifold control because Midas is hoggingit.solid greenAOKBootstrap sequence is believed to have completedsuccessfully, there have been no occurrences of the errorconditions indicated by 3 through 6 blinks., and thebaseboard microcomputer gets regular CP control.light offmicrocomputer downpower is off, the microcomputer crashed, or the light burnedout (unlikely because LED's are long-lasting)As mentioned above, the main breaker switch on the Dorado turns on only the +5 volt supplyand one fan. The basic "on" state minimizes power consumption, and enables the baseboardmicrocomputer to turn on other power supplies and fans.When the user depresses the boot button on the back of the keyboard for at least 0.2 seconds andnot more than 2.5 seconds, the microcomputer records an event called a "button push"; depressingfor less than 0.2 seconds or longer than 2.5 seconds is ignored; depressing for longer than 2.5seconds will nullify the entire boot sequence. The microcomputer will count button pushes until1.5 seconds has elapsed with the button up; then it will carry out an action as follows:1 push--ignored; standard emulators also monitor the raw boot button and may takesome action. Currently, they go through a software bootstrap sequence under theassumption that currently loaded microcode is correct and running normally.2 pushes--stops and resets the microprocessor and starts it in task 0 with tasking turnedНЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНyОbqТ═ПIТ║ НЇО^╛Т╔ТіПFНЇО\АТ÷ПHТ═НЇО[Т√Т≈ПLНЇОYLТНxОV┼sТ─Н╛Н&√ТдП6Н&√ОU*ТъТЮН&√ОSиТНxОQ+Т─Н╛ Н&√ТТП)Н&√ОOйТНxОM,Т─Н╛Н&√Т▌П2Т▐Н&√ОKкТЄП0Н&√ОJjТчТъН&√ОI ТьП4ТыН&√ОG╗Т*П,Т+ Н&√ОFHТАП.ТБН&√ОDГТНxОBIТ─Н╛Н&√Т╙П.Н&√О@ХТБП4Н&√О?┤ТП+НxО<ИТ─Н╛Н&√ТжТвН&√О;┬ТНxО8ЙТ─Н╛Н&√Т┌П0Н&√О7BТПО7оО7BТЯН&√О5БТНxО3CТ─Н╛Н&√Т┐П6Н&√О1ЦНxО/DТ─ Н╛Н&√ТuТvН&√О-ДТеТфН&√О,┐ТТН&√О+"ТП0НxО(└Т─Н╛Н&√П/Т│Н&√О'#ТП-НЇО#тqТєПGТ╔НЇО" Т©ТюПLНЇО ?ТП7НЇОмТ┬ПCТ┴НЇОТ─Т│ПXНЇО8ТЇТ╦ПFНЇОmТ≈Т≤ПAНЇОёТШПXНyО1ТхП8ТиНyОfТИП(ТЙП(НyО⌡ТПKНyО*Т÷ПEТ═hЇ Ц=П](yDorado Midas ManualEdward R. Fiala24 June 198348off at location 10678 (which is "InitMap" for the Alto emulator). This is intended to bea forcible restart of currently-loaded microcode.3 pushes--load IM from the Dorado boot loader and start it running as for 2 pushes.This initiates a complete microcode bootstrap sequence, similar to the automatic power-on boot. It assumes nothing about the current state of the machine.4, 5, or 6 pushes--same as 3 pushes.7 pushes--power down; all of the supplies and fans except the 5 volt supply and 1 fan arepowered down in a safe sequence, taking about 30 seconds. The 5 volt supply can thenbe shut down from the main breaker switch; avoid turning off the main breaker switchuntil the microcomputer has completed shutting down the disk and other supplies becauseyou will invoke the power failure safety circuits in the disk drives.8 or more pushes--ignored; the user does this when he makes a mistake and wants tostart over.Under normal conditions, in response to the boot button being pushed or the main breaker beingturned on, the microcomputer will show 1 blink for about 60 seconds and then show solid green;if Midas attaches to the machine, the status light will usually show solid green, but will show 7blinks (Midas hogging CP bus) during long-running Midas actions.Note: if the Dorado was powered down at the onset of a button push sequence, any number ofpushes from 1 to 3 will do a total (3 push) boot.Note: it is unsafe to turn on disk power when the -5 volt, -2 volt and +12 volt supplies are onbecause, the resulting power surge will blow breakers in the building wall circuits. For thisreason, be sure to power down the Dorado logic supplies (7 push sequence discussed above)before turning on the disks; then go through the complete power up sequence with a normal bootsequence (1 to 3 pushes).Note: Since the microcomputer uses the +5 volt supply itself, it will crash if that supply fails andmight subsequently auto-boot itself if the +5 volt supply starts working again. An over-temperature shutdown never turns off the +5 volt supply.Note: If the Dorado is alreay powered-on, the full bootstrap sequence can also be initiated bypressing the reset button on the front panel of the Dorado chassis (inside the cabinet, if theDorado is cabinet-mounted). However, if the Dorado is in the shut down state, pushing the resetbutton has no effect.For full user-level details on booting, consult "Dorado Booting" by Ed Taft([Indigo]DoradoBooting.press) and "Dorado Booting--Implementation" by EdTaft ([Indigo]DoradoBootingImple.press).ЪНЇОgpТ─Н"sqН5 Т НG?ОfЯpНyОbqТ▒Оa▒sОbqПDНyО`SТП1НyО\АТІП:ТЇНyО[Т═П#Т║П4НyОYLТПDНyОUзП$НyОRhТ─П2Т│П'НyОP·Т⌠П'Т■П.НyОNсТ╛ТґpП)НyОMТ╔П.ТіП)НyОK>ТПEНyОGлqТ╞Т╟П4НyОFТ НЇОB▐Т█П0Т▌П.НЇО@еТ▒ПWТ▓НЇО>ЗТіПJТїНЇО=/ТП@НЇО9ҐpqТ≤ПVНЇО7СТП1НЇО4│pqТ≤П9Т≥П"НЇО2ІТнПUТоНЇО0ЛТйТкП<НЇО/!Т┤П9Т┬П%НЇО-VТНЇО)ДpqТ┐Т└ПYНЇО(ТПП2ТЯП'НЇО&OТП8НЇО"щpqТ╚ПZНЇО!ТхП^НЇОHТ█П6Т▌П*НЇО}ТНЇОТхТиПCНЇОAТП5ТНЇОvТП4Ъ :Ї/<ПQЪDorado Midas ManualEdward R. Fiala24 June 19834940. Command Files Used With "RdCmds"At the time this was written, the following command files were in use:Table 9: Command Filespokeshow CPREG, STROBE, and D1OUT in the right column and become passive for manual hardwarepoking.normalrestore "normal" Midas display with the baseboard voltages, temperature, and currents in the rightdisplay column.testsrestore "normal" Midas display with the hardware testing items in the right display column.svcrashwrite the Midas display followed by a pretty-print of all DMux registers on the file Crash.Report.procshow ProcH/L DMux signals in middle column.controlshow ContA and ContB DMux signals in middle column.mmcshow MemC DMux and other signals in middle column.mmdshow MemD DMux signals in middle column.mmxshow MemX DMux signals in middle column.ifudshow IFU DMux signals in middle column.dskethshow disk and ethernet controller DMux signals in middle column.dspshow display controller DMux signals in middle column.tpcshow 208 TPC registers in middle column.tlinkshow 208 TLINK registers in middle column.alufmshow 208 ALUFM locations in the middle column.tshow 208 T registers in middle column.rbaseshow 208 RBASE registers in middle column.membaseshow 208 MEMBASE registers in middle column.tioashow 208 TIOA registers in middle column.mdshow 208 MD registers in middle column.brloshow BR 0 to BR 17 in middle column.brhishow BR 20 to BR 37 in middle column.histshow first 208 DMux histories in right column.vhshow first 208 DMux vertical histories in middle column.НЇОf╙pТ─Н"sqН5 Т НG?ОfЯpНЇОaвrП%НЇО^eqПFН!ЮОZСtТ▓НxОW╔sН╛Т▌П<Т▐Н╛ОV!НxОT²Н╛ТіПHТїН╛ОS<ТНxОQ╦Н╛ТГП>ТХНxОP4Н╛ТіП#ТїП?НxОM∙Н╛ТП+НxОLН╛П3НxОJ█Н╛П2НxОI Н╛П(НxОG┘Н╛П(НxОFН╛П'НxОD}Н╛П@НxОBЫН╛П6НxО@[Н╛О?нО@[НxО>ЁН╛О>&О>ЁП"НxО=Н╛О<О=П&НxО;eН╛О:ьО;eНxО9ҐН╛О90О9ҐП"НxО8Н╛О7┴О8П$НxО6oН╛О5БО6oП!НxО4гН╛О4:О4гНxО3 Н╛П$НxО1°Н╛П%НxО0Н╛О/▀О0НxО.qН╛О-ДО.qП*ЪЇ-а:/:JЗDorado Midas ManualEdward R. Fiala24 June 19835041. DMux Signal Assignments Table 10A: Control Section DMux Signals*Original addresses 0-77 and 260-377 are from ContA, 100-257 from ContB. Midas rearrangesmany signals for convenient viewing. The second column shows the way Midas displays them.DMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress 0StopCJNK00 0StopAlways 1preStartCyclea 1preStartCycleaAlways 2dStartCycle 2dStartCycleAlways 3Phase0 3Phase0Always 4Phase4 4Phase4Always 5RWTPCorRWIM 5RWTPCorRWIMAlways 6BigBDispatch 6BigBDispatchTn ge 2 & switch' 7Dispatch 7DispatchTn ge 2 & switch' 10WIM' 10WIM'Always 11RIM' 11RIM'Always 12WTPC' 12WTPC'Always 13RTPC' 13RTPC'Always 14FF=Notify'14:170 15FF=MulStep 16FF=BDispatch 17FF=BigBDispatch 20:37CIAInc[0:15]CIAINC120:37CIAInc[0:15]Tn ge 1 40:57CIA[0:15]CIA240:57CIA[0:15]Tn ge 2 60* CABlockBNT360:730 61:70* bFF[0:7]74:77Bnt[0:3]Tn ge 2 71:74* JCN[0:3] 75:77* bJCN[4:6]100:117* MIR[1:16]PENC4100:1130114:117bPEnc[0:3]Always120:121--TNIA5120:121--122:137TNIA[2:15]122:137TNIA[2:15]Unless return or IFUJump140:141--BNPC6140:141--142:157BNPC[2:15]142:157BNPC[2:15]Never 160CBTempSenseCTASK7160:1730 161bSWd'174:177CTASK[0:3]Tn ge 2 162* IMLH 163* bRSTK.0 164* bdRSTK.0 165* bdIMLH 166* bdIMRH 167* bdJCN.7170:173CTASK[0:3]174:177CTD[0:3]* Midas extracts the 44 MIR and 44 bdIM signals and arranges these as registers (MIR and IMOUT). This informationresides in DMuxTab in the peculiar MIR-loading format discussed in the "Dorado Debugging Interface" document, but isviewed by users in the standard IM format.ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНЇОaвrТ÷qТ└НкО^BsТ▓П(НЇОZпqТгПAТхНЇОYТюПEТаНЇОUзtН─НН#ЬН*+Н/рН9А НЇОTyН─НН#ЬН*+Н/рН9АНЇОSНН#ЬН*+НЇОPuТ─Н─НН$лН*+Н/рН9АНЇОN╟Н─ Н*+Н/р Н9АНЇОMOН─ Н*+Н/р Н9АНЇОKНН─Н*+Н/рН9АНЇОJ█Н─Н*+Н/рН9АНЇОI-Н─ Н*+Н/р Н9АНЇОGлН─Н*+Н/рН9АТНЇОFkТ─Н─Н*+Н/рН9АТНЇОE Т─Н─Н*+Н/рН9АНЇОC╘Н─Н*+Н/рН9АНЇОBIН─Н*+Н/рН9АНЇО@ХН─Н*+Н/рН9АНЇО?┤Н─ Н*+Н/рНЇО>&Н─ НЇО<фН─НЇО;eН─НЇО8ёН─НН$лН*+Н/рН9АТНЇО5БТ─Н─НН$лН*+Н/рН9АТНЇО3 Т─Н─НН$лН*+Н/рНЇО1©Н─ Н*+Н/рН9АТНЇО0_Т─Н─ НЇО.ЧН─ НЇО,<Н─ НН$лН*+Н/рН*+О*шН/р Н9АНЇО(Н─НН$лН*+Н/рНЇО&╧Н─ Н*+Н/р Н9АТЪТ НЇО#ЬН─НН$лН*+Н/рНЇО"≈Н─ Н*+Н/р Н9АНЇОуТ─Н─ НН$лН*+Н/рНЇОtН─Н*+Н/р Н9АТНЇОТ─Н─НЇОЁН─НЇОRН─ НЇОЯН─НЇО▒Н─НЇО0Н─НЇОоН─ НЇОnН─НЇОfТ┬Т┴П[НЇОТ─Т│П[НЇО ╔ТП*├Їы=Г\2Dorado Midas ManualEdward R. Fiala24 June 198351Table 10B: Control Section DMux SignalsDMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress200:217* bdxx for IM[1:16]NEXT10200:2030214:217Next[0:3]Always220:237* bdxx for IM[17:32]CTD11220:2330234:237CTD[0:3]Tn ge 1240:243CS[0:3]'BDbRA12240:243CS[0:3]'BDbAlways244:245RAQuad[0:1]i244:245RAQuad[0:1]iNever246:257RA[1:10]246:257RA[1:10]Always 260CallTOPE13 2600261:277ToPE[1:15]261:277ToPE[1:15]Always 300* bJCN.7CJNK114 300CallUsually 301* IMRH 301bSWd'Always 302GND 302GNDAlways 303LocalBr'a 303LocalBr'aAlways 304IFUNext'a 304IFUNext'aAlways 305LongJump'a 305LongJump'aAlways 306Return'a 306Return'aAlways 307CondBr'a 307CondBr'aAlways 310bFFok'c 310bFFok'cAlways 311FA=0' 311FA=0'Always 312FA=1' 312FA=1'Always 313bDoCBr 313bDoCBrNever 314FF=UseDMD 314Link_BMuxaTn ge 1 315FF=TOffIsOK 315B_Link'Tn ge 1 316RIMorRTPCdly 316RIMorRTPCdlyTn ge 2 317MulStep 317MulStepTn ge 2 & no switch 320FF=TaskingOnFFEQ15 320FF=TaskingOnAlways 321FF=TaskingOff 321FF=TaskingOffAlways 322FF=MidasOn 322FF=MidasOnAlways 323Link_BMuxa 3230 324FF=WriteLink 324FF=WriteLinkAlways 325FF=Link_CPReg 325FF=Link_CPRegAlways 326FF=ReadLink 326FF=ReadLinkAlways 327B_Link'327:3310330:333Bnt[0:3] 332FF=UseDMDAlways334:337bPEnc[0:3] 333FF=TOffIsOkAlways 334FF=Notify'Always 335FF=MulStepAlways 336FF=BDispatchAlways 337FF=BigBDispatchAlways* Midas extracts the 44 MIR and 44 bdIM signals and arranges these as registers (MIR and IMOUT). This informationresides in DMuxTab in the peculiar MIR-loading format discussed in the "Dorado Debugging Interface" document, but isviewed by users in the standard IM format.НЇОf╙pТ─Н!цqН5Т НG?ОfЯpНкОbsТ▓П(НЇО^РtН─НН#ЬН*+Н/рН9А НЇО]▓Н─НН#ЬН*+Н/рН9АНЇО\1НН#ЬН*+НЇОY)uН─Т─НН$лН*+Н/рН*+ОWхН/рН9АНЇОUН─НН$лН*+Н/рН*+ОSіН/рН9АТНЇОPДН─ НН$лН*+Н/р Н9АНЇОO┐Н─Н*+Н/рН9АНЇОN#Н─Н*+Н/рН9АНЇОKaТ─Н─НН$лН*+Н/рНЇОJН─ Н*+Н/р Н9АНЇОG?Н─НН$лН*+Н/рН9АНЇОEчН─Н*+Н/рН9АНЇОD}Н─Н*+Н/рН9АНЇОCН─Н*+Н/рН9АНЇОA╪Н─Н*+Н/рН9АНЇО@[Н─ Н*+Н/р Н9АНЇО>ЗН─Н*+Н/рН9АНЇО=≥Н─Н*+Н/рН9АНЇО<8Н─Н*+Н/рН9АНЇО:ьН─Н*+Н/рН9АНЇО9wН─Н*+Н/рН9АНЇО8Н─Н*+Н/рН9АНЇО6╣Н─Н*+Н/р Н9АТНЇО5UТ─Н─ Н*+Н/рН9АТНЇО3ТТ─Н─Н*+Н/рН9АТНЇО2⌠Т─Н─Н*+Н/рН9АТНЇО/яТ─Н─НН$лН*+Н/рН9АНЇО.qН─Н*+Н/рН9АНЇО-Н─ Н*+Н/р Н9АНЇО+╞Н─ Н*+Н/рНЇО*NН─Н*+Н/рН9АНЇО(НН─Н*+Н/рН9АНЇО'█Н─ Н*+Н/р Н9АНЇО&,Н─Н*+Н/рНЇО$кН─Н*+Н/рН9АНЇО#jН─ Н*+Н/р Н9АН*+О" Н/р Н9АН*+О ╘Н/р Н9АН*+ОHН/рН9АН*+ОГН/рН9АНЇОъТ┬Т┴П[НЇО~Т─Т│П[НЇОТП*ЪйЇS=ГQ╦)Dorado Midas ManualEdward R. Fiala24 June 198352Table 10C: Control Section DMux SignalsDMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress340:343pNext[0:3]CJNK316340:3430 344Next=0 344Next=0Always 345CTask=0 345CTask=0Always 346PEncGtTrueNext' 346PEncGtTrueNext'Always 347PEncLtTrueNext' 347PEncLtTrueNext'Always 350StopTasks 350StopTasksTn ge 2 351PEnc=CT' 351PEnc=CT'Always 352TPCBypass 352TPCBypassTn ge 2 353PreEmpting' 353PreEmpting'Always 354bHoldA 354bHoldAAlways 355RepeatCurz 355RepeatCurzAlways 356bSwitch'a 356bSwitch'aTn ge 2 357bSwitchUp' 357bSwitchUp'Tn ge 2 360--READY17 360--361:377Ready[1:15]361:377Ready[1:15]MIR166:171--MIR[0:35] in MIR formatIMOUT172:175--bdIM[0:35] in MIR formatTable 11: BaseBoard DMux SignalsDMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress2200:2207ClkRateCLKRUN1102200:2207ClkRateNever 2210ECLup 2210ECLupNever 2211EnRefreshPeriod' 2211EnRefreshPeriod'Never 2212IOReset' 2212IOReset'Never 2213RunRefresh 2213RunRefreshNever 2214MASync 2214MASyncNever 2215TBaseTempSense 221502216:2217--2216:2217--ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНкОbsТ▓П(НЇО^РtН─НН#ЬН*+Н/рН9А НЇО]▓Н─НН#ЬН*+Н/рН9АНЇО\1НН#ЬН*+НЇОY)uН─ НН$лН*+Н/рНЇОWхТ─Н─Н*+Н/рН9АНЇОVgН─Н*+Н/рН9АНЇОUН─Н*+Н/рН9АНЇОSіН─Н*+Н/рН9АНЇОREН─Н*+Н/рН9АТНЇОPДТ─Н─Н*+Н/рН9АНЇОO┐Н─Н*+Н/рН9АТНЇОN#Т─Н─ Н*+Н/р Н9АНЇОLбН─Н*+Н/рН9АНЇОKaН─ Н*+Н/р Н9АНЇОJН─Н*+Н/рН9АТНЇОH÷Т─Н─ Н*+Н/р Н9АТНЇОEчТ─Н─НН$лН*+Н/рНЇОD}Н─ Н*+Н/р НОA╪Н$лН*+Н/рТНО>ЗН$лН*+Н/рНйО:'sТ▓П!НЇО6ЭtН─НН#ЬН*+Н/рН9А НЇО5⌡Н─НН#ЬН*+Н/рН9АНЇО4:НН#ЬН*+НЇО12uН─НН$лН*+Н/рН9АНЇО/яТ─Н─Н*+Н/рН9АНЇО.qН─Н*+Н/рН9АНЇО-Н─Н*+Н/рН9АНЇО+╞Н─ Н*+Н/р Н9АНЇО*NН─Н*+Н/рН9АНЇО(НН─ Н*+Н/рНЇО'█Н─Н*+Н/рЪ·Ї& 3YB╙Dorado Midas ManualEdward R. Fiala24 June 198353Table 12A: Processor Section DMux Signals*Processor DMux addresses (400 to 777) are arranged so that the first 108 in each group of 208 arefrom ProcH, the last 108 from ProcL. Signals are frequently duplicated (one from each board).Midas does not rearrange any signals from the processor section.MidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberALUB20400:417alubif driven from BMux or from constantALUA21420:437aluaTn ge 1 driven from small constant & not shiftABCON22 440MarMuxAEn'Tn ge 1 441AmuxEn'Tn ge 1442:443Amux0 to 1Tn ge 1 444IOBoutTn ge 1 445BmuxEn'Tn ge 1446:447Bmux0 to 1Tn ge 1450:457=440:447Tn ge 1PERR23 460EMU'Always 461CkMdParity'Tn ge 2462:463-- 464IOPerrNever 465MdPerrNever 466RmPerrNever 467TmPerrNever 470StkSelaAlways 471StkSelSavedNever 472IOBoutSavedTn ge 2 473_MDSavedNever474:477=464:467NeverSHMV24500:517shmvPmux odd or shift'MAR25520:537MAR.0' to MAR.15'Tn ge 1 driven from processor, no shift,Tn eq 2 bits 8:15 when driven by IFU,Tn eq 2 when not driven--26540:557--PRFA27 560Last=Curr'Tn ge 2 561Curr=Next'Always 562Shift'Always 563IOBin'Tn ge 1564:566FA=0'a to FA=2'aAlways 567FA=3'Always570:577=560:567As aboveЪНЇОf╙pТ─ЫЬЗН!цqН5Т НG?ОfЯpН"ОbsТ▓ЫPЬЪЗЪЫЬЗЫPЬЪЗЪЫЬЗНЇО^оqТ▐ЫPЬЪЗЪП?Т░О^BuО^оqО^BuО^оqНЇО]ТІО\xuО]qТЇП-НЇО[:ТП@НЇОXUtЫЬЗН:НҐН@Н)W НЇОVТН:НҐН@Н)WНЇОU■Н:НЇОR▀uНКНҐН@Н)WП$НЇОOйНКНҐН@Н)WП.НЇОMНКНҐТ─Н@ Н)WТНҐОK╗Т─Н@Н)WТНҐОJGН@Т─ Н)WТНҐОHФТ─Н@Н)WТНҐОG┘Т─Н@Н)WТНҐОF$Н@Т─ Н)WТНҐОDдН@Н)WНЇОBНКНҐТ─Н@Н)WНҐО@║Н@ Н)WТНҐО?AН@НҐО=ЮТ─Н@Н)WНҐО<Н@Н)WНҐО;Н@Н)WНҐО9ҐН@Н)WНҐО8]Н@Н)WНҐО6ЭН@ Н)WНҐО5⌡Н@ Н)WТНҐО4:Т─Н@Н)WНҐО2зН@Н)WНЇО0НКНҐН@Н)WТНЇО-VНКНҐН@Т─Н)WТП&Н)WО+ЖП%Н)WО*∙НЇО'сНКНҐН@НЇО%НКНҐТ─Н@ Н)WТНҐО#╠Т─Н@ Н)WНҐО"PН@Н)WНҐО ОН@Н)WТНҐО▐Н@Т─Н)WНҐО.Н@Н)WНҐОмН@Н)WТпЇI>ГLб╡Dorado Midas ManualEdward R. Fiala24 June 198354Table 12B: Processor Section DMux SignalsMidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberSCCON30 600-- 601RepeatCurrCAlways 602HoldaAlways 603LdTaskSim'Always 604FFshift'Always 605ShcWriteEn'Tn ge 1 606LoadCnt'Always 607PropCnt'if DecCnt is false 610--611:612= 601:602Always 613LdHoldSim'Tn ge 1614:616=604:606As above 617DecCnt'AlwaysQPDCON31 620QshiftL'Tn ge 1 621QshiftR'Tn ge 1 622RmaskEn'Tn ge 1 623LmaskEn'Tn ge 1 624ShiftBitsEn'Tn ge 1625:627Pmux0 to 2Tn ge 1630:633=620:623Tn ge 1 634ALUFWriteEn'Always635:637= 625:627Tn ge 1ALUCON32 640Pdata.00Tn ge 1 if source is ALU barring shifter 641Pdata.04Tn ge 1 if source is ALU 642TIOAWriteEn'Tn ge 1 643TIOABypassAlways 644MBWriteEn'Tn ge 2 645MBBypassAlways646:647MBMux0 to 1Tn ge 1 650aluCinNever 651Pdata.08Tn ge 1 if source is ALU 652Pdata.12Tn ge 1 if source is ALU653:656aluF0 to 3Never 657aluMNeverNEXTCL33660:663LastNext.0' to .3'Tn ne 1664:667CurrLast.0' to .3'Tn ne 1670:677=660:667Tn ne 1RADDR34700:703Task2Back.0' to 3'Tn ge 2704:707Task3Back.0' to 3'Tn ge 2710:713RbWadr.0' to 3'Sometimes Tn ge 2714:717RbWadr.4 to 7Tn ge 2ЪНЇОf╙pТ─ЫЬЗН!цqН5Т НG?ОfЯpН"ОbsТ▓ЫPЬЪЗЪЫЬЗЫPЬЪЗЪЫЬЗНЇО_9tН:НҐН@Н)W НЇО]ьН:НҐН@Н)WНЇО\wН:НЇОYouНКНҐТ─Н@НҐОXН@ Н)WНҐОVўН@Н)WНҐОUMН@ Н)WНҐОSЛН@Н)WНҐОR▀Н@ Н)WТНҐОQ+Т─Н@Н)WНҐОOйН@Н)WТНҐОNiТ─Н@НҐОMН@Н)WНКОK╗НҐН@ Н)WТНҐОJGН@Н)WНҐОHФТ─Н@Н)WНЇОF$НКНҐН@Н)WТНҐОDдТ─Н@Н)WТНҐОCcТ─Н@Н)WТНҐОBТ─Н@Н)WТНҐО@║Т─Н@Н)WТНҐО?AН@Т─ Н)WТНҐО=ЮН@Н)WНКО<Т─НҐН@Н)WНҐО;Н@Н)WТНЇО8]НКНҐТ─Н@Н)WТП&НҐО6ЭТ─Н@Н)WТНҐО5⌡Т─Н@Н)WТНҐО4:Т─Н@ Н)WНҐО2зН@ Н)WТНҐО1yТ─Н@Н)WНҐО0Н@ Н)WТНҐО.ЇТ─Н@Н)WНҐО-VН@Н)WТНҐО+ЖТ─Н@Н)WТНҐО*∙Н@Т─ Н)WНҐО)4Н@Н)WНЇО&sНКНҐН@Н)WТНҐО%Н@Т─Н)WТНҐО#╠Н@Н)WНЇО ОНКНҐН@Т─Н)WТНҐО▐Н@Т─Н)WТНҐО.Н@Т─Н)WТНҐОмН@Т─Н)WТЪіЇI5чLбДDorado Midas ManualEdward R. Fiala24 June 198355Table 12C: Processor Section DMux SignalsMidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberSTKRB35 720BCWriteEn'Tn ge 2 721Cnt=Zero'Never** 722IoattaNever** 723ResEqZero'Never** 724ResLtZero'Never** 725ALUCarryNever** 726Overflow'Never** 727RmLtZero'Never** 730RBaseBypass'Tn ge 1 731SelRBaseWadr'Always 732RBaseWriteEn'Tn ge 1 733BumpRBaseAlways 734BumpRSTKAlways 735StkPMux1Always 736StkPWriteEn'Always 737RmOdd'Never**RTSB36 740ReSchedWrEn'Always 741NextMacroAlways 742RbWriteEn'Tn ge 2 743RbSelMdTn ge 2 744RbBypassDlyNever** 745TbWriteEn'Tn ge 2 746TbSelMdTn ge 2 747TbBypassTn ne 1 750StkPSaveEn'Tn ge 1 751StkErrorNever**752:757= 742:747As abovePJUNK37 760FFok'aAlways 761-- 762NextData'Always 763B_ExtAlways 764FF.0memAlways 765FF.1memAlways 766RisIFdataAlways 767TisIFdataAlways 770FFok'bAlways 771_MDAlways 772_MDIAlways 773B_ExtAlways774:775SbTskDly.0' to 1'Never 776RisIFdataAlways 777TisIFdataAlwaysЪНЇОf╙pТ─ЫЬЗН!цqН5Т НG?ОfЯpН"ОbsТ▓ЫPЬЪЗЪЫЬЗЫPЬЪЗЪЫЬЗНЇО_9tН:НҐН@Н)W НЇО]ьН:НҐН@Н)WНЇО\wН:НЇОYouНКНҐТ─Н@ Н)WТНҐОXТ─Н@Н)WНҐОVўН@Н)WНҐОUMН@ Н)WНҐОSЛН@ Н)WНҐОR▀Н@Н)WНҐОQ+Н@Н)WНҐОOйН@Н)WНҐОNiН@Н)WТНҐОMТ─Н@Н)WНҐОK╗Н@Н)WТНҐОJGТ─Н@Н)WНҐОHФН@Н)WНҐОG┘Н@Н)WНҐОF$Н@Н)WНҐОDдН@Н)WНЇОBНКНҐН@Н)WНҐО@║Н@Н)WНҐО?AН@ Н)WТНҐО=ЮТ─Н@Н)WТНҐО<Т─Н@ Н)WНҐО;Н@ Н)WТНҐО9ҐТ─Н@Н)WТНҐО8]Т─Н@Н)WТНҐО6ЭТ─Н@ Н)WТНҐО5⌡Т─Н@Н)WНҐО4:Н@Н)WТНЇО1yНКНҐТ─Н@Н)WНҐО0Н@НҐО.ЇН@Н)WНҐО-VН@Н)WНҐО+ЖН@Н)WНҐО*∙Н@Н)WНҐО)4Н@Н)WНҐО'сН@Н)WНҐО&sН@Н)WНҐО%Н@Н)WНҐО#╠Н@Н)WНҐО"PН@Н)WНҐО ОН@Н)WНҐО▐Н@Н)WНҐО.Н@Н)WЪЭЇc2AK╗ЇDorado Midas ManualEdward R. Fiala24 June 198356Table 13A: MemC DMux SignalsDMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress 1000ProcVA.04PVAH 401000:10030 1001true1004:1017ProcVA.04 to 15Tn ge 2 & no clk 1002WantCHdly'1003:1017ProcVA.07 to 19 1020MemB.0PVAL 411020:1037ProcVA.16 to 31Tn ge 2 & no clk1021:1022ProcVA.05 to 06 1023MemB.11024:1037ProcVA.20 to 311040:1047Aad.0a to 7aMAPAD 421040:104601050:1057MapAd.1 to 81047:1057MapAd.0 to 8Never** 1060dVA_Vic 1061ForceDirtyMiss 1062UseMcrV 1063DisBR 1064DisCflags 1065DisHold 1066NoRefHIT 431060:10660 1067MiscPCHP' 1067MiscPCHP'Tn ge 21070:1071ColVic.0 to 11070:1071ColVic.0 to 1Sometimes 1072HitColVA.par 1072HitColVA.par0 on miss 1073HitColDirty 1073HitColDirty0 on miss 1074Hita 1074Hita0 on ForceMiss if Tn ge 21075:1077MemB.2 to 41075:107701100:1101Victim.0' to 1'HOLD 441100:110101102:1103NextV.0' to 1' 1102true 1104MiscHold' 1103WantCHdly'Tn ge 1 1105MDhold' 1104MiscHold'Tn ge 2 1106RefHold' 1105MDhold'Tn ge 2 1107BLretry 1106RefHold'Tn ge 2 & not ForceMiss 1110AwasFree' 1107BLretryIf forced to 0 1111Dbusy 1110AwasFree'Tn ge 2 1112DbufBusy 1111DbusyTn ge 2 1113AtookST 1112DbufBusyTn ge 2 1114SomeExtHold' 1113AtookSTTn ge 2 1115Afree' 1114SomeExtHold'On StkError % CHoldReq 1116StartMap' 1115Afree'if EcHasA 1117AwantsMapFS' 1116StartMap'Always 1117AwantsMapFS'AlwaysЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpН┐ОbsТ▓НЇО^РtН─НН#ЬН*+Н/рН9А НЇО]▓Н─НН#ЬН*+Н/рН9АНЇО\1НН#ЬН*+НЇОY)uТ─Н─НН$лН*+Н/рНЇОWхН─Н*+Н/рН9АТНЇОVgТ─Н─ НЇОUН─ТНЇОREТ─Н─НН$лН*+Н/рН9АТ НЇОPДН─НЇОO┐Т─Н─НЇОN#Н─ТНЇОKaН─Т─НН$лН*+Н/рНЇОJН─Н*+Н/рН9АНЇОG?Н─НЇОEчН─ НЇОD}Н─НЇОCН─НЇОA╪Н─НЇО@[Н─НЇО>ЗН─НН$лН*+Н/рНЇО=≥Н─Н*+Н/рН9АТНЇО<8Н─Т─Н*+Н/рН9АНЇО:ьН─Н*+Н/рН9АТНЇО9wТ─Н─ Н*+Н/р Н9АТНЇО8Т─Н─Н*+Н/рН9АТҐТЎНЇО6╣Н─Т─ Н*+Н/рНЇО3ТН─НН$лН*+Н/рНЇО2⌠Н─ Н*+Н/рНЇО12Н─Н*+Н/р Н9АТНЇО/яТ─Н─Н*+Н/рН9АТНЇО.qТ─Н─Н*+Н/рН9АТНЇО-Т─Н─Н*+Н/рН9АТЕ ТФ НЇО+╞Т─Н─Н*+Н/рН9АТНЇО*NТ─Н─Н*+Н/рН9АТНЇО(НТ─Н─Н*+Н/рН9АТНЇО'█Т─Н─Н*+Н/рН9АТНЇО&,Т─Н─Н*+Н/рН9АТНЇО$кТ─Н─Н*+Н/рН9АТНЇО#jТ─Н─Н*+Н/рН9АТНЇО" Т─Н─Н*+Н/рН9АН*+О ╘Н/рН9А Їч<ГI-Dorado Midas ManualEdward R. Fiala24 June 198357Table 13B: MemC DMux SignalsDMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress 1120Store_InAPAIR 45 1120Store_InATn ge 2 % EcHasA 1121IoStoreInA 1121IoStoreInATn ge 2 % EcHasA 1122Map_InPair' 1122Map_InPair'Tn ge 2 1123FlushInA 1123FlushInATn ge 2 % EcHasA 1124PrefetchInA 1124PrefetchInATn ge 2 % EcHasA 1125IfuRefInA 1125IfuRefInATn eq 2 % EcHasA 1126IoRefInA' 1126IoRefInA'Tn ge 2 % EcHasA 1127CacheRefInA 1127CacheRefInATn ge 2 % EcHasA 1130MapAd.0 11300 1131PrivRefInPair 1131PrivRefInPairTn ge 2 1132VicInPair' 1132VicInPair'Tn ge 2 sometimes 1133FSinPair' 1133FSinPair'Tn ge 2 sometimes 1134bEcHasA 1134bEcHasATn ge 2 1135KillIfuRef 1135KillIfuRefAlways 1136_PrVArow 1136_PrVArowTn eq 2 1137PairFull' 1137PairFull'Tn ge 21140:1143PipeAd.0 to 3PIPEAD 461140:1143PipeAd.0 to 3Tn eq 21144:1145CacheConfig[0:1]1144:1145CacheConfig[0:1]Never1146:1147PageConfig[0:1]1146:1147PageConfig[0:1]Never1150:1157--1150:1157--MCR 57 3760dVA_VicNever 3761ForceDirtyMissNever 3762UseMcrVNever3763:3764Victim[0:1]Never3765:3766NextV[0:1]Never 3767DisBRNever 3770DisCflagsNever 3771DisHoldNever 3772NoRefNever3773:37740 3775WakeOnCLNever 3776ReportSE'Never 3777NoWakeupsNeverAAD1613660:366303664:3673Aad.0a to 7aNever3674:36770MEMB1623700:371203713:3717MemB.0 to 5NeverЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpН┐ОbsТ▓НЇО^РtН─НН#ЬН*+Н/рН9А НЇО]▓Н─НН#ЬН*+Н/рН9АНЇО\1НН#ЬН*+НЇОY)uТ─Н─НН$лН*+Н/рН9АТ НЇОWхТ─Н─ Н*+Н/р Н9АТ НЇОVgТ─Н─ Н*+Н/р Н9АТНЇОUТ─Н─Н*+Н/рН9АТ НЇОSіТ─Н─ Н*+Н/р Н9АТ НЇОREТ─Н─Н*+Н/рН9АТ НЇОPДТ─Н─Н*+Н/рН9АТ НЇОO┐Т─Н─ Н*+Н/р Н9АТ НЇОN#Т─Н─Н*+Н/рНЇОLбН─Н*+Н/рН9АТНЇОKaТ─Н─ Н*+Н/р Н9АТНЇОJТ─Н─Н*+Н/рН9АТНЇОH÷Т─Н─Н*+Н/рН9АТНЇОG?Т─Н─ Н*+Н/р Н9АНЇОEчН─Н*+Н/рН9АТНЇОD}Т─Н─Н*+Н/рН9АТНЇОA╪Н─Т─НН$лН*+Н/рН9АТНЇО@[Н─Н*+Н/рН9АНЇО>ЗН─Н*+Н/рН9АНЇО=≥Н─Н*+Н/рНО:ьН$лТ─Н*+Н/рН9АН*+О9wН/р Н9АН*+О8Н/рН9АН*+О6╣Н/р Н9АН*+О5UН/р Н9АН*+О3ТН/рН9АН*+О2⌠Н/рН9АН*+О12Н/рН9АН*+О/яН/рН9АН*+О.qН/рН*+О-Н/рН9АН*+О+╞Н/рН9АН*+О*NН/рН9АНО'█Н$лН*+Н/рН*+О&,Н/рН9АН*+О$кН/рНО" Н$лН*+Н/рН*+О ╘Н/р Н9АxЇч9щI-УDorado Midas ManualEdward R. Fiala24 June 198358Table 14A: MemD DMux SignalsDMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress 1200SinD.00MEMD0 50 1200SinD.00Never 1201CD.00 1201CD.00Never 1202D0in.00 1202D0in.00 1203D1in.00 1203D1in.00 1204EcSout.00' 1204EcSout.00' 1205EcInD.01205:12060 1206Dbuf_' 1207-- 1207-- 1210D.00 1210D.00 1211dMD.00 1211dMD.00 1212D1BCE'c 1212Fout.00 1213WriteD1'd1213:12170 1214DontWriteMDM1215:1217Dad1.10b to 12b 1220D0BCE'c1221:1222Dad.00f to 01fDAD 511220:1221Dad.00f to 01f1223:1231Dad.02'c to 08'c1222:1230Dad.02'c to 08'c 1232Dad.09' 1231Dad.09'1233:1235Dad0.10c to 12c1232:1234Dad0.10c to 12c 1236D0ACE'c1235:1237Dad1.10b to 12b 1237WriteD0'e 1240F_DFD 52 1240F_DTn ge 2 1241D_Dbuf 1241D_DbufTn ge 1 1242Sout_D 1242Sout_DTn ge 1 1243Fout_D 1243Fout_DTn ge 1 1244D_CD 1244D_CDTn ge 1 1245Md_D 1245Md_DTn ge 1 1246MakeMDM_D' 1246MakeMDM_D'Always 1247bFastD_Dbuf 1247bFastD_DbufAlways 1250Fout.00 1250Dbuf_'Tn ge 1 1251DadH_' 1251DadH_'Tn ge 2 1252DontLoad1 1252DontLoad1Always 1253GenPh1 1253GenPh1Tn ge 2 & EnEcGen1254:1257-- 1254DontWriteMDMTn eq 21255:1257--ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНsОbsТ▓НЇО^РtН─НН#ЬН*+Н/рН9А НЇО]▓Н─НН#ЬН*+Н/рН9АНЇО\1НН#ЬН*+НЇОY)uТ─Н─НН$лН*+Н/рН9АНЇОWхН─Н*+Н/рН9АНЇОVgН─Н*+Н/рНЇОUН─Н*+Н/рНЇОSіН─ Н*+Н/р НЇОREН─Н*+Н/рНЇОPДН─НЇОO┐Н─Н*+Н/рНЇОN#Н─Н*+Н/рНЇОLбН─Н*+Н/рНЇОKaН─Н*+Н/рНЇОJН─Н*+Н/рНЇОH÷Н─НЇОG?Н─ТНЇОD}Т─Н─НЇОCН─ НН$лН*+Н/рТ НЇОA╪Н─Т─Н*+Н/рТНЇО@[Т─Н─Н*+Н/рНЇО>ЗН─Н*+Н/рТНЇО=≥Т─Н─Н*+Н/рТНЇО<8Т─Н─НЇО9wН─НН$лН*+Н/рН9АТНЇО8Т─Н─Н*+Н/рН9АТНЇО6╣Т─Н─Н*+Н/рН9АТНЇО5UТ─Н─Н*+Н/рН9АТНЇО3ТТ─Н─Н*+Н/рН9АТНЇО2⌠Т─Н─Н*+Н/рН9АТНЇО12Т─Н─ Н*+Н/р Н9АНЇО/яН─ Н*+Н/р Н9АНЇО.qН─Н*+Н/рН9АТНЇО-Т─Н─Н*+Н/рН9АТНЇО+╞Т─Н─Н*+Н/рН9АНЇО*NН─Н*+Н/рН9АТНЇО(НН─Н*+Т─Н/рН9АТН*+О'█Н/р╟Ї%б:∙BIшDorado Midas ManualEdward R. Fiala24 June 198359Table 14B: MemD DMux SignalsDMuxSignalMidasMidasMidasSignalSimulationAddressNameWordWordDMuxNameCondition(Octal)NameNumberAddress1260:1263MDMad.0' to 3'EC 531260:12630 1264StartEcChk' 1264StartEcChk'Always 1265StartEcGen' 1265StartEcGen'Always 1266D1ACE'c 12660 1267-- 1270EcInD.11267:1270EcInD.0 to 1Never 1271WordInError' 1271WordInError'When DisableEc true 1272DisableEc' 1272DisableEc'Never** 1273ChkPh1 1273ChkPh1Tn ge 2 & preEcEn 1274ChkPh4' 1274ChkPH4' 1275ChkLastPh6' 1275ChkLastPh6' 1276DoubleError' 1276DoubleError' 1277ChkErrEn' 1277ChkErrEn'1300:1306tSyn0 to 6TSYN 541300:1306tSyn0 to 6 1307tSyn7x 1307tSyn7x1310:1317--1310:1317--MDMAD 553540:355303554:3557MDMad.0' to 3'Tn ge 2DADE 56 3560D0ACE'cTwo chip enables always 3561D0BCE'cpredicted false, other two 3562D1ACE'cif (T1Transport & (Tn ge 2)) 3563D1BCE'c 3564WriteD0'eTn ge 2 3565WriteD1'dTn ge 13566:35770ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНsОbsТ▓НЇО^РtН─НН#ЬН*+Н/рН9А НЇО]▓Н─НН#ЬН*+Н/рН9АНЇО\1НН#ЬН*+НЇОY)uН─Т─ НН$лН*+Н/рНЇОWхН─ Н*+Н/р Н9АНЇОVgН─ Н*+Н/р Н9АНЇОUН─Н*+Н/рНЇОSіН─НЇОREН─Н*+Н/рН9АНЇОPДН─Н*+Н/рН9АТНЇОO┐Т─Н─ Н*+Н/р Н9АНЇОN#Н─Н*+Н/рН9АТНЇОLбТ─Н─Н*+Н/рНЇОKaН─ Н*+Н/р НЇОJН─Н*+Н/рНЇОH÷Н─Н*+Н/рНЇОEчН─ НН$лН*+Н/рТ НЇОD}Т─Н─Н*+Н/рНЇОCН─Н*+Н/рНО@[Н$лН*+Н/рН*+О>ЗН/р Н9АТНО<8Н$лТ─Н*+Н/рН9АТН*+О:ьТ─Н/рН9АТН*+О9wТ─Н/рН9АТ░Т▒Н*+О8Т─Н/рН*+О6╣Н/рН9АТН*+О5UТ─Н/рН9АТН*+О3ТН/рЪ╨Ї2)<Г5БXDorado Midas ManualEdward R. Fiala24 June 198360Table 15A: MemX DMux Signals* = moved elsewhere (ProcSrn[0:3] and 3 bits for Mcr_ are moved)MidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberMAPBUF601400:1417Mapbuf[0:15]Tn ge 2P34INEC611420:1421Mapbuf.16 to 17Tn ge 2 1422ProcTagInATn ge 2 1423PrivRefInPairAlways1424:1427Pipe34Ad.0 to 3Tn ge 2 1430WPinEc1Tn ge 2 1431MapTroubleInEc1Tn ge 2 1432TagInEc2Never 1433CacheRefInEc2Never 1434Store_InEc2'Never 1435IFURefInEc2Never 1436MapPEInEc2Never 1437MapTroubleInEc2Tn ge 2MCDTSK621440:1443MDMtagAd.0 to 3Always1444:1447CurTask.0 to 3Always 1450ProcTagAlways 1451MDMtag'If CacheRefInPair & (Atask eq CurTask) 1452At=Curt'Always 1453Dt=Curt'Always1454:1457Dtask[0:3]NeverSTA63 1460VictimInSTTn ge 2 1461STIdle'Always 1462StartSTAlways 1463STWait-Mem'Tn ge 21464:1467STState[0:3]Tn ge 2 1470STfree'Tn ge 2 1471VictimInAAlways 1472MapRfshDlyTn ge 1 1473RefUsesDInEc1Tn ge 2 & StartEc1 1474AWordRefToDAlways 1475MapWantsPipeTn ge 2 1476MapFreeTn ge 2 1477UseAsrnTn ge 2APESRN641500:1503Asrn.0 to 3Tn ge 21504:1507ProcSrn.0 to 3Tn ge 2 1510MapIs16KNever 1511MapIs64KNever 1512MapIs256KNever 1513RfshAd.0Never1514:1517Ec2Srn[0:3]Tn ge 2НЇОf╙pТ─Н!цqН5Т НG?ОfЯpН─ОbsТ▓НЇО^РuТП@НЇО[ЙtН:НҐН║Н+i НЇОZ┼Н:НҐН║Н+iНЇОY)Н:НЇОV!uНКНҐН║Н+iНЇОS_НКНҐН║Т─Н+iТНҐОQЧТ─Н║ Н+iТНҐОP·Т─Н║Н+iНҐОO=Н║Н+iТНҐОMэТ─Н║Н+iТНҐОL{Т─Н║Н+iТНҐОKТ─Н║Н+iНҐОI╨Н║Н+iНҐОHYН║Н+iНҐОFЬН║ Н+iНҐОE≈Н║ Н+iНҐОD7Н║Н+iТНЇОAuНКНҐН║Т─Н+iНҐО@Н║ Н+iНҐО>ЁН║Н+iНҐО=SН║Н+iТП&НҐО;РТ─Н║Н+iНҐО:▒Н║Н+iНҐО90Н║ Н+iНЇО6oНКНҐН║ Н+iТНҐО5Т─Н║Н+iНҐО3ґН║Н+iНҐО2LН║ Н+iТНҐО0ЛН║Н+iНҐО/▀Т─Н║Н+iТНҐО.*Т─Н║Н+iНҐО,иН║ Н+iТНҐО+iТ─Н║Н+iТНҐО*Т─Н║ Н+iНҐО(їН║Н+iТНҐО'FТ─Н║Н+iТНҐО%ЕТ─Н║Н+iТНЇО#$НКНҐН║Т─ Н+iТНҐО!цН║Т─ Н+iТНҐО bТ─Н║Н+iНҐОН║Н+iНҐО║Н║Н+iНҐО@Н║Н+iНҐОъН║ Н+iТЪйЇ6└NВаDorado Midas ManualEdward R. Fiala24 June 198361Table 15B: MemX DMux Signals* = moved elsewhere (3 bits for Mcr_ are moved)MidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberSTOUT65 1520LoadEn'Never 1521EcLoadEn'Never 1522ShiftEn'Tn ge 2 1523EnEcGen'Tn ge 2 1524MapWait-ST'Tn ge 2 1525STPerrNow'Never 1526EnableAllModsNever 1527StartEc1Never 1530PairFullAlways 1531TransportaAlways 1532EcFault'Never 1533MemError'Never 1534-- 1535ChipsAre256/16KNever 1536ChipsAre64KNever 1537VicSTPerr-.NeverTAGAT66 1540MemColSelaNever 1541EcHasATn ge 2 1542PtagNever 1543MapWait-Ec2Tn ge 2 1544Dtag'Tn ge 2 1545sHoldAlways 1546MapWait-MemState'Always 1547MapRfshAlways 1550AcanHaveDTn ge 2 1551CacheRefInPair'Tn ge 2 1552EcWordRefToDAlways 1553ChkLastPh6Tn ge 21554:1557Atask.0 to .3Tn ge 2MEMST67 1560MapWait-MemDNever 1561MapWait-MemIOAlways 1562MemIdle'Always 1563MemFreeTn ge 21564:1567MemState.0 to 3Tn ge 2 1570FinNextTn ge 2 1571MemRfshTn ge 2 1572StopFinTaskLoadTn ge 2 1573DdataGood'Tn ge 2 1574MakeSout_DTn ge 21575:1577MakeTransport[0:2]Never**--701600:1607--НЇОf╙pТ─Н!цqН5Т НG?ОfЯpН─ОbsТ▓НЇО^РuТП/НЇО[ЙtН:НҐН║Н+i НЇОZ┼Н:НҐН║Н+iНЇОY)Н:НЇОV!uНКНҐТ─Н║Н+iНҐОTюН║Н+iНҐОS_Н║Н+iТНҐОQЧТ─Н║Н+iТНҐОP·Т─Н║ Н+iТНҐОO=Т─Н║ Н+iНҐОMэН║Н+iНҐОL{Н║Н+iНҐОKН║Н+iНҐОI╨Н║ Н+iНҐОHYН║Н+iНҐОFЬН║Н+iНҐОE≈Н║НҐОD7Н║Н+iНҐОBжН║ Н+iНҐОAuН║ Н+iНЇО>ЁНКНҐН║ Н+iНҐО=SН║Н+iТНҐО;РТ─Н║Н+iНҐО:▒Н║ Н+iТНҐО90Т─Н║Н+iТНҐО7пТ─Н║Н+iНҐО6oН║Н+iНҐО5Н║Н+iНҐО3ґН║Н+iТНҐО2LТ─Н║Н+iТНҐО0ЛТ─Н║Н+iНҐО/▀Н║ Н+iТНҐО.*Н║Т─Н+iТНЇО+iНКНҐТ─Н║Н+iНҐО*Н║Н+iНҐО(їН║Н+iНҐО'FН║Н+iТНҐО%ЕН║Т─Н+iТНҐО$┘Т─Н║Н+iТНҐО#$Т─Н║Н+iТНҐО!цТ─Н║Н+iТНҐО bТ─Н║ Н+iТНҐОТ─Н║ Н+iТНҐО║Н║Н+iНЇОъНКНҐН║VЇ2ANВҐDorado Midas ManualEdward R. Fiala24 June 198362Table 15C: MemX DMux Signals* = moved elsewhere (ProcSrn[0:3] and 3 bits for Mcr_ are moved)MidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberFLTMEM71* 1620WakeOnCL* 1621ReportSE'* 1622NoWakeups 1623ProcSrn_'Tn ge 1 1624FaultsNever 1625LoadFltSrnIf independent of FaultSrn eq 0 1626ReportFaultAlways 1627MapPEInMemNever 1630MapTroubleInMemNever 1631RfshInMemTn ge 2 1632WriteInMem'Tn ge 2 1633MemWPNever 1634IOFetchInMem'Tn ge 2 1635RefUsesD10InMem'Tn ge 2 1636RefUsesDInMemTn ge 2 1637DirtyIOFetchInMemTn ge 2RFSSRN72 1640STPerrNever 1641MapPerrNever 1642HitPerrNever 1643WantRfshTn ge 2 1644NeedRfshAlways 1645StartMemaTn ge 2 1646StkWakeNever 1647_FaultInfoDly'Never1650:1653MapSrn.0 to 3Tn ge 2654:1657MemSrn.0 to 3Tn ge 2EC1MAKE73 1660StartEc2'Tn ge 2 1661Ec1Free'Tn ge 2 1662Ec1IdleAlways1663:1664Ec1Func.0 to 1Tn ge 21665:1667Ec1State.0 to 2Tn ge 2 1670EcWantsAaTn ge 2 1671FoutNextTn ge 2 usually 1672MakeFout_DTn ge 2 usually 1673MakeD_CDTn ge 2 usually 1674MakeD_DbufAlways 1675MakeF_DAlways 1676MakeMD_DAlways 1677MakeMDM_D'Tn ge 2MAPCTRL741700:1701MapbufHi.0 to 1Never 1702MapRAS'Tn ge 2 when forced high 1703MapCAS'Tn ge 2 when forced high 1704MapWE'Tn ge 2 % StartMap 1705RefWE'Tn ge 2 1706DirtyWE'Tn ge 2 % StartMap 17070 1710MapWaitAlways 1711WantMapWait'Always 1712ValidMapFltInEc2'Tn ge 21713:1714MapFnc.0' to 1'Tn ge 21715:1717MapState.0 to 2Tn ge 2НЇОf╙pТ─Н!цqН5Т НG?ОfЯpН─ОbsТ▓НЇО^РuТП@НЇО[ЙtН:НҐН║Н+i НЇОZ┼Н:НҐН║Н+iНЇОY)Н:НЇОV!uНКНҐТ─Н║НҐОTюН║НҐОS_Н║НҐОQЧН║Н+iТНҐОP·Т─Н║Н+iНҐОO=Н║ Н+iТНҐОMэТ─Н║ Н+iНҐОL{Н║ Н+iНҐОKН║Н+iНҐОI╨Н║Н+iТНҐОHYТ─Н║ Н+iТНҐОFЬТ─Н║Н+iНҐОE≈Н║Н+iТНҐОD7Т─Н║Н+iТНҐОBжТ─Н║Н+iТНҐОAuТ─Н║Н+iТНЇО>ЁНКНҐТ─Н║Н+iНҐО=SН║Н+iНҐО;РН║Н+iНҐО:▒Н║Н+iТНҐО90Т─Н║Н+iНҐО7пН║Н+iТНҐО6oТ─Н║Н+iНҐО5Н║ Н+iНҐО3ґН║Н+iТНҐО2LН║Т─Н+iТНЇО/▀НКНҐТ─Н║Н+iТНҐО.*Т─Н║Н+iТНҐО,иТ─Н║Н+iНҐО+iН║ Н+iТНҐО*Н║Т─Н+iТНҐО(їТ─Н║Н+iТНҐО'FТ─Н║Н+iТНҐО%ЕТ─Н║ Н+iТНҐО$┘Т─Н║Н+iТНҐО#$Т─Н║ Н+iНҐО!цН║Н+iНҐО bН║Н+iНҐОН║ Н+iТНЇО@НКНҐН║Т─Н+iНҐОъН║Н+iТНҐО~Т─Н║Н+iТНҐОТ─Н║Н+iТНҐОҐТ─Н║Н+iТНҐО\Т─Н║Н+iТНҐОШТ─Н║НҐО⌡Н║Н+iНҐО:Н║Н+iНҐОыН║Н+iТНҐОxН║Т─Н+iТНҐО Н║Т─Н+iТЪдЇL2A\©,Dorado Midas ManualEdward R. Fiala24 June 198363Table 15D: MemX DMux Signals* = moved elsewhere (ProcSrn[0:3] and 3 bits for Mcr_ are moved)MidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberPEEC751720:1723PEsrn.0 to 3Always1724:1727Ec1Srn.0 to 3Tn ge 2 1730CacheLoad'Always 1731Ec2FreeTn ge 2 1732Ec2IdleAlways1733:1734Ec2Func.0 to 1Tn ge 21735:1737Ec2State.0 to 2Tn ge 2INMAP76 1740RefUsesDInMap'DirtyIOFetchInMap % ((Tn ge 2) & StartMap) 1741RefUsesD10InMap'Tn ge 2 1742DirtyIOFetchInMap'Never 1743WriteInMap'Tn ge 2 1744IOFetchInMap'Tn ge 2 1745_MapInMapNever 1746Store_InMap'Tn ge 2 1747EcWantsPipe4'Tn ge 21750:1757--НЇОf╙pТ─Н!цqН5Т НG?ОfЯpНpОbsТ▓НЇО^РuТП@НЇО[ЙtН:НҐН║Н+i НЇОZ┼Н:НҐН║Н+iНЇОY)Н:НЇОV!uНКНҐН║Т─Н+iНҐОTюН║Н+iТНҐОS_Т─Н║ Н+iНҐОQЧН║Н+iТНҐОP·Т─Н║Н+iНҐОO=Н║ Н+iТНҐОMэН║Т─Н+iТНЇОKНКНҐТ─Н║ Н+iТНҐОI╨Т─Н║Н+iТНҐОHYТ─Н║Н+iНҐОFЬН║ Н+iТНҐОE≈Т─Н║Н+iТНҐОD7Т─Н║Н+iНҐОBжН║Н+iТНҐОAuТ─Н║Н+iТНҐО@Н║Ъ▄Ї>I9З)бДDorado Midas ManualEdward R. Fiala24 June 198364Table 16: Disk Controller DMux SignalsMidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberKSTATE100 20000 2001IndexTW 2002SectorTW 2003SeekTagTW 2004RdFifoTW 2005WrFifoTW 2006ReadData 2007WriteData 2010EnableRun 2011DebugMode 2012RdOnlyBlock' 2013WriteBlock' 2014CheckBlock' 2015Active2016:2017Select[0:1]KSTAT101 2020SeekInc 2021HeadOvfl 2022DevCheck 2023NotSelected 2024NotOnLine 2025NotReady 2026SectorOvfl 2027FifoUnderflow 2030FifoOverflow 2031ReadDataErr 2032ReadOnly 2033CylOffset 2034IOBParityErr 2035FifoParityErr 2036WriteError 2037ReadErrorKRAM1022040:2043RamAddr[0:3]2044:2057Ram[4:15]KTAG103 2060DriveTag 2061CylinderTag 2062HeadTag 2063ControlTag 2064Tag.000 2065Tag.002066:2077Tag[0:9]KFIFO104 2100ShiftIn 2101ShiftOut 2102ComputeECC 2103NextBlock 2104LoadTag 2105CntDone' 2106OutRegFull 2107InRegFull2110:1113FifoWaddr[0:3]2114:2117FifoRaddr[0:3]ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНUОbsТ▓П'НЇО^РtН:НҐН║Н+i НЇО]▓Н:НҐН║Н+iНЇО\1Н:НЇОY)uНКНҐТ─Н║НҐОWхН║НҐОVgН║НҐОUН║НҐОSіН║НҐОREН║НҐОPДН║НҐОO┐Н║НҐОN#Н║НҐОLбН║НҐОKaН║НҐОJН║ НҐОH÷Н║ НҐОG?Н║НҐОEчН║ НЇОCНКНҐН║НҐОA╪Н║НҐО@[Н║НҐО>ЗН║ НҐО=≥Н║НҐО<8Н║НҐО:ьН║ НҐО9wН║НҐО8Н║НҐО6╣Н║ НҐО5UН║НҐО3ТН║НҐО2⌠Н║НҐО12Н║НҐО/яН║ НҐО.qН║НЇО+╞НКНҐН║НҐО*NН║НЇО'█НКНҐН║НҐО&,Н║ НҐО$кН║НҐО#jН║ НҐО" Н║НҐО ╘Н║НҐОHН║НЇО┤НКНҐН║НҐО&Н║НҐОеН║ НҐОdН║НҐОН║НҐОёН║НҐОBН║ НҐОАН║НҐО─Н║ НҐО Н║ лЇT2AYЇhDorado Midas ManualEdward R. Fiala24 June 198365Table 17: Ethernet Controller DMux SignalsMidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberERX0105 2120PDNew 2121PDOld2122:2125PDCnt[0:3] 2126PDCntCtrl 2127ReportCollisions 2130RxWakeupsOn 2131EthData.18 2132RxCRCError 2133-- 2134RxDataLate 2135RxBusRegFull 2136RxFifoFull 2137RxFifoEmptyETX1062140:2142TxState[0:2] 2143TxEOP 2144TxBusRegFull' 2145TxGone 2146TxSREmpty' 2147TxCntDwn' 2150TxCRCEnbl 2151TxGo 2152TxData2153:2154TxSRCtrl[0:1] 2155PEOutput 2156TxFifoFull 2157TxFifoEmptyERX11072160:2162RxState[0:2] 2163RxCollision 2164PDCarrier2165:2166PDEvent[0:1] 2167RxSRFull' 2170RxEOP 2171RxSync' 2172RxIncTrans 2173RxCRCReset 2174RxCRCClk 2175RxData2176:2177RxSRCtrl[0:1]НЇОf╙pТ─Н!цqН5Т НG?ОfЯpН,ОbsТ▓П+НЇО^РtН:НҐН║Н+i НЇО]▓Н:НҐН║Н+iНЇО\1Н:НЇОY)uНКНҐТ─Н║НҐОWхН║НҐОVgН║ НҐОUН║НҐОSіН║НҐОREН║ НҐОPДН║ НҐОO┐Н║ НҐОN#Н║НҐОLбН║ НҐОKaН║НҐОJН║ НҐОH÷Н║ НЇОEчНКНҐН║НҐОD}Н║НҐОCН║НҐОA╪Н║НҐО@[Н║ НҐО>ЗН║НҐО=≥Н║НҐО<8Н║НҐО:ьН║НҐО9wН║НҐО8Н║НҐО6╣Н║ НҐО5UН║ НЇО2⌠НКНҐН║НҐО12Н║ НҐО/яН║НҐО.qН║НҐО-Н║НҐО+╞Н║НҐО*NН║НҐО(НН║ НҐО'█Н║ НҐО&,Н║НҐО$кН║НҐО#jН║Ї!÷2AFlDorado Midas ManualEdward R. Fiala24 June 198366Table 18A: IFU DMux SignalsMidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberMEMRQ1202400:2407PcF[8:15]Tn eq 2 & Testing' 2410NewFTn eq 2 & Testing' 2411KillResponseTn ge 1 & Testing' 2412PauseTn ge 2 & Testing' unless IFUM write 2413RefOutstandingNever 2414IncPcFNever 2415IncPcFG'Always 2416WantIfuRef'Always 2417ThreeOutOfFiveAlwaysLOADS121 2420ValidRamAlways 2421J_OddFAlways 2422RealPcFG.15Tn eq 2 & Testing' unless IFUM write 2423FDvTn eq 2 & Testing' unless IFUM write 2424GDvTn eq 2 & Testing' unless IFUM write 2425HDvTn eq 2 & Testing' unless IFUM write 2426JDvTn eq 2 & Testing' unless IFUM write 2427MDv'Tn eq 2 & Testing' unless IFUM write 2430EnableFG'Always 2431XLdAlways 2432AlphaXLdAlways 2433BrkLdTn ne 1 2434MLdAlways 2435InstrAddrLdTn ge 2 2436JLdaAlways 2437GLd'AlwaysHJ1222440:2447H[0:7]Never2450:2457J[0:7]bTn ge 2 & Testing' unless IFUM write when no clock oron J_H the 1's are checkedMX123 2460TwoAlphaXTn ge 2 & Testing' 2461JFaultTn ge 2 & Testing' unless IFUM write 2462HFault'Tn eq 2 & Testing' 2463NM=17Tn ge 2 & Testing' 2464TwoAlphaMTn ge 2 & Testing' 2465TypeJumpM'Tn ge 2 & Testing'2466:2467LengthM[0:1]Tn ge 2 & Testing'2470:2471DSel[0:1]Tn ge 2 & Testing' unless XShift with DSel eq 02472:2473LengthX[0:1]Tn ge 2 & Testing'2474:2477NX[0:3]Tn ge 2 & Testing' when unclocked or NM eq 17ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpН QОbsТ▓НЇО^РtН:НҐН║Н+i НЇО]▓Н:НҐН║Н+iНЇО\1Н:НЇОY)uНКНҐН║Н+iТНҐОWхТ─Н║Н+iТНҐОVgТ─Н║Н+iТНҐОUТ─Н║Н+iТП"НҐОSіТ─Н║ Н+iНҐОREН║Н+iНҐОPДН║Н+iНҐОO┐Н║ Н+iНҐОN#Н║ Н+iНЇОKaНКНҐН║Н+iНҐОJН║Н+iНҐОH÷Н║ Н+iТП$НҐОG?Т─Н║Н+iТП"НҐОEчТ─Н║Н+iТП"НҐОD}Т─Н║Н+iТП"НҐОCТ─Н║Н+iТП"НҐОA╪Т─Н║Н+iТП"НҐО@[Т─Н║Н+iНҐО>ЗН║Н+iНҐО=≥Н║Н+iНҐО<8Н║Н+iТНҐО:ьТ─Н║Н+iНҐО9wН║ Н+iТНҐО8Т─Н║Н+iНҐО6╣Н║Н+iНЇО3ТНКНҐН║Н+iНҐО2⌠Н║Н+iТ▌Т▐П0Н+iО12ТНЇО.qНКНҐТ─Н║Н+iТНҐО-Т─Н║Н+iТП"НҐО+╞Т─Н║Н+iТНҐО*NТ─Н║Н+iТНҐО(НТ─Н║Н+iТНҐО'█Т─Н║ Н+iТНҐО&,Н║Н+iНҐО$кН║Н+iТУП%ТЖ НҐО#jН║Н+iТНҐО" Н║Н+iТХТИП(┼Ї ?<ГGл╦Dorado Midas ManualEdward R. Fiala24 June 198367Table 18B: IFU DMux SignalsMidasMidasDMuxSignalSimulationWordWordAddressNameConditionNameNumberJMPEXC124 2500ExceptionAlways 2501SayNotReadyAlways 2502WantReschedTn ge 2 & Testing' 2503SawRamParityErrOnly during Reset 2504SawFGParityErrOnly during Reset or when testing 2505ReschedPendingTn ge 2 & Testing' 2506KReadyAlways 2507-- 2510ZapFGHAlways 2511ZapJAlways 2512NewJTn ge 2 & Testing' unless IFUM write 2513DoJumpTn ge 2 & Testing' unless IFUM write 2514TurnOffAluTn even 2515NewGoAlways 2516BMuxEnableTn even 2517FGFaultNeverPCJ1252520:2527PcJ[8:15]Tn eq 2 & Testing' unless IFUM write 2530MLdDly'Tn ge 2 & Testing' 2531BetaInMTn ge 2 & Testing' 2532FGErrDlyTn ge 2 2533RamErrDlyTn ge 12534:2535InstrSetNever** 2536OneByteJumpInJTn ge 2 & Testing' 2537OneByteJumpInJdTn ge 2 & Testing'FFK126 2540Test_Tn ge 1 2541GenOut_'Tn ge 1 2542NewPC_Tn ge 2 & Testing' 2543IfuResetTn ge 2 2544BrkIns_Tn ge 2 & Testing' 2545TestingTn ge 2 2546SignX'Never 2547BrkPendingTn eq 2 & Testing'2550:2552-- 2553TypeJumpK'Never 2554TypePauseK'Never2555:2556LengthK[0:1]Never 2557SignKNeverНЇОf╙pТ─Н!цqН5Т НG?ОfЯpН QОbsТ▓НЇО^РtН:НҐН║Н+i НЇО]▓Н:НҐН║Н+iНЇО\1Н:НЇОY)uНКНҐТ─Н║Н+iНҐОWхН║ Н+iНҐОVgН║ Н+iТНҐОUТ─Н║Н+iТНҐОSіТ─Н║ Н+iТНҐОREТ─Н║ Н+iТНҐОPДТ─Н║Н+iНҐОO┐Н║НҐОN#Н║Н+iНҐОLбН║Н+iНҐОKaН║Н+iТП$НҐОJТ─Н║Н+iТП"НҐОH÷Т─Н║ Н+iТНҐОG?Т─Н║Н+iНҐОEчН║ Н+iТНҐОD}Т─Н║Н+iНЇОA╪НКНҐН║Н+iТП$НҐО@[Т─Н║Н+iТНҐО>ЗТ─Н║Н+iТНҐО=≥Т─Н║Н+iТНҐО<8Т─Н║Н+iТНҐО:ьН║Н+iНҐО9wТ─Н║ Н+iТНҐО8Т─Н║Н+iТНЇО5UНКНҐТ─Н║Н+iТНҐО3ТТ─Н║Н+iТНҐО2⌠Т─Н║Н+iТНҐО12Т─Н║Н+iТНҐО/яТ─Н║Н+iТНҐО.qТ─Н║Н+iТНҐО-Т─Н║Н+iНҐО+╞Н║ Н+iТНҐО*NН║НҐО(НТ─Н║ Н+iНҐО'█Н║ Н+iНҐО&,Н║Н+iНҐО$кН║Н+i└Ї#6╙E╙Dorado Midas ManualEdward R. Fiala24 June 198368Table 19: Display Controller DMux SignalsMidasMidasMidasSignalSimulationWordWordDMuxNameConditionNameNumberAddressAPTRS140 3000ACurrentWCBFlagNever3001:3007AReaderPtr.1 to 7Never 3010ANextWCBFlagNever3011:3017AWriterPtr.1 to 7NeverBPTRS141 3020BCurrentWCBFlagNever3021:3027BReaderPtr.1 to 7Never 3030BNextWCBFlagNever3031:3037BWriterPtr.1 to 7NeverITEMS1423040:3047AItem.0 to 7Never3050:3057BItem.0 to 7NeverSPSIZE1433060:3063AServicePtr.1 to 4Never3064:3067BServicePtr.1 to 4Never 3070AFifoFullNever 3071BFifoFullNever 3072ASize8Never 3073ASize8-4Never 3074ASize8-4-2Never 3075BSize8Never 3076BSize8-4Never 3077BSize8-4-2NeverRESON144 3100AOnNever 3102BOnNever3103:3104ARes.0 to 1Never3105:3106BRes.0 to 1Never 3107OISRcvdDataNever3110:3117--ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpН{ОbsТ▓П*НЇО^РtН:НҐН║Н+i НЇО]▓Н:НҐН║Н+iНЇО\1Н:НҐНЇОY)uНКНҐТ─Н║Н+iНҐОWхН║Н+iНҐОVgН║Н+iНҐОUН║Н+iНЇОREНКНҐН║Н+iНҐОPДН║Н+iНҐОO┐Н║Н+iНҐОN#Н║Н+iНЇОKaНКНҐН║Н+iНҐОJН║Н+iНЇОG?НКНҐН║Н+iНҐОEчН║Н+iНҐОD}Н║Н+iНҐОCН║Н+iНҐОA╪Н║Н+iНҐО@[Н║Н+iНҐО>ЗН║ Н+iНҐО=≥Н║Н+iНҐО<8Н║Н+iНҐО:ьН║ Н+iНЇО8НКНҐН║Н+iНҐО6╣Н║Н+iНҐО5UН║ Н+iНҐО3ТН║ Н+iНҐО2⌠Н║ Н+iНҐО12Н║(Ї/g2A8єDorado Midas ManualEdward R. Fiala24 June 198369Table 20: Other DMux Stuff* BMUX and ESTAT signals are obtained from the four-bit slice readout. The temperature sensing signals are movedfrom the position in which the hardware reads them out.MidasMidasMidasSignalSimulationWordWordDMuxNameConditionNameNumberAddressTEMP160 3500CBTempNever 3501BaseTempNever 3502ProcHTempNever 3503ProcLTempNever 3504IFUTempNever 3505DskEthTempNever3506:3517--BMUX163 --BMux[0:17]if driven from ALUBESTAT164 4020PEIMrh 4021PEIMlh 4022MdPE 4023RAMPEen 4024IOBPE 4025RAMPE 4026MemPE 4027MemPEen 4030CIMPErh 4031CIMPElh 4032Stopped 4033MdPEen 4034IMrhPEen 4035IMlhPEen 4036IOBPEen 4037MIRDebugenНЇОf╙pТ─Н!цqН5Т НG?ОfЯpН ШОbsТ▓НЇО^РuТ≈Т≤ПYНЇО]▓ТП7НЇОZ┼tН:НҐН║Н+i НЇОY)Н:НҐН║Н+iНЇОWхН:НҐНЇОTюuНКНҐТ─Н║Н+iНҐОS_Н║Н+iНҐОQЧН║Н+iНҐОP·Н║Н+iНҐОO=Н║Н+iНҐОMэН║ Н+iНҐОL{Н║НЇОI╨НКНҐН║ Н+iТНЇОFЬНКНҐТ─Н║НҐОE≈Н║НҐОD7Н║НҐОBжН║НҐОAuН║НҐО@Н║НҐО>ЁН║НҐО=SН║НҐО;РН║НҐО:▒Н║НҐО90Н║НҐО7пН║НҐО6oН║НҐО5Н║НҐО3ґН║НҐО2LН║ ╨Ї2)=Г5БЯDorado Midas ManualEdward R. Fiala24 June 19837042. Hardware Read/Write Methods This section discusses the methods Midas uses to read and write each register and memory, so thatfailing data paths can be identified when Midas reports problems via "Test" or "TestAll". Thesesequences are included to help maintainers determine what registers or data paths might bemalfunctioning when something is found to be non-working.To understand how the sequences given below communicate information between Midas and theDorado, you have to understand the lowest-level communication protocols which are discussed in"Dorado Debugging Interface" ([Indigo]DoradoDebugging.press). These primitivesare outlined here:DoradoOutStoring into DoradoOut sends 13d bits of control information over the printerinterface to the (connected) Dorado. This information is interpreted by thereceiving hardware as a 3-bit address field, 9-bit data field, and 1-bit strobe.StrobeA strobe operation consists of 3 DoradoOut's identical except for the strobe bit,which is first off, then on, then off again. Strobe sequences are used to sendcommands to the Dorado.Load ClockA register internal to the communication interface that can be loaded with onestrobe operation.Load ControlAnother register internal to the communication interface that can be loaded withone strobe operation.Load MIRMIR can be loaded by four strobe operations, each loading 9 bits of themicroinstruction. Midas computes and sends the parity also.Load CPRegTwo strobe operations load the 16d-bit CPReg, the register from which Midasusually sends data to the Dorado.Xct(mic)A microinstruction can be executed by loading it into MIR and single-stepping theDorado. To get data from Midas to the Dorado, Midas first loads CPReg withdata, then executes a microinstruction which does "Q _ Link" or "T _ Link", forexample, while the UseCPReg bit in the Clock register is true. This kind ofsequence is denoted by "Q _ CPReg(data)" below, which means that the data isrouted from CPReg through the multiplexor on the ContA board to the Q or Tregister. The fact that the B data path is used is not explicitly stated in themicroinstruction, but B is the only possible data path; this implicit use of data pathsin the examples below is consistent with the conventions of the microprogramminglanguage.Also, a function called "B _ RWCPReg", solely for use by Midas and thebaseboard microcomputer is used to do "Link _ B _ CPReg(data)". This functionis needed when reading and writing some registers in the control section.DoradoInReading from DoradoIn obtains 5 bits of data selected according to bits 0..4 in thelast DoradoOut operation; it is not necessary to use a strobe operation for thepurposes of DoradoIn. The fifth bit is always the current DMux bit; the first 4 bitscan be any of the 4 B nibbles, any of 4 error nibbles, either of two MAReg nibblesor the MASync bit (for communication with the baseboard microcomputer).Read BReading 16 bits of B is accomplished by a sequence of four DoradoOut/DoradoInoperations to obtain the 4 nibbles of B data. When a microinstruction is executedfor the purpose of extracting data on the B, it is written like "B* _ Q"; "*"denotes that Midas captures the B data.Read DMuxMidas has special microcode to extract all 2048d DMux signals using strobeoperations. This is done in about (32+39)/2 * 2048 * .00018 msec = 13 msec.Assembly code uses about 15 msec more appending B and ESTAT to the readout,rearranging certain signals, and computing histories.SelectTaskComplicated. See "Dorado Debugging Interface".SingleStepComplicated. See "Dorado Debugging Interface".ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНЇОaвrТ÷qТ└НЇО^eТ▓П"Т⌠П?НЇО\⌡ТєП$Т╔П<НЇОZпТНПQТОНЇОYТП9НЇОU■Т╞П+Т╟П.НЇОSиТ╙Т╚ПNНЇОQЧТ▐ПPТ░ НЇОP4ТНxОMsН░ТпП%ТяП(Н░ОK╗ТЛП9ТМН░ОJGТщП7ТчНxОHН░ТЇПLТ╦Н░ОF╡Т╩Т╪ПGН░ОEQТНxОCТ─ Н░ТаПIТбН░ОA╪ТНxО?┤Т─Н░Т╡ТЁП0Н░О>&ТНxО;РТ─Н░ТВП@ТЬН░О:▒ТП<НxО8]Т─ Н░ТпПBТяН░О6ЭТП!НxО4гН░Т∙П"Т√П/Н░О3gТ╞Т╟П,Н░О2Т√П4Т≈Н░О0╔ТхТиП-Н░О/DТїП(Т╗П$Н░О-ДТ╘П)Т╙П!Н░О,┐ТдПBТе Н░О+"Т┌П#Т┐П4Н░О)аТ ПPН░О(`Н░О&,ТДП>ТЕН░О$кТ█П+Т▌П#Н░О#jТПIНxО!6Н░Т░ПBТ▒Н░ОуТбПGТцН░ОtТ─Т│П5Н░ОТ┐ПJТ└Н░ОЁТПGНxО~Т─Н░Т≥Т ПCН░ОТ⌠Т■ПEН░ОҐТЎП:Т©Н░О\ТП'НxО(Т─Н░ТЙП%ТКН░ОгТіП"ТїП*Н░ОfТ√Т≈П+Н░ОТП5НxОя Н░П/НxО ° Н░П/ЪHЇ y=Г]▓═Dorado Midas ManualEdward R. Fiala24 June 198371RunComplicated. See "Dorado Debugging Interface".StopComplicated. See "Dorado Debugging Interface".LoadDMDExecute a "manifold" operation by loading the 11-bit DMux address with a controlfunction and then executing it.MCXctMCXct is used to communicate with the baseboard microcomputer. Midas firstloads CPReg with a command and then interrupts the microcomputer withDoStrobe(Clock+BaseBAtten); a slowed strobing sequence is used because themicrocomputer requires it. Then Midas waits for an acknowledge by doingDoradoIn's until the microcomputer responds with MASync. MCXct can be usedwhile the Dorado is running to extract voltage, current, temperature, and daytimeinformation from the baseboard microcomputer. DoradoIn can be used to get twonibbles of information from the baseboard.Each sequence below gives the microinstructions or other sequences executed by Midas to read andwrite each register and memory. These sequences do not include the shifting and masking andother transformations which occur within Midas to position data. Sequences bracketed with "[]" areused to restore registers incidentally smashed on the read or write. The restoration sequences ARENOT executed when using "Test" or "TestAll"; they ARE executed when registers or memorywords appearing in a name value menu are accessed.D1OUTWrite only. This artificial register allows the user to execute the most primitive controlfunction for the Dorado interactively.STROBEWrite only by DoStrobe(D), which is equivalent to three D1OUT's with the strobe bit first off,then on, then off again. This artificial register allows the user to send strobed commandsinteractively.CPREGRead by B* _ CPReg;[Restore MIR].Write by Midas direct handle.MIRRead from DMux.Write by Midas direct handle.IMOUTArtificial read-only register (part of DMux memory).QRead by B* _ Q;[Restore MIR].Write by Q _ CPReg(new value); Noop;[Restore MIR; read DMux].CNTRead byT _ Cnt;B* _ T;[T _ CPReg(SavedT); Noop; restore MIR].Write byQ _ CPReg(new value);Cnt _ Q;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux].SHCRead byT _ ShC;B* _ T;[T _ CPReg(SavedT); Noop; restore MIR;].Write byНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНxОbAsН░П/НxО` Н░П/НxО]ьН░Т▐П-Т░П#Н░О\wТНxОZCН░Т╩П>Т╪Н░ОXБТТП3Н░ОW│ТИП>ТЙН░ОV!ТЛП3ТМН░ОTюТ╒П+ТёН░ОS_Т╗Т╘ПHН░ОQЧТ∙Т√П>Н░ОP·ТП*НЇОMOqТ▀ПBТ▄НЇОK└Т╦П3Т╧П)НЇОI╨Т┘ПUТ├ НЇОGОТ█Т▌П\НЇОF$ТгТхП@НЇОDZТП2НЇОA.sНнТмПSТнНнО?нТП&НЇО<фНнТ├П^НнО;eТЄТ╣ПJНнО: НЇО6ЭНнТНнО5⌡ НнО2ЩНЇО/УНнНнО-VНЇО*NНнП4НЇО'FНнНнО%Е НнО#GП$НнО!ФНЇОчНнНнО}НнОНнО╪П'НнОНнОҐНнО\НнОШП2НЇОСНнНнО▓НнО2НнОяП(НнО 3┼Ї =Г]Ш"Dorado Midas ManualEdward R. Fiala24 June 198372Q _ CPReg(new value);ShC _ Q;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux].MEMBXRead byT _ Pointers;B* _ T;[T _ CPReg(SavedT); Noop; restore MIR].Write byMemBX _ S;[Restore MIR; read DMux].STKPRead byT _ TIOA&StkP;B* _ T;T _ Pointers;B* _ T;[T _ CPReg(SavedT); Noop; restore MIR]. Note that StkOvf and StkUnd are obtained fromPointers while the value in the register is obtained from TIOA&StkP.Write byQ _ CPReg(new value);StkP _ Q;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux]. StkOvf and StkUnd are read-only.TASKRead returns value saved at breakpoint.Write with SelectTask;[Restore MIR; read DMux].PROCSRNRead by B* _ Config;[Restore MIR].Write by Q _ CPReg(new value); ProcSRN _ Q;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux].MCRRead from DMux.Write byT _ CPReg(new value);MCR _ T;[T _ CPReg(SavedT); Noop; restore MIR; read DMux].The MCR register is written only when DMuxTab is selected by the "DMux" action. WritingMCR is illegal when OldDMuxTab or DWrong is selected; and DCheck is written insteadwhen DCheck is selected.CONFIGRead only byB* _ Config;[Restore MIR].PCXRead only byB* _ PCX;[Restore MIR].INSSETRead byB* _ IFUMLH';[Restore MIR].Write byQ _ CPReg(new value);InsSetOrEvent _ Q;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux].ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНнОbAsНнО`ЮНнО_─П2НЇО\wНнНнО[НнОYІНнОXUП'НнОUЇНнОTVНнОRУНЇОOМНнНнОN▄ НнОM,НнОKкНнОJjНнОI Т▓П=Т⌠НнОG╗ТПDНнОE НнОC╘НнОBIНнО@ХТ²ПEТ·НЇО=ЮНнТП'НнО;AНнО9АНЇО6ыНнНнО5x НнО2зП+НнО1yП2НЇО.qНнНнО+рНнО*rНнО)НнО'╟П2НнО&OТ┼ПGТ▀НнО$НТЇП@Т╦НнО#▌ТНЇО ├НнНнО%НнОд НЇО╪НнНнО[НнОЗ НЇОРНнНнО▒НнО1 НнО▓НнО2НнОяНнОpП2Ъ,ЇM2A\ЎЯDorado Midas ManualEdward R. Fiala24 June 198373TESTSYNWrite only bySelectTask(16B);T _ CPReg(constant);MCR _ T;Q _ CPReg(new value);Noop;Store _ T, DBuf _ Q;LoadTestSyndrome;[T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT); Noop; Q _ CPReg(SavedQ);SelectTask(SavedTask); restore MIR; read DMux].UPTIMEArtificial read-only register (part of ABSOL memory).TGLITCHArtificial read-only register (part of ABSOL memory).EVCNTARead only by B* _ EventCntA';[Restore MIR].EVCNTBRead by B* _ EventCntB';[Restore MIR].Write byQ _ CPReg(new value);EventCntB _ Q;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux].AATOVAArtificial register.ESTATActually read by Midas direct handle but treated as part of the DMux memory. This is aregister rather than simply another word in the DMux memory so that the error enables canbe written.Write error enables with LoadDMD; write MIRDebug with four LoadDMD's.ABSOLRead ABSOL by two MCXct's followed by, if the Dorado isn't running,DoStrobe(Clock+UseCPReg).Write with MCXct(constant+new value) followed by, if the Dorado isn't running,DoStrobe(Clock+UseCPReg);TPCRead from a static if address .eq. SavedTask; otherwise,RdTPC _ CPReg(address);B* _ Link;[If address .eq. SavedTask, then done; otherwise, B _ RWCPReg(SavedLink); Noop; restoreMIR].If address eq SavedTask then write static and done;otherwise, write byB _ RWCPReg(new value);LdTPC _ CPReg(address);Noop;[B _ RWCPReg(SavedLink); Noop; restore MIR; read DMux].TLINKRead bySelectTask(address);B* _ Link;[SelectTask(SavedTask); Noop; restore MIR; read DMux]Write bySelectTask(address);B _ RWCPReg(SavedLink);[SelectTask(SavedTask); Noop; restore MIR; read DMux].НЇОf╙pТ─Н!цqН5Т НG?ОfЯpНЇОbAsНнНнО`ЮНнО_─НнО^НнО\ЎНнО[]НнОYЭНнОX°НнОW;ТЎП9Т©НнОUзТП/НЇОRрНнП5НЇОOйНнП5НЇОLбНнНнОKa НЇОHYНнНнОFЬ НнОDZНнОBЫНнОA≤ НнО@7П2НЇО=/НнНЇО:'НнТїПMТ╗ НнО8фТ⌡П>Т°НнО7fТ НнО4гПEНЇО1©НнТ▒П-Т▓НнО0_НнО-юТ5П-Т6П!НнО,_НЇО)WНнТП8НнО'ВНнО&√ НнО%5Т╚Т╛П7НнО#тНнО!6ТП3НнОуН░ОtН░ОН░ОЁН░ОRП7НЇОJНнНнОИНнО┬ НнО(П5НнО┴НнО)НнО хНнОgП6pЇD=Г[гЭDorado Midas ManualEdward R. Fiala24 June 198374OLINKArtificial memory read and written like TLINK.IMBDThe setup code common to both the read and the write of IMBD first zeroes BNPC, which iswire-OR'ed with the control store address loaded by manifold operations. This is accomplishedby loading TPC for task 17B with 0 and then notifying that task; the notify causes the priorityencoder to select task 17B, so BNPC becomes equal to 0.Read bySelectTask(0);RdTPC _ CPReg(17B);B* _ Link (save old TPC(17B) for restoration later);B _ RWCPReg(0);LdTPC _ CPReg(17B);Noop;LoadMIR(Notify[17B]); single-step with Freeze off;B _ CPReg(-1);three LoadDMD's to setup the control store address;LoadDMD(constant);read DMux to get the IMOUT signals;four LoadDMD's to clear IMBD adress again;[B _ RWCPReg(SavedTPC17B); LdTPC _ CPReg(17B); Noop; B _ RWCPReg(SavedLink);SelectTask(SavedTask); DoStrobe(Clock+UseCPReg+ClrReady); DoStrobe(Clock+UseCPReg);Noop; restore MIR].Write bySelectTask(0);RdTPC _ CPReg(17B);B _ Link (UseCPReg turned off) to save TPC(17B) for later;B _ RWCPReg(0);LdTPC_ CPReg(17B);Noop;LoadMIR(Notify[17]); single-step with Freeze off;B _ CPReg(-1);three LoadDMD's to setup the control store address;four LoadDMD's to load left-half of the instruction;four LoadDMD's to load right-half of the instruction;four LoadDMD's to clear the Control register;three more LoadDMD's to something else;[B _ RWCPReg(SavedTPC17B); LdTPC _ CPReg(17B); Noop; B _ RWCPReg(SavedLink);SelectTask(SavedTask); DoStrobe(constant); DoStrobe(constant); restore MIR; read DMux;].IMArtificial form of IMX memory.IMXRead byB _ RWCPReg(address);B* _ ReadIM[0];B _ RWCPReg(address);B* _ ReadIM[1];B _ RWCPReg(address);B* _ ReadIM[2];B _ RWCPReg(address);B* _ ReadIM[3];[B _ RWCPReg(SavedLink); Noop; restore MIR].Write byB _ RWCPReg(address);IMLHR0POK _ CPReg(new value);B _ RWCPReg(address);IMRHBPOK _ CPReg(new value);[B _ RWCPReg(SavedLink); Noop; Noop; restore MIR; read DMux].ALUFMRead from static if address is 0 or 16B; otherwise, read byT _ ALUFM, ALUF[address];B* _ T;НЇОf╙pТ─Н!цqН5Т НG?ОfЯpНЇОbAsНнП.НЇО_9НнТ┼П<Т▀НнО]ьТ└П!Т┘П=НнО\wТ├П:Т┤П%НнО[ТП7НнОXxНнОW НнОUЇНнОTVП4НнОRУНнОQ■НнОP4НнОNсП2НнОMr НнОLП3НнОJ╠НнОIPП#НнОGОП*НнОF▌Т╛П.ТґНнОE-ТхП9ТиНнОCмТНнОA.НнО?н НнО>mНнО=П:НнО;╚НнО:KНнО8ЙНнО7┴П1НнО6( НнО4гП3НнО3gП4НнО2П5НнО0╔П-НнО/DП'НнО-ДТ╛П.ТґНнО,┐ТДПFТЕНЇО){НнТНЇО&sНнНнО%НнО#╠НнО"PНнО ОНнО▐НнО.НнОмНнОlНнОП,НнОmНнОНнО╛НнОKНнОЙНнО┴П=НЇО │НнП;НнО НнО юЇ ²=Г]nDorado Midas ManualEdward R. Fiala24 June 198375[T _ CPReg(SavedT); Noop; restore MIR].Write static if address is 0 or 16B; otherwise, write byQ _ CPReg(new value);ALUFMRW _ Q, ALUF[address];Noop;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux].TRead bySelectTask(address);B* _ T;[SelectTask(SavedTask); Noop; restore MIR].Write bySelectTask(address);T _ CPReg(new value);Noop;[Restore MIR; read DMux].RBASERead bySelectTask(address);T _ Pointers;B* _ T;[T _ CPReg(SavedT); SelectTask(SavedTask); Noop; restore MIR].Write bySelectTask(address);T _ CPReg(new value);Noop;[SelectTask(SavedTask); restore MIR; read DMux].TIOARead bySelectTask(Address);T _ TIOA&StkP;B* _ T;[T _ CPReg(SavedT); SelectTask(SavedTask); Noop; restore MIR].Write bySelectTask(Address);Q _ CPReg(new value);TIOA _ Q;Noop;[Q _ CPReg(SavedQ); Noop; SelectTask(SavedTask); restore MIR; read DMux].MEMBASERead bySelectTask(address);T _ Pointers;B* _ T;[T _ CPReg(SavedT); SelectTask(SavedTask); Noop; restore MIR].Write byMemBase _

S;Noop;[SelectTask(SavedTask); restore MIR; read DMux].RMRead byRBase _ S;B _ RB, RStk[lowaddress];[RBase _ S; Noop; restore MIR].Write byRBase _ S;RB _ CPReg(new value), RStk[lowaddress];Noop;[RBase _ S; restore MIR; read DMux].ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНнОbAsП'НнО`SП8НнО^РНнО]▓НнО\1НнОZпП2НЇОWхНнНнОVgНнОUНнОSіП+НнОQНнОOїНнОNFНнОLЕНнОK└НЇОH|НнНнОGНнОE╩НнОDZНнОBЫП>НнО@[НнО>ЗНнО=≥НнО<8НнО:ьП0НЇО7пНнНнО6oНнО5 НнО3ґНнО2LП>НнО/ўНнО.MНнО,МНнО+▄НнО*+НнО(йПIНЇО%бНнНнО$aНнО#НнО!═НнО ?П>НнО║НнО@НнОъНнО~П0НЇОvНнНнОНнО╣НнОTП+НнОІНнОUНнОТП(НнО⌠НнО 3П0Ї 2A]ШЙDorado Midas ManualEdward R. Fiala24 June 198376STK and STKXRead byQ _ CPReg(address);StkP _ Q;SelectTask(0);B _ RB, RStk[0], Blk[1];[SelectTask(SavedTask); Q _ CPReg(SavedStkP); StkP _ Q; Q _ CPReg(SavedQ); Noop;restore MIR].Write byQ _ CPReg(address);StkP _ Q;SelectTask(0);RB _ CPReg(new value), RStk[0], Blk[1];Noop;[Q _ CPReg(SavedStkP); StkP _ Q; Q _ CPReg(SavedQ); Noop; SelectTask(SavedTask);restore MIR; read DMux].PIPERead only byT _ CPReg(address);ProcSRN _ T;B* _ VAhi;*First screen lineB* _ VAlo;B* _ Pipe2';*Second screen lineB _ Map';B _ Errors';*Third screen lineB _ Pipe5;[T _ CPReg(SavedSRN); ProcSRN _ T; T _ CPReg(SavedT); Noop; restore MIR].BRRead byMemBase _

S;T _ CPReg(constant);MCR _ T;T _ CPReg(0);DummyRef _ T;Noop;B* _ VAhi;B* _ VAlo;[MemBase _ S; T _ CPReg(SavedSRN); ProcSRN _ T; T _CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT); SelectTask(SavedTask); Noop; restoreMIR].Write byMemBase _

S;T _ CPReg(constant);MCR _ T;T _ CPReg(highdata);BRhi _ T;T _ CPReg(lowdata);BRlo _ T;Noop;[MemBase _ S; T _ CPReg(SavedSRN); ProcSRN _ T; T _CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT); SelectTask(SavedTask); restore MIR;read DMux].For both the read and the write, the cleanup is done by a subroutine shared with othermemories. "T _ CPReg(SavedSRN); ProcSRN _ T;" and the "SelectTask(SavedTask)" areextraneous to the requirements of BR.BRXSame as BR with "MemBaseX _

S" replacing "MemBase _

S".CACHEARead bySelectTask(17B);T _ CPReg(1);ProcSRN _ T;НЇОf╙pТ─Н!цqН5Т НG?ОfЯpНЇОbAsТ─НнТНнО`ЮНнО_─НнО^ НнО\ЎНнО[]ТкП-ТлП#НнОYЭТНнОW^НнОUЩНнОT²НнОS< НнОQшП'НнОPzНнОOТкТлП5НнОM╧ТНЇОJ╠НнНнОIPНнОGОНнОF▌Т─ Н#уТНнОE- НнОCмТ─Н#уТНнОBlНнОAТ─Н#уТНнО?╙ НнО>JПIНЇО;AНнНнО9АНнО8─НнО7НнО5ЎНнО4^НнО2ЩНнО1° НнО0; НнО.зТ\П6Т]НнО-zТ╟Т╠П8НнО,НнО){ТНнО(НнО&╧НнО%XНнО#ЬНнО"≈НнО!6НнОуНнОtНнОТ\П6Т]НнОЁТ╩Т╪П:НнОRТ НнОЄТЎТ©ПNНнОSТ╠ Т╡ПHНнОРТП%НЇОЙНнТЯП<ТРНЇОБНнТНнО │НнО НнО юЬЇ ²<Г]n1Dorado Midas ManualEdward R. Fiala24 June 198377MemBase _ 36S;(Other stuff to save BR 36 if not saved yet since breakpoint--this stuff isn't done automaticallyat breakpoints because it prevents continuing.);T _ CPReg(constant+lowaddress);MCR _ T;T _ CPReg(hiaddress);Noop;TurnOffRefresh with two LoadDMD's;DummyRef _ T;Noop;B* _ Pipe5;restore Refresh;B* _ VAhi;B* _ VAlo;[T _ CPReg(DisHold+DisCF+NoWake); MCR _ T; T _ CPReg(SaveBR36!0); BRhi _ T; T_ CPReg(SaveBR36!1); Xct(BRLOFT); MemBase _ S; T _CPReg(SavedSRN); ProcSRN _ T; T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);SelectTask(OldTask); restore MIR; read DMux].Write bySelectTask(17B);T _ CPReg(1);ProcSRN _ T;MemBase _ 36S;(Other stuff to save BR 36 if not saved yet since breakpoint);T _ CPReg(constant);MCR _ T;T _ CPReg(hi(address - new flag value));BRhi _ T;T _ CPReg(low(address - new flag value));BRlo _ T;T _ CPReg(new flag value);Noop;Fetch _ T;Noop;Fetch _ T;Noop;T _ CPReg(constant+lowaddress);MCR _ T;T _ CPReg(new flag value);Noop;TurnOffRefresh;DummyRef _ T;CFlags _ T;restore Refresh;Noop;[T _ CPReg(constant); MCR _ T; T _ CPReg(SavedBR36!0); BRhi _ T; T _CPReg(SavedBR36!1); BRlo _ T; MemBase _ S; T _ CPReg(SavedSRN);ProcSRN _ T; (T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);SelectTask(SavedTask); restore MIR; read DMux].CACHEDRead byT _ CPReg(constant);MCR _ T;T _ CPReg(hiaddress);BRhi _ T;T _ CPReg(lowaddress);BRlo _ T;T _ CPReg(0);Noop;Fetch _ T;T _ Md;B* _ T;[T _ CPReg(constant); MCR _ T; T _ CPReg(SavedBR36!0); BRhi _ T; T _НЇОf╙pТ─Н!цqН5Т НG?ОfЯpНнОbAs НнО`ЮТ┼ПHТ▀НнО_─ТП0НнО^НнО\ЎНнО[]НнОYЭНнОX°П"НнОW;НнОUзНнОTy НнОSНнОQ╦ НнОPW НнОNЖТ┬П%Т┴П(НнОM∙ТчП:ТъНнОL5Т│Т┌П1НнОJтТП-НнОH6НнОFуНнОEtНнОDНнОB╡ НнОARП>НнО?ЯНнО>░НнО=/П(НнО;оНнО:nП)НнО9 НнО7╛НнО6KНнО4К НнО3┼НнО2) НнО0хНнО/hНнО.НнО,іНнО+EНнО)ДНнО(└НнО'# НнО%бНнО$aНнО#ТТ П)НнО!═Т⌠П%Т■П(НнО ?ТeП-ТfНнОчТП/НЇОжНнНнОuНнОНнОЄНнОSНнОРНнО▒НнО1НнОпНнОo НнОНнОўНнОMТТ П)ЪЇ*2A\А!Dorado Midas ManualEdward R. Fiala24 June 198378CPReg(SavedBR36!1); BRlo _ T; MemBase _ S; T _ CPReg(SavedSRN);ProcSRN _ T; T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);SelectTask(SavedTask); Noop; restore MIR].Write byT _ CPReg(constant);MCR _ T;T _ CPReg(hiaddress);BRhi _ T;T _ CPReg(lowaddress);BRlo _ T;T _ CPReg(0);Noop;Q _ CPReg(new value);Store _ T,DBuf _ Q;Noop;[Q _ CPReg(SavedQ); Noop; T _ CPReg(constant); MCR _ T; T _ CPReg(SavedBR36!0);BRhi _ T; T _ CPReg(SavedBR36!1); BRlo _ T; MemBase _ S; T _CPReg(SavedSRN); ProcSRN _ T; T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);SelectTask(SavedTask); restore MIR; read DMux].MAPRead bySelectTask(17B);T _ CPReg(1);ProcSRN _ T;MemBase _ 36S;(Other stuff to save BR 36 if not saved yet since breakpoint);T _ CPReg(constant);MCR _ T;T _ CPReg(hiaddress);BRhi _ T;T _ CPReg(lowaddress);BRlo _ T;T _ CPReg(0);Noop;RBase _ 0S;RB _ CPReg(0), RStk[0];RMap _ RB, RStk[0];B* _ Map';B* _ Errors';B* _ Config';[RB _ CPReg(SavedR0), RStk[0]; RBase _ S; T _ CPReg(constant); MCR _T; T _ CPReg(SavedBR36!0); BRhi _ T; XctL16T(SavedBR36!1); BRlo _ T; MemBase _S; T _ CPReg(SavedSRN); ProcSRN _ T; T _ CPReg(SavedMCR); MCR _T; T _ CPReg(SavedT); SelectTask(SavedTask); Noop; restore MIR].Write bySelectTask(17B);T _ CPReg(1);ProcSRN _ T;MemBase _ 36S;(Other stuff to save BR 36 if not saved yet since breakpoint);T _ CPReg(constant);MCR _ T;T _ CPReg(hiaddress);BRhi _ T;T _ CPReg(lowaddress);BRlo _ T;T _ CPReg(0);Noop;Q _ CPReg(hi new value);TIOA _ Q;Q _ CPReg(low new value);Map _ T, MapBuf _ Q;НЇОf╙pТ─Н!цqН5Т НG?ОfЯpНнОbAsТ╪ТҐП.НнО`ЮТnП=НнО_─ТП*НнО\АНнО[─НнОZ НнОX©НнОW^НнОUЩНнОT²НнОS<НнОQшНнОPzНнОO НнОM╧НнОLXНнОJВТёП7ТєНнОI√ТкП+ТлНнОH6Т│Т┌П1НнОFуТП/НЇОCмНнНнОBlНнОAНнО?╙НнО>J НнО<ИП>НнО;┬НнО:'НнО8фНнО7fНнО6НнО4єНнО3CНнО1ЦНнО0┌ НнО/!НнО-юНнО,_ НнО*ЪНнО)·НнО(=Т■Т∙ПKНнО&эТ╠ПNНнО%|Т┼П4Т▀НнО$ТП@НнО!}НнО НнО╩НнОZНнОЫ НнО≥П>НнО8НнОвНнОvНнОНнО╣НнОTНнОСНнО▓НнО2НнОяНнОpНнО Ъ8Ї Л2A^Dorado Midas ManualEdward R. Fiala24 June 198379Noop;Q _ CPReg(SavedTIOA);TIOA _ Q;Q _ CPReg(SavedQ);Noop;[T _ CPReg(constant); MCR _ T; T _ CPReg(SavedBR36!0); BRhi _ T; T _CPReg(SavedBR36!1); BRlo _ T; MemBase _ S; T _ CPReg(SavedSRN);ProcSRN _ T; T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);SelectTask(SavedTask); restore MIR; read DMux].VMRead bySelectTask(17B);T _ CPReg(1);ProcSRN _ T;MemBase _ 36S;(Other stuff to save BR 36 if not saved yet since breakpoint);T _ CPReg(constant);MCR _ T;T _ CPReg(hiaddress);BRhi _ T;T _ CPReg(lowaddress);BRlo _ T;T _ CPReg(0);Noop;Fetch _ T;T _ Md;B* _ T;[T _ CPReg(constant); MCR _ T; T _ CPReg(SavedBR36!0); BRhi _ T; T _CPReg(SavedBR36!1); BRlo _ T; MemBase _ S; T _ CPReg(SavedSRN);ProcSRN _ T; T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);SelectTask(SavedTask); Noop; restore MIR].Write bySelectTask(17B);T _ CPReg(1);ProcSRN _ T;MemBase _ 36S;(Other stuff to save BR 36 if not saved yet since breakpoint);T _ CPReg(constant);MCR _ T;T _ CPReg(hiaddress);BRhi _ T;T _ CPReg(lowaddress);BRlo _ T;T _ CPReg(0);Noop;Q _ CPReg(new value);Store _ T, DBuf _ Q;Noop;[Q _ CPReg(SavedQ); Noop; T _ CPReg(constant); MCR _ T; T _ CPReg(SavedBR36!0);BRhi _ T; T _ CPReg(SavedBR36!1); BRlo _ T; MemBase _ S; T _CPReg(SavedSRN); ProcSRN _ T; T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);SelectTask(SavedTask); restore MIR; read DMux].IFUMRead byIFUReset;Q _ CPReg(F(address));InsSetOrEvent _ Q;Q _ CPReg(F(address));BrkIns _ Q;Noop;B* _ IFUMRH';B* _ IFUMLH';[Q _ CPReg(SavedQ); Noop; restore MIR].ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНнОbAsНнО`ЮНнО_─НнО^НнО\ЎНнО[]ТТ П)НнОYЭТ╪ТҐП.НнОX°ТnП=НнОW;ТП/НЇОT3НнНнОRрНнОQqНнОPНнОN╟ НнОMOП>НнОKННнОJ█НнОI-НнОGлНнОFkНнОE НнОC╘НнОBIНнО@Х НнО?┤НнО>&НнО<фТТ П)НнО;eТ╪ТҐП.НнО:ТnП=НнО8ёТП*НнО6НнО4єНнО3CНнО1ЦНнО0┌ НнО/!П>НнО-юНнО,_НнО*ЪНнО)·НнО(=НнО&эНнО%|НнО$НнО"╨НнО!YНнОЬНнО≤ТёП7ТєНнО7ТкП+ТлНнОжТ│Т┌П1НнОuТП/НЇОmНнНнОНнО╛НнОKНнОЙНнО┴ НнО)НнО хНнОgНнОП'Ъ*Ї Ц2A](Dorado Midas ManualEdward R. Fiala24 June 198380Write byIFUReset;Q _ CPReg(hiaddress);InsSetOrEvent _ Q;Q _ CPReg(lowaddress);BrkIns _ Q;Noop;Q _ CPReg(new value);IFUMLH _ Q;B _ Q;Q _ CPReg(new value);IFUMRH _ Q;B _ Q;Noop;[Q _ CPReg(SavedQ); Noop; restore MIR; read DMux].LDRArtificial memory.MDATAArtificial memory.MADDRArtificial memory.DMUXRead only by the special Alto microcode and software discussed at the beginning of thissection, when "current" DMux readout is selected. Old, wrong, or checked tables may beselected for this memory by the "DMux" command action; when DChecked is selected, writesare legal.DHISTArtificial memory.VHArtificial memory.MDRead only bySelectTask(address);T _ Md;B* _ T;[T _ CPReg(SavedT); SelectTask(SavedTask)].TASKNArtificial memory which cannot be read or written (used for displaying some valuessymbolically).DEVICEArtificial memory which cannot be read or written (used for displaying some valuessymbolically).MSTATArtificial form of ABSOL memory.ABSArtificial form of ABSOL memory.ROWRead lines 0 to 3 like CACHEA; line 4 (Victim/Next Victim) bySelectTask(17B);T _ CPReg(1);ProcSRN _ T;MemBase _ 36S;(other stuff to save BR 36 if not saved yet since breakpoint);T _ CPReg(constant);MCR _ T;T _ CPReg(F(address));DummyRef _ T;Noop;B* _ Pipe5;[T _ CPReg(constant); MCR _ T; T _ CPReg(SavedBR36!0); BRhi _ T; T _CPReg(SavedBR36!1); BRlo _ T; MemBase _ S; T _ CPReg(SavedSRN);ProcSRN _ T; T _ CPReg(SavedMCR); MCR _ T; T _ CPReg(SavedT);ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНнОbAsНнО`ЮНнО_─НнО^НнО\ЎНнО[] НнОYЭНнОX°НнОW; НнОUзНнОTyНнОS НнОQ╦НнОPWНнОNЖП2НЇОKННнНЇОHФНнНЇОEчНнНЇОBжНнТцТдПKНнОAuТЄПAТ╣НнО@Т▐Т░П@НнО>ЁТ НЇО;╚НнНЇО8ёНнНЇО5⌡НнНнО4:НнО2зНнО1yНнО0П+НЇО-НнТП!ТП1НнО+╞ НЇО(їНнТП!ТП1НнО'F НЇО$>НнТНЇО!6НнНЇО.НнП=НнОмНнОlНнОНнО╚ НнОJП>НнОИНнО┬НнО(НнОгНнОfНнО НнО ╔ТТ П)НнОDТ╪ТҐП.НнО ЦТnП=ЪрЇ ю=Г]KDorado Midas ManualEdward R. Fiala24 June 198381SelectTask(SavedTask); Noop; restore MIR]Write rows 0 to 3 like CACHEA; row 4 is read-only.ЪНЇОf╙pТ─Н!цqН5Т НG?ОfЯpНнОbAsП)НнО_ёП2Ъ▄Ї_─2A▀%MidasPicture.silLoaded: KERNELBEGIN;Sample Midas DisplayGo at 0:BEGIN, BrkP after 0:QERR+1 at 0:QERR+2RunProg RdCmds Brk UnBrk Go SS OS Passive Ld LdSyms Cmpr Dtach Reset SetClkConfig PEscan TestAll Test SimTest SimGo T1 T2 T3 RepGo RepSS RepT2 FieldsLDRtest ShowCmds WrtCmds Virtual DMuxCONFIG 0 PROBLEMS 0 UPTIME 0 days 3:24:42CLKRUN 1040 OUTOFSPEC 0 TGLITCH 0 days 1:2:31ESTAT 0 BADSUPPLYSPEC 0 COMM-ERRS 0INSSET 2 MIR-PES 0OLINK 20 344 VOLTS +12.07 +4.93 -1.98 -5.36TLINK 20 345 AMPS 6 27 75 150TPC 20 346 TEMP0 +27 +35 ?? +27RBASE 20 17 TEMP0+1 +27 +33 ?? ??MEMBASE 20 14 TEMP0+2 +25 +23 -- --T 20 177767 *RTEMP 133747 MINVOLTS +12.07 +4.93 -1.97 -5.18TIOA 20 0 *LTEMP 122001 MAXVOLTS +12.07 +4.93 -1.98 -5.36CNT 1 MINAMPS 5 26 73 86STKP 1 MAXAMPS 34 55 109 154MEMBX 3 BMUX 177777 MAXTEMP0 +27 +35 ?? +27Q 177766 MAXTEMP0+1 +27 +33 ?? ??PCX 0 SHC 0 MAXTEMP0+2 +25 +23 -- --PROCSRN 0 PIPE 0 0 DWATCH 0MCR 0 0 IMOUT 321747 023457TASK 0 0 MIR 124576 035777***8/1/79Н9Оd'ЧF░$НHиОРЧ$XXН9ОоЧFЄ$Н9ОоЧ$X|Н9иxОПН▌pО5ПН▌О%хПНОРПН▌О1╨П.Н▌О,sПKН▌О*хПJН▌О)П%НОZJПKНОX÷ПKНОVУПKНОUJПKНОS÷ПKНОQТПKНОPJПKНОN÷ПKНОLТПKНОKJПKНОI÷ПKНОGТПKНОFIПKНОD÷ПKНОBТПKНО?·ПKНОAIПKНО=ТПKНО