Digital PDFs
Documents
Guest
Register
Log In
EK-DELUA-UG-002
April 1986
126 pages
Original
5.8MB
view
download
OCR Version
6.6MB
view
download
Document:
DELUA User's Guide
Order Number:
EK-DELUA-UG
Revision:
002
Pages:
126
Original Filename:
OCR Text
EK-DELUA-UG-002 Networks - Communications DELUA User’s Guide Prepared by Educational Services of Digital Equipment Corporation 2nd Edition, April 1986 Copyright © 1986 by Digital Equipment Corporation All Rights Reserved The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: PRanasg TM DATATRIEVE DEC DECtape DECUS DELUA Rainbow RSTS RSX DECnet MASSBUS VAX DECsystem-10 DECSYSTEM-20 P/OS Professional VT Work Processor DECmate DECset DIBOL PDP UNIBUS VMS CONTENTS INTRODUCTION Page ETHERNET OVERVIEW ...ttt errree e cssner e s sesnrne s 1-1 PHYSICAL DESCRIPTION ....ooiiiie ettt escereerecsssnvae e s essnsreeses DELUA SYSTEM OPERATION ...ttt saabe e s sssaes Physical Channel FUNCLIONS ...........cccvvvviviiiiiiiieeecireee e easae Data Link Layer FUNCHONS.........ccciiiiiiiiieiiicirier ittt seccerreecceeneeseesssnavneesens Data EncapSulation .........ccccccoiiiiiiiiiiiieiiiiciiinieeeesenniieseseeesesesssssnseessessssens Data Decapsulation ........ccceiiieciiiiiiiiiiiee e errereecerrreeecesansesesssareeessssssseeesensns Link Management ............ooviiiiiiiiiiiiiiiieicccccniiiere e sseieesseseeeeessssnsssssssesseessns DIAGNOSTIC FEATURES .......oi oottt cttnecesreerecessnsesessssnanseessons INTERNAL HARDWARE OVERVIEW .......iiitieeeecccninrreeeeee e MICTrOProCesSOr SUDSYSIEM .....cccvviviviiiciieeeiertieeeesreeeessrrrreesessnreeesssaesesesssnns MemOry SUDSYStEM .....cccovviiiiiiiiiiiie i scrrecnreeereesebeeeeeee e s saee e ssnssssasneens LANCE SUDSYStEML...ccciiiiiiiiiciriie et sssree e ceesree s ssarsresessannaesessannnes Direct Memory Access (DMA) Subsystem .........cooveeeeviveennineenniiennsinenensnees Port Control and Status Register (PCSR) Subsystem .........c.cccccecevvvereernnneen. SPECIFICATIONS . ...t revrreereenrreeeeenrraees RELATED DOCUMENTS ..ottt csereee s snnseeseessreeessssansesssnssenes 1-2 1-5 1-5 1-6 1-6 1-6 1-7 1-7 1-8 1-8 1-8 1-9 1-9 1-9 1-10 1-11 INSTALLATION PREINSTALLATION CONSIDERATIONS.......teeeetteeerrerec e ceeenneeeee 2-1 Backplane ReqUIrEMENLS.........ccocvvvieieieiiiiiiiriiieeeenineeneeecesssnsssssessssssssssssnee Bus Latency CONStraints .........coccvvveeeeiiiiiiiiinireeeeensiiieereesesssssesseereessssssssssssses Bus L0ading FacCtor.......c.voviiiiiiiiiiiiiiic it ccrre e esnnere s esssrrseesssnnseens UNPACKING AND INSPECTION......ccottiireeeeecrrrcnrrccineeesvesessiseecsnee e PREINSTALLATION PREPARATION ...ttt ccerecnieeennireensreeenns Backplane Preparations..........cccccceiovvieeeiiiiieeeeienreeeenseeeeeesisseecssssssesesssssnesessns 2-1 2-1 2-1 2-2 2-2 2-4 Device Address ASSIZNMENL........cccccivieiiiiiiiireeiiiierecciieecsiseeeesssrseeeeesssnsees Boot Option Selection (PDP-11 Host Systems Only).......cccccceevvveeeiveeennnnn, Loop Selftest Switch (for Manufacturing Use) ........ccocvvveevecrverenrcineerennnnn. INSTALLATION ..ottt nireeseesre s e e sensraeessssssaassssesbssssasessassesnssnaens VERIFICATION CHECKS ...ttt ccrrecnrieecesvneseseneesssnne e seesssaessesnassens 2-4 2-5 2-7 2-7 2-9 2-11 Postinstallation Power ChecK..........cccviviiiiiiiiiiccieieeeecere e sccvneecsevnne s Light-Emitting Diode (LED) Checks......c.cccceviviuiriiiririicnrneieireneneessnneeessinnenes DIAGNOSTIC ACCEPTANCE PROCEDURE..........ccoovtvertiercreecieeesiveennenes 2-12 2-12 2-12 Vector Address ASSIZNMENL ...........cooiveiiiiiiiiiieeeeeiiiiiireereeeeesessereesssssssssssseens W N INTRODUCTION ......coiiiiiiiiiiiiiiiiiiiiinitciiienresessatsescsssesseessssssessssessessseons PORT COMMAND EXECUTION .....ccccovirirririnnrennennnesessnessenssssssssessssssesssons ANCILLARY FUNCTION EXECUTION........cccoviiimiinnirncinscnnennneissienessnenns W PROGRAMMING OVERVIEW w CHAPTER 3 W N »— W — w N — CHAPTER 2 DD ND DD DD T T B W — R N e T B N AW - CHAPTER 1 il 3-1 3-1 3-1 CONTENTS (Cont) 3.9 DATA FRAME TRANSMISSION AND RECEPTION.......ccccoovvevrvviveennnnnenn, 3-2 FUNCTIONAL STATES ...ttt siesssrteesstnscebaesssaeessee s nns 3-3 POWERUP AND RESET ...ttt csrreeesiessesssreeessssesossasaessnns 3-8 STOP AND RESTART...ttt e sseniesesestseesssaassssssasssssnnessans 3-9 ANCILLARY FUNCTIONS THAT INTERFERE WITH MESSAGE PROCESSING .....ooociiecireeeeecrte e srtreenreeeeses s bessensseesssesssssesssessssbesssnnees 3-9 SUMMARY OF COMMANDS ...ttt sneseessets e seresessseessveesasns 3-11 CHAPTER 4 REGISTERS AND COMMANDS 4.1 PORT CONTROL AND STATUS REGISTER 0 (PCSRO).......ccccoovevvirerreennnn. 4-1 4.2 4.3 4.4 4.5 4.5.1 4.5.2 4.5.3 4.5.4 4.5.5 4.5.6 4.5.7 4.5.8 4.5.9 4.5.10 4.5.11 4.5.12 4.5.13 4.6 4.7 4.8 4.9 PORT CONTROL AND STATUS REGISTER 1 (PCSR1).....ccovvvvvvererierenens 4-5 PORT CONTROL AND STATUS REGISTER 2 (PCSR2).......ccccccevvvrnvrrnnnnn. PORT CONTROL AND STATUS REGISTER 3 (PCSR3).....ccccocvvvvvvrvrvrinennns PORT CONTROL BLOCK FUNCTIONS.........ovteereiectenntee e eveens No-Operation, Ancillary Function Code O.........ccccevvevvvviiniviiniineeniieene, Start Microaddress, Ancillary Function Code 1........ccccovvvevriieecirencirinnnnnne. Read Default Physical Address, Ancillary Function Code 2........................ No-Operation, Ancillary Function Code 3 .......ccccoovvirvimriiiinernceeneenerenene Read/Write Physical Address, Ancillary Function Codes 4/5..................... Read/Write Multicast Address List, Ancillary Function Codes 6/7 ........... Read/Write Descriptor Ring Format, Ancillary Function Codes 10/11 ..... Read/Read and Clear Counters, Ancillary Function Codes 12/13.............. Read/Write Mode Register, Ancillary Function Codes 14/15 .................... Read/Read and Clear Status, Ancillary Function Codes 16/17.................. Dump/Load Internal Memory, Ancillary Function Codes 20/21 ................ Read/Write System ID Parameters, Ancillary Function Codes 22/23........ Read/Write Load Server Address, Ancillary Function Codes 24/25 .......... TRANSMIT DESCRIPTOR RING ENTRY....cccceovviniiniriniicrrinresreenneesree RECEIVE DESCRIPTOR RING ENTRY ....ccoocioiiiiiiineinretecrecriseeseneseenens TRANSMIT DATA BUFFER FORMAT ........cooccoiiiniiiiircecrineeseeceeeresneesneas RECEIVE DATA BUFFER FORMAT ..ottt 4-7 4-7 4-7 4-8 4-9 4-10 4-10 4-11 4-11 4-13 4-15 4-22 4-24 4-26 4-28 4-34 4-34 4-37 4-40 4-42 CHAPTER § MAINTENANCE OPERATIONS LU NLLLULLLL U LWL Page REMOTE BOOT AND DOWN-LINE LOAD......cccccoovitintinieeeeeereeeeeeeeesesnns 5-1 Remote Boot Disabled............oovveiiiiiniiiiiiicieccecceee st eee e s s 5-1 Remote Boot from System Boot ROM .......ccocoovviiiiiieiiiienieeeeeeeeeeeeeeennns 5-1 Remote Boot and System Load..........cccoveiiriiiiiiiiiieeciceeeeeeeee e 5-2 Remote Boot 0n POWEIUP ......cccueeieieeiieieceictictecct et s 5-4 BOOT Port Command...........cccovvivviiiiniiiiicririeieseesreeseese st eeree e sevesesesees 5-4 BOOT FRAME FORMAT ........cooiiiiiieitie ettt st eee s seesaeeesasenase cce e ens 5-5 REQUEST PROGRAM FRAME FORMAT .....ccccoocvvevevvecveeeannn.e eerr e 5-7 MEMORY LOAD WITH TRANSFER ADDRESS FRAME FORMAT......... 5-10 INTERNAL AND EXTERNAL LOOPBACK MODE .......ccccouvvveeeeereeneannnn, 5-11 CHANNEL LOOPBACK ...ttt esteseee e esneesasasesaneeens 5-12 LOOPBACK FRAME FORMAT ..ottt eae e s e 5-13 REQUEST ID FRAME.......oooiii ettt iiiccee e s e sena s 5-14 SYSTEM ID FRAME FORMAT .....coo ettt oiiieeee eeveeae s e seesere e 5-16 MICROCODE LOADING .......cccoieieiiiteceieeiteecte et eeeeeeaeaeeeseeesseetesnn stest 5-18 MICROCODE UPDATE PROCESS .........oooiitieeiiteeteeteee eeeeeeeeceeeseeesene e 5-19 —— —-— O 000 QNN BRI Nh WL — 3.4 3.5 3.6 37 3.8 1v CONTENTS (Cont) CHAPTER 6 SERVICE Page MAINTENANCE PHILOSOPHY ...ooiiiiiiitiee ettt csessvivevee s s s sssssennas TROUBLESHOOTING PROCEDURE.........ivtiiiiiiiiiieiiiiiciieeneeeeeineeeeeeeees SO St ittt e e e e e e et e e e e s e eaasreaares DELUA VAX On-Line Functional Diagnostic (EVDYB¥*).........ccccuvvveeee.n. DELUA PDP-11 Functional Diagnostic (CZUAD*).......ccccccovvvviinvrrvinnnnnnn. DEC/X11 DELUA Test CXUAD ...ttt NI Exerciser CZUAC*/EVDWOCH . oiiiieeetettetvseveeeeeeeeseeeees APPENDIX A 6-1 6-1 6-1 6-5 6-6 6-8 6-8 FLOATING DEVICE ADDRESSES AND VECTORS FLOATING DEVICE ADDRESSES AND VECTOR ADDRESSES............... FLOATING DEVICE ADDRESSES ...t ccerinereeee e FLOATING VECTOR ADDRESSES.........ii e DEVICE AND VECTOR ADDRESS ASSIGNMENT EXAMPLE ................. A-1 A-2 A-3 A-4 FIGURES e Page DELUA Component PartS........ccccccoeiiiiiiiiiiiiiiiiiiiieec et eeeevnree e e e e e s Large-Scale Ethernet Configuration.............cocoviiviiiiiiiiiiiiiiiee 1-3 1-4 DELUA-to-LAN Block Diagram........cc.cccccciiiiiiiiiiiiiiicccciieeee e cecirerree e e 1-5 1-6 DELUA Block DIagram .........ccccccoiiiiiiiiiiiicce e cesntrenr e essaiaaae e 1-8 DELUA Component PartS.........cccccvviiiiiiiiiiiiieeeesiiieeceririeeessiieeeseessveeessssnnessesnnns Switch Pack at E106, Device Address ASSIZNMENt .........ccvvvvvieiiviiiiinininneeerinnnnnee. Device Address and SwitCh POSItIONS..........cocovvvviiiiiiiiiiiriiec it Switch Pack at E69, Vector Address Assignment...........cccceeeeevviiieeerncnineeeeennvneenn. Vector Address and Switch PoSItiONs.............ccoovvuvviviiiiviiiiiiee e Boot Function SWitChes .........c..ooviiiiiiiiiiere e Loop Selftest SWitCh Setting .......cccccovivivieiiiiiiiiie e svee e e 2-3 DELUA Installation Procedure...........cccoiviviiiiiiiiiiiiiiieccceiree s ee e s s Loopback TransCeIVET SELUP .......cccccveiiiiiiiriiieeeiiieeeecrie e ceitreeeeesareeeecssrareeeeenarreesenns DELUA LEDS...ciiiiiiiiiiiiie ettt eesetisbae s e e s essanasnasseesssssannes Bulkhead LED ..ot ceeirere e cessrnre s e es e 2-9 2-11 2-13 2-13 DELUA PCSRs and Host Memory Data Structures..........ccccceeevveenveveeeeiinninnnee. 3-2 Port Control and Status Register 0 (PCSRO) Bit Format........ccooeevvivveeeiiiiinnnnene. 4-1 Port Control and Status Register 1 (PCSR 1) Bit Format...........ccoeevvvvvevirirennnnnee. 4-5 Port Control and Status Register 2 (PCSR2) Bit Format.........ccccccoevvvriinninnnennnns 4-7 Port Control and Status Register 3 (PCSR3) Bit Format.......ccccoovvveevviveveevennennnn. 4-7 Port Control Block (PCB) Bit FOrmat ............cvvviiieiiiiiiiiiiieciirieeeeeeeeeeeneeessseseens 4-8 No-Operation, Ancillary Function Code 0 Bit Format.........c.cccccccovvvvvereeivniinnnnen. 4-8 Start Microaddress, Ancillary Function Code 1 Bit Format...........ccccovvvreerennnnnn. 4-9 Read Default Physical Address, Ancillary Function Code 2 Bit Format............. 4-10 Read/Write Physical Address, Ancillary Function Codes 4/5 Bit Format.......... 4-11 Read/Write Multicast Address List, Ancillary Function Codes 6/7 Bit FOrmMat .......ooooivivviviriiiriiirrcisseieiseneeesseseeeesseesteneesreseeseseses 4-12 D 00 ~JON W W N — L —— —_— O O 00 INW W — NN NN N e e i — o Format of @ Data Frame..........cccccoovoiiiiiiiiiee e Kt e Title e i O N N N ] [} [} [] bW N Figure No. 2-4 2-5 2-6 2-6 2-8 2-8 FIGURES (Cont) Figure No. Title 4-11 4-12 Multicast Address List UDB Bit FOrMat...........ccoeveveeemeeeeereeeeeeeeoeeeeoeeoeeoeosesenos 4-13 Read/Write Descriptor Ring Format, Ancillary Function Codes 10/11 Bit FOIMAL ........covviviuiiieiiet ee eeeeeeeeee 4-13 Read/Write Descriptor Ring Format UDB Bit Format............o.oveovemoooomoonnn., 4-14 Read/Read and Clear Counters, Ancillary Function Codes 12/13 Bit Format... 4-16 Read/Read and Clear Counters UDB Bit FOrmat ............o.oovveoeomoooeooooeooono 4-17 Read/Write Mode Register, Ancillary Function Codes 14/15 Bit Format.......... 4-22 Read/Read and Clear Status, Ancillary Function Codes 16/17 Bit Format ....... 4-24 Dump/Load Internal Memory, Ancillary Function Codes 20/21 Bit Format ..... 4-26 Dump/Load Internal Memory UDB Bit FOrmat.............oououoeoeoeeeoeooeooooomoonn 4-27 Read/Write System ID Parameters, Ancillary Function Codes 22/23 Bit FOrMAL ..........covivvieeeieeereeeeeeeeeee oot 4-29 Read/Write System ID Parameters UDB Bit Format ...........ooovvoeoooooooooon, 4-30 Read/Write Load Server Address, Ancillary Function Codes 24/25 Bit FOIMAL ......cc.oocuvuiiineieceeeeecereeeeeesesesesese et 4-34 Format of an Entry in the Transmit Descriptor Ring..........ocooevevevveveveeveonn o. 4-35 Format of an Entry in the Receive DeScriptor Ring.........coocevevevvvevevevevoiens 4-38 Transmit Data Buffer Starting on an Even-Byte Boundary.........ccoovvveevrerennnn, 4-40 Transmit Data Buffer Starting on an Odd-Byte Boundary ..........cccoovvvvveeiennennn. 4-41 Receive Data Buffer FOrMat............ccovviveveeeeeeeeeeereeceee oot 4-42 4-13 4-14 4-15 4-16 4-17 4-18 4-19 4-20 4-21 4-22 4-23 4-24 4-25 4-26 WO D WN — N — Troubleshooting FIOWCRArt .............oucuiviuiveeeeeeeeeeee oo Selftest and Status LEDS ............coovuviee oo ueveree e eeeeeeee 6-2 6-4 UNIBUS Address Map ...........coouviiuireinieeeeeeeeeeeesesieceesesee oo A-1 A s BoOt Frame FOrMAat........coocuiuii oo e eiiiiiicceeee 5-5 Request Program Frame FOrmat .........c.ouvveveeiomeeeemoreeeeeceeeeeeeeeeeeeeeeseeoeeoon 5-7 Memory Load with Transfer Address Frame FOrmat..........o.ovovevemomomoooooonn 5-10 Loopback Frame FOrmat.........c.ccciuiuiiiiiieeeeee oo eeeeeeeee oo eeeseeeee 5-13 Request ID Frame FOrmat............ovuvveueeeeeeeeeseeeeeeeeeeeeeeeee oo 5-15 System ID Frame FOrmMat ..........couvvevueueeeeeeeeeeeeere oo 5-16 Microcode Patch File FOIMAat .........covvvveereeeeveeenierereeeeeeeeeeoeeeoeeeeeeeeeeeeees e 5-19 Patch File Data Block FOrmat ..........cooeeueveuemeeeeeeeeeeeeeeeeoeeeeeeeeoeeoeooo ee 5-20 > 4-27 Page vi TABLES Table No. Title Page I-1 DELUA SpPeCifiCations .........ccccvereriiuriersrieeeenisiiieeiniinerissisneecsssnssessssnsssnsmssesssssaes Related Documents...........cccoevvnvviencenenns teeersrereseereeeeerrrraeeeeeesssssnnetessesssiasataeiesseres 1-10 1-11 PR ELLY FUNCLIONAL SEALES ...vvviiiviii ittt eerre e s erteseetreeessasssseasssasassssnassssnrsssssesssrenes 3-3 Functional State Transition SUIMMATY ........cceeiiiriirnreeeerirrrreereeesierssssnssssssssssanessssns 3-5 State Information Retention SUMMATY......c..covviniiriirinnnnrisisninnneeresiieeemm. 3-7 Ancillary Functions that Interfere with Message Processing...........ccoocevvuieiiinnennns 3-10 DELUA Port Commands..........covviereeeieeirinneeercesssssnnnsssssssssnsssssssssancessssssnsesssssssanes DELUA ANCIllary FUNCLIONS ......ccccvivieiiiiriniieeieeiniecneieeresssnasnssssnenessssnecssssnssenns DELUA Maintenance FUNCLONS.........ccoovvviiiiiieiivereeeneninnneesiicsnneieccsnnneeseessnane 3-11 3-11 3-12 Port Control and Status Register 0 (PCSRO) Bit DescCriptions.....c..cocoeeeeeurerrnne Port Control and Status Register 1 (PCSR1) Bit Descriptions.........ccccccvvuveeinneee Port Control and Status Register 2 (PCSR2) Bit Descriptions..........ccccceevueeernnee. Port Control and Status Register 3 (PCSR3) Bit Descriptions.........cccccocrveerrnnnnne Port Control Block (PCB) Bit DeSCrIPtions .........cccccveeeeeririececssrrrenreseassereessessonsnns No-Operation, Ancillary Function Code 0 Bit Description .......c.ccccoeeveiirivueeennnnee. Start Microaddress, Ancillary Function Code 1 Bit Descriptions...........cccoeuueeeen. Read Default Physical Address, Ancillary Function Code 2 Bit Description....... Read/Write Physical Address, Ancillary Function ............cccooviiiiiiiiiiiinniinninnnnnn, Read/Write Multicast Address List, Ancillary Function Codes 6/7 Bit DESCrIPLIONS.......cccccvuieeriivrerrerreersssieeiornesssinnsisssseesssssansessssaessssns Read/Write Descriptor Ring Format, Ancillary Function Codes 10/11 Bit DeSCIIPLONS........cecveeiirerireerireeerierssieessssessseesssneessseessssnssnne Read/Write Descriptor Ring Format UDB Bit Descriptions............cccoocceiinuennnnen. Read/Read and Clear Counters, Ancillary Function Codes 12/13 Bit DesCriptions..........ccccvveereererrnineneinnniensiniesscsssssisssessssserssssnns Read/Read and Clear Counters UDB Bit Descriptions .........c.ccocvveceviivinnnereennnnns Read/Write Mode Register, Ancillary Function Codes 14/15 Bit DeSCriPLiONS. .......cccvvvieeiieriieeeeererrreeereecsseeeeessssssstessosssnesesessnes Read/Read and Clear Status, Ancillary Function Codes 16/17 Bit DeSCIIPLIONS. ......c.ccvuiieiiereirireeressnrrreeesssisteessssssesessssssnsessessns 4-1 4-6 4-7 4-7 4-8 4-9 4-9 4-10 4-11 ' — o O 00 1N bW — ~N AN W — S WHN— Nt?)NN DELUA Power CONnSUMPLION.........cuuuierrereeeeceeeeiiiniiiiiinnimmmssssmsmissmseeesessesssssssmnnne 2-2 Boot Function Switches (PDP-11 Only)......cccoovveriiiiiiiiiniiiiinnneiinnenennineneenne. 2-7 DELUA PoWer ChecCK.....o.oooiiiiiiiiiieecieriercccccsreeeeseecssssnnneessssssssssennesssssssssanaessees 2-12 DELUA DiagnoStiCS ......uveeeiiiiirreereiieerirereresseseressnsessessssssssnessesssssssrssssssssssssassasanees 2-12 PPEPP &A&A?A&h&b 1-2 4-11 4-15 4-16 4-17 Dump/Load Internal Memory, Ancillary Function Codes 20/21 Bit DeSCIIPIONS. .....cccivviiiiieiriiiirieerecesinreresesesaereesssssneesssossannissess Dump/Load Internal Memory UDB Bit Descriptions............cccccvvviiivinninieiniinnnns Read/Write System ID Parameters, Ancillary Function Codes 22/23 Bit Descriptions........ Nererreeeeereeierranrrrateeteettaeasrraaraeaeeeaaesenrnenarrnaeas Read/Write System ID Parameters UDB Bit Format ..........cccoonvviviiinnnniininnne, Read/Write Load Server Address, Ancillary Function Codes 24/25 Bit DeSCIIPLIONS.........cccccuviiiiieieeiierirneirnrerecesssesssoniinnerseesesssssnsnns 4-12 4-14 4-15 4-16 4-18 4-22 4-25 4-27 4-28 4-29 4-31 4-34 Bit Descriptions of a Transmit Descriptor Ring Entry......cccococvvvvinnnnnin. 4-35 Bit Descriptions of a Receive Descriptor Ring Entry........ccccccceviiivininnnnininnn 4-38 Vil TABLES (Cont) Title Page Boot Frame DESCriPtioN..........cccovriiiieieicieieectc ettt se n e Request Program Frame DesCription..........cc.c.c.cveviiiniiriiinneceesiseseeseenessessesaes Memory Load with Transfer Address Frame Description..........co.ccveveeevveeverennnnn. Loopback Frame DeSCription ...........cccovveiieiiiiiiiiiciiccetcretseeceeee eee e sessenas Request ID Frame DesCription...........cccucivouieiiriiiiiiiieecieeiereteeeeseeseseseesessssesssnes System ID Frame DeSCriPtion............ccooiiviiiiiviieeeeeeeeeeeeeeeeeeeeesesesseesssesssseessesesenes 5-6 5-8 5-11 5-14 5-15 5-17 Selftest Error and Status Codes...........covvvvvriivieeiinieeieeereieeeee e eeee e eereseseess e, DELUA VAX On-Line Functional Diagnostic (EVDYB*) Test Summary ......... DELUA PDP-11 Functional Diagnostic (CZUAD*) Test Summary................... 6-6 6-7 Floating Device Address Ranking SEqQUENCE.........cooveueeeveeveeeeeeeeereeeeeeeeeeresseesaen, Floating Vector Assignment SEQUENCE.............ccvvveeeeereeeeeeeeeereeeeeeeeereieeseesesessesons Device and Vector Address ASSIZNMENLS............ccovevvereeeeeeeeeeeeeeeeereereressesseesessons viii 6-4 A-2 A-3 A-5 CHAPTER 1 INTRODUCTION The DIGITAL Ethernet large-scale-integration UNIBUS adapter (DELUA) is an Ethernet communica- tions controller option for VAX and PDP-11 computers. The DELUA adapter is a follow-on product to the DIGITAL Ethernet UNIBUS network adapter (DEUNA). The DELUA option performs all the same functions as the DEUNA option, but it offers higher performance and lower power consumption. NOTE For ease of use and reader comprehension, the DELUA adapter will be referred to as the DELUA throughout the document. Similarly, the DEUNA adapter will be referred to as the DEUNA and the UNIBUS bus as the UNIBUS. 1.1 ETHERNET OVERVIEW The Ethernet is a local area network (LAN) that provides high-speed data transfer among computers and other digital devices within a moderately sized geographic area. It is intended for devices requiring brief bursts of high-speed data transfers, such as terminal access, distributed processing, and office automation. The primary characteristics of Ethernet include: Topology - branching bus. Medium - shielded coaxial cable, Manchester-encoded digital baseband signaling. Data Rate — 10 million bits per second (maximum). Maximum Separation of Nodes - 2.8 kilometers (1.7 miles) on one LAN; several LANSs can be connected with LAN Bridge 100 devices to form an extended LAN. Maximum Number of Nodes — 1,024 nodes on one LAN; several LANSs can be connected with LAN Bridge 100 devices to form an extended LAN. Network Control — multiaccess, fair distribution to all nodes. Access Control - carrier sense, multiple access with collision detect (CSMA /CD). Frame Length - 64 to 1518 bytes, including a data field from 46 to 1500 bytes. The Ethernet is a medium-sized network. It is smaller than long-distance, low-speed networks that carry data for hundreds or thousands of kilometers and it is larger than specialized high-speed interconnections that are generally limited to tens of meters. 1-1 An example of a large-scale Ethernet configurations is shown in Figure 1-1. When configuring an Ethernet local area network you must observe the following rules: I. A segment of coaxial cable can be a maximum of 500 meters (1640 feet) long. Each segment must be terminated at both ends with the characteristic impedance. 2. Up to 100 nodes can be connected to any segment of the cable. Nodes on a cable segment must be spaced at least 2.5 meters (8.2 feet) apart. 3. The maximum length of the transceiver cable between a transceiver and a controller, such as the DELUA, is 50 meters (164 feet). In the case of the DELUA, the internal cabling between the DELUA and its bulkhead assembly accounts for 10 meters (33 feet). The DELUA, therefore, can support up to 40 meters (131 feet) of transceiver cable. 4. The maximum length of coaxial cable between any two nodes in a single LAN is 1500 meters (4922 feet). However, the length of cable between two nodes can be greater if part of the cable is fiber-optic cable connected by repeaters. Also, this 1500-meter length limitation does not apply to nodes on different LANSs of an extended LAN connected by LAN Bridge 100 devices. 5. A LAN can be extended by connecting two segments with repeaters and a length of fiber-optic cable. A fiber-optic cable connected to a repeater can be up to 1000 meters (3280 feet) long. 6. A maximum of two repeaters can be placed between any two nodes on the same LAN. 7. LAN Bridge 100 devices can be used to connect LANS to form an extended LAN. There is no limit to the number of LANs that can be connected using LAN Bridge 100 devices, but performance may be poor if a message must travel through more than seven bridges before reaching its destination node. 8. LAN Bridge 100 devices can be connected using a fiber-optic cable. The maximum length of such a cable depends on the type of cable and the number of splices and connectors, but it can extend as far as 2000 meters (6560 feet). 1.2 PHYSICAL DESCRIPTION The DELUA is illustrated in Figure 1-2. The DELUA consists of: e ) e M7521 hex-height module UNIBUS Network Adapter (UNA) bulkhead assembly UNA bulkhead cable assembly The DELUA kit for non-FCC-compliant cabinets (CK-DELUA-KI) also contains a bulkhead frame (74-27292-01). The UNA bulkhead assembly is connected to the transceiver on the LAN’s coaxial cable with a transceiver cable. DELUA controls and indicators consist of two dual in-line package (DIP) switches and eight light-emitting diodes (LEDs) mounted on the M7521 module, plus an LED on the UNA bulkhead assembly. The switches are used to select DELUA operating parameters and are set before installing the module. The LED:s display DELUA selftest error and status information. The function of these switches and indicators is described in Chapter 2. R J10W3Y 1-3 -d4381d Jl1dO H31v3id3y -438I14 JiLdO 318vD WVIXVOD 318vO 2InSiLg-19[eos-981eyjPuIdYIguoneIndijuo) 1v201 390148 H31Vv3id3ay N1 C# LN3WS3S IvI01 H3IAIFOSNVYHL €#NV L/ Y SP8L-SBANN M75621 BULKHEAD BULKHEAD CABLE ASSEMBLY Ny — ) MODULE BULKHEAD FRAME (FOR USE WITH NON-FCCCOMPLIANT L CABINETS) MKV85-1838 Figure 1-2 DELUA Component Parts DELUA SYSTEM OPERATION 1.3 The DELUA controller performs both the data link layer functions and a portion of the physical channel functions. It also provides the following network maintainability functions: Loops back maintenance messages from other nodes Periodically transmits system identification e e Loads and boots its host operating system (PDP-11 only) from another node on the network e The DELUA provides all of the logic necessary to connect VAX and PDP-11 computers to a local area network (Figure 1-3). The DELUA performs data encapsulation and decapsulation, data link management, and all channel access functions to ensure maximum throughput with minimum host processor intervention. BULKHEAD CABLE i T TRANSCEIVER CABLE DELUA UNIBUS P M7521 <:> MODULE B oy UNA \} TRANSCEIVER BULKHEAD ASSEMBLY s MKV85.0320 Figure 1-3 1.3.1 DELUA-to-LAN Block Diagram Physical Channel Functions The DELUA provides the following specific physical channel functions to interface with the transceiver: During Transmission Generates the 64-bit preamble for synchronization Provides parallel-to-serial conversion of the frame Generates the Manchester encoding of data Ensures proper channel access by monitoring the presence of another station’s transmission Monitors the selftest collision detect signal from the transceiver During Reception Senses for presence of a carrier from another station Performs Manchester decoding of the incoming data stream Synchronizes itself to the preamble and removes the preamble before processing Provides serial-to-parallel conversion of the frame Buffers received frames 1.3.2 Data Link Layer Functions The DELUA provides the following data link layer functions: Calculates the 32-bit cyclic redundancy check (CRC) value and sends Attempts retransmission upon detecting a collision it with the frame Checks incoming frames for the proper CRC value Accepts only frames with specified destination addresses 1.3.3 Data Encapsulation The frame format is shown in Figure 1-4. Each frame begins with a 64-bit preamble that allows the receiving node to synchronize exactly to the data rate. Frames are separated by at least 9.6 us to allow another node the opportunity to send a message. /7 DESTI- PREAMBLE | NaTION [ SOURCE | Tvee ADDRESS FRAME DATA CHECK SEQUENCE | INTERFRAME | | _____[ 8 BYTES 6 BYTES 6 BYTES 2BYTES 46 TO 1500 BYTES 4 BYTES 9.6 us MKV85-0326 Figure 1-4 Format of a Data Frame The destination address field contains the address of the node to which the frame is being sent. This address may be the address of a particular node, a multicast address associate d with a group of nodes, or a broadcast address for all nodes on the network. The source address field specifies the physical address of the transmitting node. Each DELUA has a unique 48-bit physical address built in during manufacture. The system software can override this value and assign a different physical address. The type field is used by high-level network protocols. It indicates The data field may have between 46 and how the data field is to be interpreted. 1500 bytes of data. The DELUA can be initialized to automatically insert null characters, if the amount of data is less than the minimum 46-byte data size. The frame check sequence field contains a 32-bit CRC value, which is determined and inserted by the DELUA during transmission. 1.3.4 Data Decapsulation The DELUA continuously monitors the signals received by its transceiver. After sensing a carrier, the DELUA uses the preamble sequence of the frame to synchro nize itself to the data rate of the frame. The DELUA then processes the destination address field through a hardware comparator to determine whether the incoming frame is intended for its node. The DELUA accepts only frames that have a destination address matching one of the following types of addresses: The physical address of the node The broadcast address for all nodes One of the ten multicast group addresses that the user may assign to the DELUA, when desired Any multicast address, when desired All addresses, when desired The DELUA performs a hardware comparison of the 6-byte destination address to determine if thereis a match with the node’s physical address or one of the user-designated multicast addresses. If the user desires to receive more than ten multicast address groups, then all multicast addresses can be passed to higher-level software for discrimination. To assist in network management functions and to aid in fault diagnosis, the DELUA may operate in a mode that disregards the address field, thus accepting all frames received from the network. The DELUA verifies the integrity of the received data by recalculating the 32-bit CRC value and comparing it to the CRC obtained from the received frame. 1.3.5 Link Management The method used for channel access is called carrier-sense, multiple-access with collision-detection (CSMA /CD). The DELUA controls all of the link management functions necessary to send or receive a frame of data. These functions include: e Carrier Deference - The DELUA monitors the physical channel for traffic. If the channel is e Collision Detection - Collisions occur when two or more controllers attempt to transmit data simultaneously on the channel. The DELUA monitors the collision sense signal generated by a transceiver to detect a collision. When it detects a collision, it continues to transmit for a period busy, the DELUA waits until it is not busy before sending a frame. of time to ensure that all other nodes detect the collision. e 1.4 Collision Backoff and Retransmission — When a controller attempts a transmission and encounters a collision on the channel, it attempts a retransmission a short time later. The schedule for retransmission is determined by a controlled randomization process called truncated binary exponential back-off. The DELUA attempts to transmit a total of 16 times (15 times plus the original transmission). If it fails after these 16 tries, it will report an error. DIAGNOSTIC FEATURES Microdiagnostics, system, and network diagnostics are used to minimize the time required to isolate and diagnose a network communication fault. Built-in selftest microdiagnostics automatically test the DELUA component logic during powerup. These selftest diagnostics report errors by means of LEDs on the edge of the module. To eliminate the possibility that the DELUA may monopolize the network after certain logic failures, the DELUA has a special circuit that limits the frame transmit period. The DELUA monitors the transceiver’s collision test signal after every frame transmission to verify that the collision sense circuitry is working properly. At the request of another node, the DELUA sends a loopback message to the node specified by the requesting node. This feature allows physical connections between nodes to be verified. The DELUA detects and tabulates network statistics and error conditions for use by higher-level network management applications. 1-7 1.5 INTERNAL HARDWARE OVERVIEW . The DELUA is a microprocessor device based on the Motorola 68000TM microprocessor. The internal hardware of the DELUA is divided into the following major subsystems also shown in Figure 1-5. Microprocessor Memory Local Area Network Controller for Ethernet (LANCE) Direct Memory Access (DMA) Port Control and Status Registers I MICROPROCESSOR l é © Z 5 I SUBSYSTEM l 1 PORT CONTROL ‘ l 2 0 — AND STATUS REGISTERS SUBSYSTEM I ? [¥2] , bl LANCE SUBSYSTEM @ o = I TO NETWORK TRANSCEIVER l < & < l MEMORY SUBSYSTEM 128KB RAM 16KB ROM DMA SUBSYSTEM I .| MKVBS-1039 Figure 1-5 DELUA Block Diagram 1.5.1 Microprocessor Subsystem The Motorola 68000 microprocessor has a 400 ns cycle time and supports auto-vectored interrupts. Each of the internal subsystems has its own interrupt vector address. The microprocessor also resolves internal bus (IBUS) arbitration conflicts when two or more internal subsystems try to use the IBUS simultaneousl y. 1.5.2 Memory Subsystem The internal memory is made up of 128K bytes of random access memory (RAM) used for data buffering and microcode execution, and 16K bytes of ROM containing the microcode. There is also an 8-byte ROM containing the Ethernet physical address assigned to the DELUA during manufacturi ng. During powerup the DELUA copies its microcode from ROM to RAM because the memory cycle time of RAM is faster. Motorola 68000 is a trademark of Motorola, Inc. The memory control and status register provides the microprocessor with status information on memory errors and allows the microprocessor to remap memory at powerup. This register also allows the microprocessor to disable parity checking and force parity errors for microdiagnostic purposes. Normally, the left byte of cach word has even parity and the right byte has odd parity. Thus, a failure that produces data of all ones or all zeros will produce a parity error. The system timer circuit causes a 300 ns memory refresh cycle every 8 us. 1.5.3 LANCE Subsystem The LANCE itself is also a microprocessor-controlled device. When the DELUA is initialized, the DELUA microprocessor provides the LANCE with receive data buffers in DELUA internal memory. The LANCE watches message traffic on the network and checks the destination address of each frame. If the address matches the DELUA physical address, a multicast address, or the broadcast address, the LANCE writes the frame into one of the receive data buffers and interrupts the microprocessor. The LANCE checks the CRC field of the frame and reports any errors to the microprocessor. When the microprocessor has a frame to send on the network, it writes an entry in the LANCE transmit descriptor ring in DELUA memory and then sets the transmit demand bit in the LANCE control and status register 0. The LANCE waits until there is a pause in the message traffic on the network and then sends the frame. The LANCE adds the preamble and CRC fields to the frame as it sends it. If the frame collides with a frame from another node, the LANCE waits and then tries again (up to 16 tries). After sending the frame, the LANCE writes status into the transmit descriptor ring entry in DELUA memory and interrupts the microprocessor. The LANCE mode register provides a number of special features for diagnostic testing. The LANCE can loop data frames inside the LANCE subsystem or out onto the network cable and back. It can force a collision to test the collision detection circuitry. It can also disable the CRC generation circuitry. This allows a diagnostic test to send frames with correct and incorrect CRC fields to test the LANCE CRC detection circuitry. 1.5.4 Direct Memory Access (DMA) Subsystem The DMA subsystem transfers data between DELUA memory and host memory. The DMA subsystem comprises a word mover and a block mover. The word mover transfers one word from host memory to DELUA memory, or from DELUA memory to host memory. The block mover transfers a block of contiguous words. The word mover and the block mover can operate simultaneously. The microprocessor uses the word mover to read ancillary functions, addresses, and pointers from host memory and to write status words into host memory. It uses the block mover to write frames it has received on the network into host memory and to read frames from host memory to transmit on the network. To transfer a word or a block of words between internal memory and host memory, the microprocessor writes registers in the DMA subsystem to specify the internal memory address, the host memory address, the number of words to be transferred, and the direction of transfer. The DMA subsystem interrupts the microprocessor when the transfer is complete. 1.5.5 Port Control and Status Register (PCSR) Subsystem The DELUA has four port control and status registers for communication with the host. Inside the DELUA, the microprocessor has direct access to only PCSRO. PCSR1, PCSR2, and PCSR3 are not connected to the internal bus. The microprocessor uses the DMA word mover to read and write these registers by way of the UNIBUS. 1-9 1.6 SPECIFICATIONS Table 1-1 lists the DELUA specifications. Table 1-1 DELUA Specifications Specification Description Operating Mode Half-duplex Data Format Ethernet specification Data Rate (Physical Channel) 10M bits/sec UNIBUS Loading 1 dc load 4 ac loads DC Power Requirements +5+40.25V,8 A —15 V, 1 A (for transceiver) Physical Size M7521 Module Height (hex): 21.4 cm (8.4 in) Length: 39.8 cm (15.7 in) Bulkhead Assembly Height: 10.6 cm (4.0 in) Length: 10.6 cm (4.0 in) Operating Environment Temperature 10° to 50°C (50° to 122°F) Relative Humidity 10% to 90% (noncondensing) Wet-Bulb Temperature 28°C (82°F) maximum Dew Point 2°C (36°F) Altitude Sea level to 2.4 km (8000 ft) Shipping Environment Temperature —40°C to 66°C (—40 to 151°F) Rate of Change 20°C/hr (36°F/hr) maximum Relative Humidity 0% to 95% (noncondensing) Altitude Sea level to 9 km (30,000 ft) 1-10 1.7 RELATED DOCUMENTS Table 1-2 lists related documents. Table 1-2 Related Documents Title Order Number DELUA Technical Description EK-DELUA-TD H4000 Technical Description EK-H4000-TM The Ethernet, A Local Area Network, Data Link Layer, AA-K759B-TK Ethernet Installation Guide EK-ETHER-IN Network Interconnect Exerciser User's Guide AA-HIO6A-TE Introduction to Local Area Networks EB-22714-XX DELUA Maintenance Print Set MP-01787-01 and Physical Layer Specifications DIGITAL personnel may order printed documents from: Digital Equipment Corporation 444 Whitney Street Northboro, MA 01532 . Attention: Publishing and Circulation Services (NR03/W3) Order Processing Section Customers may order printed documents from: Digital Equipment Corporation Accessories and Supplies Group Cotton Road Nashua, NH 03060 For information call: 1-800-257-1710. Information concerning microfiche libraries may be obtained from: Digital Equipment Corporation Micropublishing Group (BUO/E46) 12 Crosby Drive Bedford, MA 01730 CHAPTER 2 INSTALLATION This chapter provides the information necessary for installing a DELUA in a PDP-11 or VAX host | system. PREINSTALLATION CONSIDERATIONS 2.1 The following factors should be considered before installing a DELUA: e e e Backplane requirements Bus latency constraints Bus loading factor Backplane Requirements 2.1.1 : slot that can be configured for The DELUA requires one hex-height, small peripheral controller (SPC)(REV E) or later] can accept a nonprocessor request (NPR) operations. Any SPC backplane [DD11-B DELUA module. The DELUA module can be placed anywhere on the UNIBUS system, but before all UNIBUS repeaters. Bus Latency Constraints 2.1.2 ssor request For the DELUA, bus latency is the delay between the time the DELUA raises the nonproce which allows it signal, (NPR) UNIBUS signal line and the time it receives the nonprocessor grant (NPG) when it is reading and to transfer a word on the UNIBUS. Excessive bus latency will slow the DELUA the DELUA is Since writing words from the host processor’s memory using direct memory access (DMA). a very well-buffered device, it is unlikely to lose data due to excessive bus latency. and, thus, a A module in a UNIBUS backplane slot closer to the processor has a higher NPRe priority places the that slot backplan a lower bus latency. To obtain optimum DELUA performance, select optimum If . repeaters UNIBUS all DELUA module before all devices with a lower NPR rate and before before UNIBUS the on anywhere installed performance is not a requirement, the DELUA module can be all repeaters. Bus Loading Factor 2.1.3 Make sure that system loading capacities are not exceeded as a result of installing the DELUA. The DELUA ac and dc loads on the UNIBUS signal lines are as follow: ° ) UNIBUS dc loads - 1 UNIBUS ac loads - 4 2-1 The power consumption of the DELUA is shown in Table 2-1. Table 2-1 DELUA Power Consumption Power Supply Allowable Range Current Backplane Pin +5V —15 V (for transceiver) +4.75 Vto 525V ~14.25 V to —-15.75V 8 A 1 A CA2 FB2 2.2 UNPACKING AND INSPECTION To unpack a DELUA subsystem, remove the equipment from its shipping containers, verify that there are no missing parts, and inspect the equipment for damage. Report any damage or shortages to the shipper and notify the DIGITAL representative. 1. Before opening the shipping containers, check for external damage such as dents, holes, or crushed corners. CAUTION The M7521 module and the UNA bulkhead assembly are easily damaged by static electricity. To avoid damage, handle these parts only on the VelostatTM mat. When not in use, store these parts in their conductive plastic bags. 2. Open a Velostat static discharge system (CD kit no. A2-W0299-10) and unfold the mat. 3. Attach one end of the 4.5-meter (15-foot) ground cable to an electrical ground point in the host computer. Attach the other end to the mat snap fastener. 4. Attach the wrist strap to your wrist and clip the other end of the cable to the edge of the mat. 5. Open and unpack the shipping container. Check the contents against the parts shown in Figure 2-1. NOTE Keep the packing materials in case you must return parts. 6. Inspect each part for shipping damage. Check the modules carefully for cracks, breaks, or loose components, such as socketed chips. 2.3 PREINSTALLATION PREPARATION To prepare the DELUA for installation, perform the steps describedin Sections 2.3.1 through 2.3.5. Velostat is a trademark of the 3M Company. 2-2 A. M7521 MODULE Q e 2 Ej HARDWARE ~ CABINET KIT CKDELUA-KI I/0 PACKAGE (FOR NON-FCC-COMPLIANT CABINETS) , —— UNA S BLe UNA QUAD ASSEMBLY FRAME o -1 UNA BULKHEAD CABLE ASSEMBLY 70-18798-08 (8-FOOT CABLE) ”, | UNA BULKHEAD ASSEMBLY B. ONE OF THREE < CABINET KIT CKDELUA-KL CABINETS) e—— — UNA BULKHEAD CABLE ASSEMBLY 70-18798-04 (4-FOOT CABLE) UNA BULKHEAD ASSEMBLY CABINET KIT CKDELUA-KM (FOR FCC-COMPLIANT \. CABINETS) < UNA BULKHEAD CABLE ASSEMBLY C. USER'S 70-18798-08 GUIDE (8-FOOT CABLE) EK-DELUA-UG MKV85-0340 Figure 2-1 DELUA Component Parts 2-3 2.3.1 Backplane Preparations 1. If present, remove the grant continuity module from the slot for the DELUA. 2. If present, remove the nonprocessor grant (NPG) jumper wire that runs between backplane pins CA1 and CBI of the slot for the DELUA module. NOTE If at a later time you remove the DELUA module, be sure to either replace the NPG jumper wire and install a G727 single-height grant module, or install a G7273 dual-height grant module. 2.3.2 Device Address Assignment Set the device address of the first DELUA (or DEUNA) being installed in a system to 774510 by setting the switch pack at E106 as shown in Figure 2-2. For device address assignment purposes, the DELUA and the DEUNA are equivalent. The DELUA address of 774510 could overlap with the twenty-third DP11 (double-buffered synchronous line controller) if your system has 23 DP11 controllers. If it does, select another address for the DP11 controller from the floating address space described in Appendix A. NS e TM\ 0000 ~ Y 12345678910 L AAAMALAAY 1 1A12) - OFF —— 10 (A3) - OFF 2 (A11) - OFF 9 (A4) — ON 3 (A10) - ON 8 (A5) — ON 4 (A9) - ON — OFF 7 (A6) 5 (A8) — OFF 6 (A7) — ON MKVES 1321 Figure 2-2 Switch Pack at E106, Device Address Assignment For the second and any subsequent DELUA (or DEUNA) being installed in the same system, select the device address from the floating address space. If the system already has a DEUNA, select the DELUA device address from the floating address space. Figure 2-3 shows the correlation between address bits and switches in the switch pack at E106. Refer to Appendix A for information on determining the appropriate floating address. 2-4 LSB mMSB 15 14 13 1 1 1 12 1" 10 09 08 06 07 04 05 03 SWITCH PACK E106 | SWITCH NUMBER OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF 01 00 0 0 0 FLOATING ADDRESS 760010 760020 760030 760040 760050 760060 /60070 760100 , OFF OFF 02 OFF | OFF OFF 760200 760300 760400 OFF OFF OFF OFF QFF OFF 760500 760600 OFF 760700 761000 OFF OFF 762000 OFF | OFF 763000 OFF 764000 MKV85-1836 Figure 2-3 2.3.3 Device Address and Switch Positions Vector Address Assignment Set the vector address of the first DELUA (or DEUNA) being installed in a system to 120 by setting the switch pack at E69, as shown in Figure 2-4. For vector assignment purposes, the DELUA and the DEUNA are equivalent. For the second and any subsequent DELUA (or DEUNA) being installed in the same system, select the vector address from the floating vector address space. If the system already has a DEUNA, select the DELUA vector address from the floating vector address space. Figure 2-5 shows the correlation between vector address bits and switches in the switch pack at E69. Refer to Appendix A for information on determining the appropriate floating address. 2-5 AA N VT T 4 (VO8) - ON — 10 (VO2) - ON 5(v07) - ON —— 9 (VO3) — ON 6 (VO6) — OFF 8 (V04) — OFF 7 (VO5) — ON MKV85-1832 Figure 2-4 Switch Pack at E69, Vector Address Assignment FLOATING V§CTOR ASSIGNMENT"TABLE fl 13 0 | 12 | 1 10 1 09 1 08 0 0 ) 0 0 nomeer | |06 | 05 04 | 03] 02101 SWITCH PACK E69 l SWITCH | 07 N | | S [ 6 | 7] 0 I FLOATING |0 [T OFF | OFF o0 OFF 300 304 OFF | OFF OFF 310 OFF | OFF OFF | OFF 314 OFF | OFF ~| oo 0 | 8 | 9 | OFF | OFF f~—u OFF_] 320 OFF | OFF OFF OFF | OFF OFF | OFF 330 OFF | OFF OFF | OFF | OFF 334 OFF 344 OFF | OFF | OFF OFF OFF | OFF | OFF 350 OFF | OFF 354 OFF 364 OFF | OFF | OFF | OFF | OFF | OFF 374 OFF OFF | OFF | OFF 340 OFF | OFF | OFF OFF | OFF | OFF | OFF 360 OFF | OFF | OFF | OFF OFF | OFF | OFF | OFF | OFF OFF OFF 324 370 400 OFF 500 OFF | OFF 600 OFF | OFF | OFF 700 MKV85-1833 Figure 2-5 Vector Address and Switch Pogitions 2-6 2.3.4 Boot Option Selection (PDP-11 Host Systems Only) At the request of another node, a DELUA installedin a PDP-11 host can load the host operating system. Switch settings on the DELUA module determine whether the DELUA loads the host by transferring the operating system software across the network from another node, or signals the host to load itself from its own mass storage system. The DELUA cannot load a VAX host. The DELUA can be set up to perform a remote boot on powerup with the optional M9312 boot module and ROM set, order number MR 11K-AE. During powerup, the DELUA loads the host operating system by transferring the operating system software across the network from another node. When installing a DELUA into a PDP-11 host system, set switches 2 and 3 of the switch pack at E69 for the boot function desired. Figure 2-6 shows switches 2 and 3. Table 2-2 lists the switch settings and boot functions. Section 5.1 provides additional information on remote boot functions. When installing a DELUA into a VAX host system, set switches 2 and 3 on the switch pack at E69 to the ON (disabled) position. Figure 2-6 shows switches 2 and 3. Table 2-2 Boot Function Switches (PDP-11 Only) Switch 2 Switch 3 Boot Function ON ON OFF OFF ON OFF ON OFF Remote boot disabled Remote boot from system boot ROM Remote boot and system load Remote boot disabled 2.3.5 Loop Selftest Switch (for Manufacturing Use) Disable the loop selftest feature by setting switch 1 on the switch pack at E69 to the ON position as shown in Figure 2-7. Enabling the loop selftest feature does not cause the selftest to start, but once it is started (such as by a powerup) the selftest will loop continuously. 2-7 r¥ y4 ¥ > r% Iooooij 12345678910 3 (BOO SEL T 1) - 2 (BOO SEL T 0) MKV85-1834 Figure 2-6 Boot Function Switches B .4 ~s .4 rVe Co oo fizfi’//////7 0000 | 1 (SELFTEST LOOP) —ON MKVg5-1835 Figure 2-7 Loop Selftest Switch Setting 2.4 INSTALLATION Perform the steps shown in Figure 2-8 to install the DELUA. Plugged Hole 1. Install the UNA bulkhead cable. Note the plugged hole in the BergTM connector on the UNA bulkhead cable. Plug the connector into J3 on the DELUA module. 2. Install the DELUA module. Install the DELUA (M7521) module in the selected backplane slot. NOTE Remove the NPR jumper (CA1l to CB1) before installing the DELUA module. You must reinstall this jumper if you remove the DELUA module from the system. 3. Install the UNA bulkhead (FCC-compliant bulkhead panel). Remove the blank bulkhead panel and install the UNA bulkhead assembly. MKV85-1839 Figure 2-8 DELUA Installation Procedure (Sheet 1 of 2) Berg is a trademark of Berg Electronics. 2-9 Install the UNA bulkhead (non-FCC-compliant bulkhead panel). a. Locate the two 10-32 screws and u-nuts. b. Slip the u-nuts onto the cabinet frame. |\\5NN\ 4. Secure the I/O bulkhead metal frame to the cabinet frame. Install the UNA bulkhead assembly into the metal frame. S. Connect the UNA bulkhead cable to the bulkhead assembly. a. Unlock the latch on the cable D connector. Connect the cable to J2 on the component side of the UNA bulkhead assembly. Slide the latch on the D connector to the locked position. N » MKV85-1840 Figure 2-8 DELUA Installation Procedure (Sheet 2 of 2) 2-10 2.5 . VERIFICATION CHECKS Perform the following tests to verify that the DELUA is operating correctly. For these tests the DELUA must be attached to the network or to an H4080 loopback transceiver as shown in Figure 2-9. The H4080 loopback transceiver is not included with the DELUA. NOTE DIGITAL personnel may obtain the H4080 loopback transceiver through their local DIGITAL Field Service branch office. Customers may obtain the H4080 through their local DIGITAL Sales Representative. UNA BULKHEAD ASSEMBLY DIGITAL ETHERNET LOOPBACK CONNECTOR TRANSCEIVER CABLE MKV85-0325 Figure 2-9 Loopback Transceiver Setup 2-11 2.5.1 Postinstallation Power Check Turn on the system power and verify that the voltages at backplane pins CA2 and FB2 are in accordance with those listed in Table 2-3. If necessary, adjust the power supply voltages. Table 2-3 Power Supply Allowable Range Backplane Pin +5V +4.75 Vto 5.25 V —~14.25 Vto -15.75V CA2 —15 V (for transceiver) 2.5.2 DELUA Power Check FB2 Light-Emitting Diode (LED) Checks I. Turn on the system power. Note that the DELUA must be connected to the network or to a loopback test transceiver. 2. The LEDs on the DELUA module will cycle indicating that the selftest diagnostic (see Figure 2-10). The selftest takes about 15 seconds to complete. is running When the test completes successfully, LED D8 should be on indicating that the DELUA is in the ready state. The activity LED, D5, may also be flickering. If any other LEDs are on, the selftest has found an error. Table 6-1 shows the LED 3. status codes. Check that the UNA bulkhead assembly LED shown in Figure 2-11 is lighted. This LED is lighted by the —15-volt power supply that powers the transceiver. 2.6 DIAGNOSTIC ACCEPTANCE PROCEDURE The final step in the DELUA installation procedure is to exercise the DELUA on the UNIBUS and on the network. Run the appropriate diagnostics for the VAX or PDP-11 system as listed in Table 2-4. To run the PDP-11 diagnostics, CZUAD and CXUAD, the DELUA must be connecte d to a loopback transceiver. These diagnostic programs assume that the only messages to and from the transceiver are the messages they have sent. If the DELUA is connected to a network and the diagnost ic receives a message sent by another node on the network, it reports errors. Run each diagnostic for at least five passes. To run the network interconnect exerciser (NIE) program, the DELUA must be connected to the network. Refer to the Network Interconnect Exerciser User's Guide (order number AA-HIO6A-TE) for further information. Table 2-4 DELUA Diagnostics PDP-11 VAX Diagnostic Host System Host System Functional CZUAD (Stand-Alone) EVDYB (Level 2R On-Line) DEC/X-11 CXUAD (Stand-Alone) None NIE CZUAC (Stand-Alone) EVDWC 2-12 NN LRI NERRR mmm NOTE: LED D2 IS NOT USED. MKV8S-1841 Figure 2-10 DELUA LEDs MKV85.0327 Figure 2-11 Bulkhead LED 2-13 CHAPTER 3 PROGRAMMING OVERVIEW 3.1 INTRODUCTION The operation of the DELUA is controlled by a program in host memory called the port driver. The port driver controls the DELUA in two ways: with port commands written to the four control and status registers, and by ancillary commands written into shared data structures in host memory. Figure 3-1 shows the DELUA control and status registers and the different data structures in host memory. 3.2 PORT COMMAND EXECUTION Port commands are used to start and stop the DELUA, to tell it to read and execute an ancillary function in host memory, and to tell it to transmit a message on the network. The host processor issues a port command by writing bits (03:00) of the port control and status register 0 (PCSR0). The DELUA responds by executing the port command and setting the done interrupt (DNI) bit or the port command error interrupt (PCEI) bit. 3.3 ANCILLARY FUNCTION EXECUTION The host processor issues an ancillary function by writing to a data structure in host memory called the port control block (PCB) rather than directly to PCSR0. The PCB consists of four 16-bit words in host memory. Ancillary functions are used to read and write various addresses and pointers, and to read counters and extended status information in the DELUA. When the DELUA is initialized, the port driver gives the DELUA the starting address of the PCB by writing a GET PCBB port command to PCSRO. The following list shows a typical sequence of events when the DELUA executes an ancillary function: 1. The port driver writes (moves) the ancillary function to the PCB and, if necessary, sets up other memory data structures. 2. The port driver instructs the DELUA to fetch and execute the ancillary function by writing a GET COMMAND port command to PCSRO. 3. The DELUA uses direct memory access (DMA) to read the PCB and execute the ancillary function. 4. When the DELUA has finished, it notifies the host by setting the done interrupt (DNI) bit in PCSRO. J r——————— I mTennuprsT PORT COMMAND | PCSRO l I PORT CONTROL BLOCK ADDRESS | PSCR2 l ' I STATE | PCSR1 ZEROS l PCSR3 I L I | HOST MEMORY 1L SELF TEST UNIBUS DATA BLOCK PORT CONTROL BLOCK | PorT FuNcTION PORT FUNCTION PORT FUNCTION DEPENDENT DEPENDENT INFORMATION INFORMATION TRANSMIT DESCRIPTOR RING RECEIVE DESCRIPTOR RING BUFFER LENGTH BUFFER ADDRESS BUFFER LENGTH 15T BUFFER ADDRESS ENTRY STATUS & ERROR STATUS & ERROR INFORMATION INFORMATION * L] . [ ENTRY N TMTM ENTRY L] BUFFER LENGTH BUFFER ADDRESS | L] 157 BUFFER LENGTH N TMTM ENTRY BUFFER ADDRESS STATUS & ERROR INFORMATION STATUS & ERROR INFORMATION TRANSMIT DATA BUFFER RECEIVE DATA BUFFER = | | | I I I I | I | | I I I I - —_——e 2Eo$t’)TngsAsTlo ' DESTINATION N ADDRESS SOURCE RCE i%%nsss ADDRESS TYPE FIELD —— DATA DATA FIELD FIELD CRC MKV85-1837 Figure 3-1 DELUA PCSRs and Host Memory Data Structures 3.4 DATA FRAME TRANSMISSION AND RECEPTION The DELUA transmits and receives message frames directly between the network and the host’s memory with DMA operations. The port driver tells the DELUA where to get frames to transmit and where to place frames it has received by means of transmit and receive descriptor rings in host memory. The transmit descriptor ring contains a number of entries. Each entry specifies the length and starting address of a data buffer in host memory. If the ownership bit in one or more of the transmit descriptor ring entries is set, the DELUA reads the specified data buffers and transmits them on the network. 3-2 Each entry specifies the length and starting The receive descriptor ring also contains a number of entries.DELUA receives a frame on the network, it the When . address of a receive data buffer in host memory writes the frame into one of these receive data buffers. writes an entry in the transmit descriptor ring for When the host has frames for the DELUA to transmit, itand starting address of the transmit data buffer. each frame. In each entry the host specifies the length entry. The host then writes the The host also sets the ownership bit in the transmit descriptorNGring DEMAND port command causes the POLLING DEMAND port command into PCSRO. The POLLI the DELUA finds an entry with the DELUA to read the entries in the transmit descriptor ring. asWhen on the network. The DELUA can ownership bit set, it transmits the contents of the data buffer a frame a single longer frame. If the end-ofalso chain together the contents of several transmit data buffers into the next data buffer to form a longer frame bit in the descriptor ring entry is not set, the DELUA appends frame until it encounters a frame. The DELUA continues appending data buffers into a singlehaslong transmitted the frame, it writes descriptor ring entry with the end-of-frame bit set. After the DELUA DELUA then continues to read entries in status information into the transmit descriptor ring entry. The ip bit set. After the DELUA has the transmit descriptor ring looking for more entries with the ownersh ted the associated data found all of the descriptor ring entries with the ownership bit set and transmit host. buffers, it sets the transmit ring interrupt bit in PCSRO, which interrupts the setting the ownership bit in each receive The host allocates receive data buffers for use by the DELUAthebynetwork , it writes the frame data into the descriptor ring entry. When the DELUA receives a frame on large enough to fit the entire frame, the next allocated receive data ‘buffer. If the data buffer is not frame. sets the start-of-frame bit in the DELUA fills successive receive buffers until it completes the end-of-Itframe bit in the receive descriptor receive descriptor ring entry for the first buffer and it sets the bit in the receive descriptor ring entry and ring entry for the last buffer. The DELUA clears the ownership sets the receive interrupt bit in PCSRO, which interrupts the host. 3.5 FUNCTIONAL STATES 1. These states are described in Table The DELUA reports its functional state with bits (03:00) of PCSR ' 3-1. Table 3-1 Functional State Running Functional States Description port command in The DELUA enters the running state when it receives the START following functions: PCSRO. When in the running state, the DELUA performs the e Transmits and receives frames on the network e Responds to port commands from the host e Maintains internal counters e Loops frames when requested by another node e Sends system ID frame e Accepts a remote boot frame from another node if the boot select switch is enabled Table 3-1 Functional State Functional States (Cont) Description Ready The DELUA enters the ready state after powerup, remote boot, or after receiving a STOP port command. When in the ready state, it does not transmit or receive message frames, but it does perform the following functions: e Responds to port commands from the host e Maintains internal counters e Loops frames when requested by another node e Sends system ID frame e Accepts a remote boot frame from another node if the boot select switch is enabled Reset The DELUA enters the reset state during powerup, when it receives the UNIBUS initialization signal, or when the host sets the RESET bit in PCSRO. During the reset . Primary Load state, the DELUA clears its internal registers and counters. It also runs its selftest diagnostic if it has not already successfully run since the last powerup. If selftest is successful, the DELUA enters the ready state. The DELUA enters the primary load state when it is requested to load the host operating system. This happens when the DELUA receives a BOOT port command in PCSRO or a boot frame from another node. The DELUA transmits a request program frame and then waits for a memory load with transfer address frame from another node. The memory load with transfer address frame contains the secondary loader program that the DELUA loads into its internal memory. When in the primary load state, the DELUA also performs the following functions: e Maintains internal counters ® Loops frames when requested by another node e Sends system ID frame ® Accepts a remote boot frame from another node after it has been in the primary load state for 40 seconds or more Secondary Load The DELUA enters the secondary load state when the primary loader has loaded the secondary loader program from another node into DELUA internal memory. The secondary loader program loads a tertiary loader program from another node into host memory and starts it. Table 3-1 Functional State Port Halted UNIBUS Halted Functional States (Cont) Description port command in The DELUA enters the port halted state when it receives a HALT . In the port PCSRO. The host uses this state to write new microcode into the DELUA on the network halted state, the DELUA does not transmit or receive any frames ds, but the including maintenance frames. The DELUA responds to port comman the UNIBUS only way to get the DELUA out of the port halted state is with DELUA at an initialization signal, the RESET bit in PCSRO, or by starting thefunctio n code 1. y ancillar dress microad start the with appropriate microcode routine error in its The DELUA enters the UNIBUS halted state when it detects a fatal internal DMA system. When in the UNIBUS halted state, the DELUA also performs the following functions. e Responds to the RESET bit in PCSRO e Loops frames when requested by another node e Sends system ID frame The DELUA only responds to the UNIBUS initialization signal or the RESET bit in PCSRO. NI Halted The DELUA enters the network interconnect (NI) halted state when it detects a fatal error in its internal LANCE system. The DELUA accepts port commands. It also responds to the UNIBUS initialization signal or the RESET bit in PCSRO. NI and UNIBUS Halted internal The DELUA enters the NI and UNIBUS halted state when it detects a fatal the RESET error. The DELUA only responds to the UNIBUS initialization signal or bit in PCSRO. Table 3-2 provides a summary of the events that cause the DELUA to make a transition from one functional state to another. Table 3-2 Functional State Transition Summary From State Transition Event To State Any State Powerup Reset Reset Selftest ran successfully Ready Selftest failure - DMA system UNIBUS Halted Reset Reset RESET bit in PCSRO set UNIBUS initialization Selftest already ran successfully Selftest failure — LANCE system Selftest failure — any other type of internal failure UNIBUS initialization signal Ready NI Halted NI and UNIBUS Halted Reset Reset RESET bit in PCSRO set 3-5 Table 3-2 Functional State Transition Summary (Cont) From State Transition Event To State Primary Load Received memory load with transfer address frame Fatal UNIBUS error Fatal internal error UNIBUS initialization signal RESET bit in PCSRO set Secondary Load UNIBUS Halted NI and UNIBUS Halted Reset Reset Port driver START command Port driver BOOT command Running Primary Load Ready Boot frame (with remote boot switch enabled) Fatal UNIBUS error Fatal internal error UNIBUS initialization signal RESET bit in PCSRO set Port driver HALT command Running Port driver STOP command Boot frame (with remote boot Ready Fatal UNIBUS error Primary Load UNIBUS Halted NI and UNIBUS Halted switch enabled) Fatal internal error UNIBUS initialization signal RESET bit in PCSRO set Port driver HALT command Port Halted UNIBUS initialization signal RESET bit in PCSRO set Start microaddress ancillary function code 1 Fatal UNIBUS error Fatal internal error UNIBUS Halted Primary Load UNIBUS Halted NI and UNIBUS Halted Reset Reset Port Halted Reset Reset Port Halted Reset Reset State entered depends on microaddress UNIBUS Halted NI and UNIBUS Halted Fatal internal error UNIBUS initialization signal RESET bit in PCSRO set Reset NI Halted Fatal UNIBUS error Fatal internal error UNIBUS initialization signal RESET bit in PCSRO set NI and UNIBUS Halted NI and UNIBUS Halted Reset Reset NI and UNIBUS Halted UNIBUS initialization signal RESET bit in PCSRO set Reset NI and UNIBUS Halted Reset Reset Table 3-3 provides a summary of the state of the internal information retained or reset by the DELUA when making a transition from one state to an other. 3-6 Table 3-3 State Entered Reset | State Information Retention Summary State Changes Resets the following: Ring formats Counters Physical address Multicast address list Status register Ring pointers [nternal memory Load server address System 1D PCSRs Mode register Primary Load State State information retained depends on the action of the down-line loaded software. Ready Retains the following: Ring formats Counters Physical address Multicast address list Mode register Status register Internal memory Load server address System 1D PCSRs Running Retains everything, resets nothing. Port Halted Retains the following: Ring formats Counters Physical address Multicast address list Mode register Status register Internal memory Load server address System ID PCSRs UNIBUS Halted Immaterial because you cannot read any status with the UNIBUS halted. All ways of clearing the UNIBUS halted state involve the reset state. NI Halted DELUA only enters the NI halted state after executing selftest. All status is cleared at this time. 3-7 3.6 POWERUP AND RESET . When the DELUA is turned on, it executes its built-in selftest diagnostic. If the DELUA enters the ready state. If it fails the test, it enters the UNIBUS halted, passes the test, it NI halted, or NI and UNIBUS halted state. It displays the failing error code with the LEDs on the edge of the module (see Table 6-1) and also attempts to report the error code in PCSR1. The DELUA performs a reset operation when the host sets the reset bit in PCSRO or when it detects the UNIBUS initialization signal. The DELUA runs selftest only if it failed selftest the last time it ran. If selftest passed last time, the DELUA just clears its registers and counters and enters the ready state. The following list describes the status of the DELUA registers after powerup I. The 2. The multicast address list is empty. 3. The lengths of both the transmit and receive descriptor rings are DELUA physical manufacturing. address equals the default physical specification is invalid. 4. The mode register is clear. 5. The counters are zeros. 6. The DELUA responds to port commands. 7. The DELUA forwards loopback frames to another node. 8. The DELUA sends its system ID frame. 9. The DELUA accepts a remote boot frame from another or reset. address assigned during zero, indicating that the ring node. To set up the DELUA to receive and transmit frames on the network, the the host must perform the following steps. 1. The host enables interrupts by setting the interrupt enable 2. The host writes the base address of the port control bit in PCSRO. () The host writes a GET PCBB port command into PCSRO. This causes the DELUA to read the base address of the PCB from PCSR2 and PCSR3. The DELUA then sets the done interrupt in PCSRO. 4. The host clears the interrupt by writing the done hd block (PCB) into PCSR2 and PCSR3. The PCB is used as an extra set of registers in host memory for issuing ancillary functions to the DELUA. The host writes a write descriptor ring format ancilla ry function code into the PCB. The host also writes the base address of a structure called the UNIBUS data block (UDB) into the PCB. 6. The host writes descriptor ring information into the UDB. This information includes the base addresses and the number of entries in the transmi t and receive descriptor rings. 3-8 interrupt bit in PCSRO with a one. The host writes a GET COMMAND port command into PCSRO. This causes the DELUA to read the write descriptor ring format ancillary function from the PCB and store the appropriate descriptor ring information internally. The DELUA then sets the done interrupt in PCSRO. The host clears the interrupt by writing the done interrupt bit in PCSRO with a one. The host assigns a number of receive data buffers for use by the DELUA by writing the associated entries in the receive descriptor ring. In each entry, the host writes the base address and length of the receive data buffer and sets the ownership bit. 10. The host writes a START port command into PCSRO. This causes the DELUA to change from the ready state to the running state. The DELUA now receives frames addressed to it. The DELUA also transmits message frames when the host issues a POLLING DEMAND port command in PCSRO. The DELUA sets the done interrupt in PCSRO to acknowledge the START port command. 11. 3.7 The host clears the interrupt by writing the done interrupt bit in PCSRO with a one. STOP AND RESTART The host can stop the DELUA from transmitting and receiving frames by writing the STOP port command into PCSRO. This causes the DELUA to change from the running state to the ready state. If the DELUA is transmitting a frame on the network when it receives the STOP command, it finishes transmitting the frame. Otherwise, the DELUA does not transmit or receive any frames except system ID, boot, and loopback MOP frames. The host can restart the DELUA after a stop by writing the START port command into PCSRO. This causes the DELUA to change from the ready state to the running state. The following parameters remain e B ol ol e unchanged by a stop and restart operation. Ring formats Physical address Multicast address list Mode register Status register System ID parameters Internal memory microcode PCSRs 3.8 ANCILLARY FUNCTIONS THAT INTERFERE WITH MESSAGE PROCESSING Some ancillary functions affect the processing of messages by the DELUA. Table 3-4 shows which functions affect message throughput. 3-9 Table 3-4 Impact None* Portt None None None Ancillary Functions that Interfere with Messa ge Processing Function Code Function Description 0 No Operation Load and Start Microaddress Read Default Physical Address No Operation Read Physical Address 1 2 3 4 LANCE#} 5 None Write Physical Address 6 LANCE None PORT None None None LANCE None None None Read Multicast Address List 7 10 11 12 13 14 15 16 17 20 Port Write Multicast Address List Read Ring Format Write Ring Format Read Counters Read and Clear Counters Read Mode Write Mode Read Port Status Clear Port Status Dump Internal Memory 21 None Load Internal Memory 22 None None Read Load Server Address Write Load Server Address Read System ID Parameters 23 24 None 25 Write System ID Parameters Explanation of Impact terms: * None 1 Port There is no disturbance to the receive or The DELUA does NOT execute these state. These functions execute as a ancillary functions while it is in the runni ng NO-OP. The STOP PORT command before any of these ancillary functions $ LANCE transmit frame throughput. can be executed. must be issued Response to these ancillary functions requir e the DELUA to temporarily disengage from the network while the mode of the LANCE chip is being modified. The use of these commands can affect the data throu ghput of the DELUA. Unless it is absol utely . necessary, frequent use of these commands ° Reception parameters. The DELUA is not recommended. ignores all frames while modifying LANCE Frames that the LANCE has already processed and are in the internal memory buffers of the DEL UA are sent to the host memory in the normal manner. ® Transmission - The DELUA finish es transmitting the current frame before modifying LANCE parameters. 3-10 3.9 SUMMARY OF COMMANDS Tables 3-5, 3-6, and 3-7 summarize the DELUA commands and functions. DELUA Port Commands Table 3-5 Reference Command Description Section STOP The DELUA stops transmitting and receiving frames. 4.1 START The DELUA starts transmitting and receiving frames. 4.1 GET PORT CONTROL The DELUA reads the port control block (PCB) base 4.1 EXECUTE ANCILLARY The DELUA reads the ancillary function from the PCB 4.1 POLLING DEMAND The DELUA reads frames from host memory and 4.1 BOOT The DELUA loads its PDP-11 host operating system. 4.1 SELFTEST The DELUA runs its built-in selftest diagnostic. 4.1 HALT The DELUA stops all operations and waits for the host 4.1 BLOCK BASE ADDRESS FUNCTION address from the host. and executes it. transmits them on the network. to down-line load special microcode. Table 3-6 DELUA Ancillary Functions Reference Function Description Section Read Default 4.5.3 Physical Address Provides the host with the Ethernet physical address of the DELUA. Read/Write currently being used by the DELUA. 4.5.5 Physical Address Allows the host to read or change the physical address Read/Write table currently being used by the DELUA. 4.5.6 Multicast Address Allows the host to read or write the multicast address Read/Write Descriptor Ring Allows the host to read or write the current base address and lengths of the transmit and receive 4.5.7 Read/Write Mode Allows the host to read or set certain operating features 4.5.9 Table Format descriptor rings. of the DELUA that are used primarily for diagnostic testing. 3-11 Table 3-6 DELUA Ancillary Functions (Cont) Function Description Reference Section Read/Read and Clear Counters Allows the host to read and clear the error and status counters. 4.5.8 Read/Read and Clear Status Provides the host with extended statu 4.5.10 Allows the host to read and modify the DELUA 4.5.11 s information. Dump/Load Internal Memory microcode. Start Microaddress Allows the host to start execution of the DELUA microcode at a specified address. 4.5.2 Write System ID Parameters Allows the host to specify certain parameters that the DELUA sends in its system ID message. 4.5.12 Write Load Server Address Specifies the preferred node from which the DELUA should get the operating system, when it is booting its PDP-11 host operating system. Table 3-7 Function Selftest DELUA Maintenance Functions Reference Section Description The DELUA.executes its built-in diag nostic test when it receives the 4.1 The DELUA loops a frame on the network when it receives a 5.5 The DELUA sends a system ID frame on the network when 5.9 SELFTEST port command in PCS RO. Loop loopback frame from another Identification requested by another node. node. It also automatically sends frame about every ten minutes. Boot 4.5.13 The DELUA boots its PDP-1 | host processor. 3-12 a system ID 5.1 CHAPTER 4 REGISTERS AND COMMANDS PORT CONTROL AND STATUS REGISTER 0 (PCSR0) 4.1 Figure 4-1 shows the bit format of the PCSRO, and Table 4-1 describes the bit functions. 15 13 14 05 04 DN! | RCBI |FATL| USCI | INTR | INTE {RSET| O 1 12 SERI | PCEI | RXI | TXI 10 09 07 08 IR/CLlR/CL R/CL| R/CL{R/CL|R/CL|R/CL}R/CL R 06 R/W 00 03 PORT_COMMAND W R/W NOTE: R/CL = Read Access/ Write one to clear R = Read Only RW = Read/Write MKV85-1842 W=Write Only Figure 4-1 Table 4-1 Bit Name (15) SERI Port Control and Status Register 0 (PCSRO0) Bit Format Port Control and Status Register 0 (PCSRO0) Bit Descriptions Description Status Error Interrupt - Indicates that there is an error bit set in the DELUA extended status in bits (15:08) of word PCBB+2. Read this status information with the read and clear status, ancillary function codes 16/17. Interrupts the host. Cleared by writing with a one. (14) PCEI Port Command Error Interrupt — Indicates a function error or a UNIBUS timeout during the execution of a port command. PCSR1 (07) distinguishes between the two error conditions. Interrupts the host. Cleared by writing with a one. (13) RXI Receive Interrupt — Indicates that the DELUA has placed a frame in a receive data buffer in host memory. Interrupts the host. Cleared by writing with a one. (12) TXI Transmit Interrupt — Indicates that the DELUA has finished transmitting all the frames on the transmit ring or an error was encountered during a transmission. Interrupts the host. Cleared by writing with a one. (1) DNI Done Interrupt — Indicates that the DELUA has completed a port command. Interrupts the host. Cleared by writing with a one. 4-1 PCSRO Table 4-1 Port Control and Status Register 0 (PCSRO0) Bit Descript ions (Cont) Bit Name Description (10) RCBI Receive Buffer Unavailable Interrupt — Indicates that the DELUA has discarded an incoming frame because receive buffers were unavailable. This condition occurs when: 1. The DELUA does not own any more data buffers in host memory. The DELUA increments the receive frames lost — local buffer error counter in word UDBB+32 of the extende d status information. The host can read this extende d status information with the read and clear counters, ancillary function codes 12/13. 2. The DELUA has not been able to write receive data frames into host memory quickly enough and has run out of internal data buffers. The DELUA increments the receive frames lost — internal buffer error counter in word UDBB+30 of the extended status information. The host can read this extende d status information with the read and clear counters , ancillary function codes 12/13. Interrupts the host. Cleared by writing with a one. When receive data buffers are available again, the host must issue a POLLING DEMAND port command. (09) FATL Fatal Internal Error — Indicates that the DELUA has detecte d a fatal internal error. The status information in PCSR1 is invalid. Interrupts the host. Cleared by writing with a one. The host can attempt to clear the error condition by setting the reset bit (05). (08) USCI Unsolicited State Change Interrupt — Interrupts when the following occur in the DELUA: 1. Remote boot started — The DELUA receives a boot frame and enters the primary load state. 2. NI halted state — The DELUA detects an error in its LANCE subsystem and enters the NT halted state. These conditions are distinguished by examining the state field (03:00) of PCSRI. Interrupts the host. Cleared by writing with a one. (07) INTR Interrupt Summary — The logical OR of bits (15:08) . Interrupts the host. Cleared by clearing the appropriate error bit(s). (06) INTE Interrupt Enable - When clear, the DELUA does not interrupt the host. This bit and the port command field (03:00) cannot be written at the same time; two different instructions must be issued. 4-2 PCSRO Table 4-1 Port Control and Status Register 0 (PCSRO0) Bit Descriptions (Cont) Bit Name Description (05) RSET Reset — When set, initializes the DELUA. Note that reset also clears (04) Zero Zero. (03:00) PORT_COMMAND The port command field and the interrupt enable bit (INTE) (06) INTE bit (06). cannot be written at the same time; two different instructions must be issued. 0 0 0 0 NO-OP Causes no action. Does not set the 0 0 O 1 GET PCBB Instructs the DELUA to fetch the base address of the port control block (PCB) from PCSR2 and PCSR3. 0 0 1 0 GET CMD Instructs the DELUA to fetch and execute an ancillary function from the port control block (PCB). 0 0 1 1 SELFTEST Instructs the DELUA to enter the reset state and execute selftest. Selftest takes about 15 seconds. After executing selftest, the DELUA responds by setting the done interrupt bit (11), the unsolicited state change interrupt bit (08), or the fatal error DNI bit (11). interrupt bit (09). If selftest passes, the DELUA sets the done interrupt bit (11). If selftest fails, but the failure does not from DELUA the prevent sets it host, the with communicating the unsolicited state change interrupt bit {08). In this case, the failing error code is in PSCR1, and the DELUA responds to port commands. If selftest fails, and the failure from DELUA the prevents communicating with the host, the DELUA sets the fatal error interrupt bit (09). The error code information in PCSR1 is invalid. 4-3 PCSRO Table 4-1 Bit Name Port Control and Status Register 0 (PCSRO0) Bit Descriptions (Cont) Description 0 1 0 O START Causes the DELUA to enter the running state. If the DELUA is already in the running state, it does nothing but set the done interrupt bit (11). 0O 1 0 1 BOOT Instructs the DELUA to enter the primary load state and boot the host system. 0O 1 1 O NotUsed Reserved code, NO-OP, sets DNI. 0 1 1 1 NotUsed Reserved code, NO-OP, sets DNI. 1 0 0 0 PDMD Polling Demand - Instructs the DELUA to read the descriptor rings to determine if a free buffer has been placed on the receive ring or if a frame is ready for transmission on the transmit ring. 1 0 O 1 Not Used Reserved code, NO-OP, sets DNI. 1 0 1 0O Not Used Reserved code, NO-OP, sets DNI. 1 0 1 1 Not Used Reserved code, NO-OP, sets DNI. 1 1 0 0 Not Used Reserved code, NO-OP, sets DNI. I 1 0 1 Not Used Reserved code, NO-OP, sets DNI. 1 1 1 0 HALT Causes the DELUA to enter the port halted state. This is the best state for the host to write new microcode into the DELUA. The DELUA does not transmit or receive any messages including MOP messages. If the DELUA is transmitting a frame when it receives the HALT command, it may transmit only a partial frame. Cleared by setting the RESET bit (05), by the UNIBUS Iinitialization signal, or by starting the microcode at an appropriate address with the start microaddress, ancillary function code 1. 4-4 PCSRO Table 4-1 Port Control and Status Register 0 (PCSRO) Bit Descriptions (Cont) Description Name Bit 1 1 1 1 Suspends operation of the DELUA. STOP The DELUA goes from the running state to the ready state. If the DELUA is transmitting a frame, it finishes sending it. If the DELUA is not in the running state, the STOP command acts as a NO-OP and sets the done interrupt (DNI) bit (11). PCSR1 4.2 PORT CONTROL AND STATUS REGISTER 1 (PCSR1) PCSR1 is a read-only register. Figure 4-2 illustrates the bit format of PCSR1, and Table 4-2 describes the bit functions. 15 STER 07 08 14 ERROR CODE PCTO 06 05 iD 04 03 02 01 00 STATE MKV86-1843 Figure 4-2 Port Control and Status Register 1 (PCSR1) Bit Format 4-5 PCSR1 Table 4-2 Port Control and Status Register 1 (PCSR1) Bit Descriptions Bit(s) Field Description (15) STER Status or Selftest Error — Selftest or the operational microcode has detected an error. Bits (14:08) contain the error code. ERROR Status or Selftest Error Code — The error codes are listed in Table 6-1. (14:08) CODE Bits (14:08) correspond to LEDs (D3:D9). Note that the DELUA is unable to report errors in this register that involve the DMA system, internal memory, or interrupts. (07) PCTO Port Command Timeout — Valid only when the port command error interrupt (PCEI) bit (14) of PCSRO is set. When set, this bit indicates that a UNIBUS timeout occurred while the DELUA was executing a port command. When clear, indicates that the port command contained a function error. (06:04) ID Identification — Identifies the type of network controller. The DELUA returns 001. The DEUNA returns 000. (03:00) STATE Table 3-1 describes the functional states. 0 0 0 O O 0 0 1 Primary Load O 0 1 0 Ready 0 0 1 1 Running O 1 0 O Notused O 1 1 0 1 1 0 UNIBUS Halted NI Halted 0 Reset O 1 1 1 NIand UNIBUS Halted 1 0 0 O Port Halted 1 Not used (reserved for DELUA) Not used (reserved for DELUA) 0 0 1 10 1 0 1 1 0 1 1 1 0 O Not used (reserved for DELUA) Not used 1 1 0 1 Notused 1 1 1 0 Not used 1 1 1 1 Secondary Load 4-6 PCSR2 PORT CONTROL AND STATUS REGISTER 2 (PCSR2) 4.3 Figure 4-3 illustrates the bit format of PCSR2, and Table 4-3 describes the bit functions. 00 01 15 0 PCBB <15:01> MKV85-1844 Figure 4-3 Port Control and Status Register 2 (PCSR2) Bit Format Port Control and Status Register 2 (PCSR2) Bit Descriptions Table 4-3 Bits Name Description (15:01) PCBB Sixteen low-order address bits of the port control block (PCB) base address. (00) Zero The PCB base address must be on a word boundary. PCSR3 4.4 PORT CONTROL AND STATUS REGISTER 3 (PCSR3) Figure 4-4 illustrates the bit format of PCSR3, and Table 4-4 describes the bit functions. 15 0 0 0 0 0 0 0 0 0 0 0 0 0 00 02 01 0 PCBB <17:16> MKV85-1845 Figure 4-4 Port Control and Status Register 3 (PCSR3) Bit Format Table 4-4 Port Control and Status Register 3 (PCSR3) Bit Descriptions Bits Name Description (15:02) MBZ Must be zero. (01:00) PCBB (17:16) Two high-order bits of the port control block (PCB) base address. PCB NS PORT CONTROL BLOCK FUNCTIO uses to issue additional The port control block (PCB) is four 16-bit words in host memory that the hostwhere to find the PCB by DELUA the tells host The commands called ancillary functions to the DELUA. 4-5 describes the Table and format, bit PCB the shows issuing the GET PCBB port command. Figure 4-5 4.5 bit functions. 4-7 PCB 15 08 07 06 05 PORT FUNCTION DEPENDENT 03 02 01 00 PORT FUNCTION :PCBB+0 PORT FUNCTION DEPENDENT :PCBB+2 PORT FUNCTION DEPENDENT -PCBB+4 PORT FUNCTION DEPENDENT :PCBB+6 Figure 4-5 Table 4-5 04 Port Control Block (PCB) Bit Format Port Control Block (PCB) Bit Descriptions Word Bits Description PCBB+0 (15:08) Interpretation of these bits is dependent upon the PCB ancillary function field (07:00). PCBB+0 (07:00) These bits specify the ancillary function that the DELUA must perform PCBB+2 (15:00) Interpretation of these bits is dependent upon the ancillary function field. PCBB+4 (15:00) Interpretation of these bits is dependent upon the ancillary function field. PCBB+6 (15:00) Interpretation of these bits is dependent upon the ancillary function field. for the port driver. These are written by the port driver and unchange d by the DELUA. No-Op 0 4.5.1 No-Operation, Ancillary Function Code 0 Figure 4-6 shows the bit format, and Table 4-6 describes the bits for the no-operatio n function. 15 08 MBZ 07 06 05 04 03 02 01 00 0 0 0] 0 0 0 0 0 :PCBB+0 IGNORED :PCBB+2 IGNORED :PCBB+4 IGNORED :PCBB+6 TK-9061 Figure 4-6 No-Operation, Ancillary Function Code 0 Bit Format 4-8 No-Op 0 Table 4-6 No-Operation, Ancillary Function Code 0 Bit Description Word Bits Field Description PCBB+0 (07:00) OP CODE Op code = 0 - NO-OP Start Microaddress 1 4.5.2 Start Microaddress, Ancillary Function Code 1 n of the microcode that the This function is used by the port driver to instruct the DELUA to start executio loads the microcode with the load port driver has previously loaded into the DELUA. The port driver and Table 4-7 describes the internal memory, ancillary function code 21. Figure 4-7 shows the bit format, bit functions. o8 15 MBZ 07 06 05 04 03 02 01 00 0 0 0 0 0 0 0 1 | :pcBB+0 | IDBB <15:01> MBZ | :PCBB+2 IDBB <23:16> MBZ IGNORED :PCBB+4 .PCBB+6 MKV85-0344 Figure 4-7 Start Microaddress, Ancillary Function Code 1 Bit Format Table 4-7 Start Microaddress, Ancillary Function Code 1 Bit Descriptions Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 1 _ Load and Start Microaddress. Causes the DELUA to start executing from the microaddress supplied in words PCBB+2 and PCBB+4. PCBB+2 (15:01) IDBB Bits (15:01) of the internal data block base address from which PCBB+2 (00) MBZ Must be zero. The IDBB must be on a word boundary. PCBB+4 (15:08) MBZ Must be zero. PCBB+4 (07:00) IDBB Bits (23:16) of the internal data block base address from which (15:01) (23:16) the DELUA is to start executing. the DELUA is to start executing. 4-9 Read Default Physical Address 2 4.5.3 Read Default Physical Address, Ancillary Function Code 2 This function code allows the host to read the default Ethernet physical address during manufacturing. Figure 4-8 shows the bit format, and Table 4-8 describes 15 08 MBZ built into the DELUA the bit functions. 07 06 05 04 03 02 01 00 0 0 0 0 0 0 1 0/1 DPA <15:00> :PCBB+0 DPA <31:16>> :PCBB+2 DPA <47:32> :PCBB+4 :PCBB+6 MKV85-0350 Figure 4-8 Table 4-8 Read Default Physical Address, Ancillary Function Code 2 Bit Format Read Default Physical Address, Ancillary Function Code 2 Bit Descripti on Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 2 — Read default physical address out of the DELUA. PCBB+2 (15:00) DPA(15:00) The low-order 16 address bits of the default physical address. PCBB+4 (15:00) DPA(31:16) The middle-order 16 address bits of the default physical address. PCBB+6 (15:00) DPA(47:32) The high-order 16 address bits of the default physical address. No-Op3 4.5.4 No-Operation, Ancillary Function Code 3 This function causes no action in the DELUA. 4-10 Read/Write Physical Address 4/5 4.5.5 Read/Write Physical Address, Ancillary Function Codes 4/5 uses This function allows the port driver to read and write the Ethernet physical address that the DELUA Figure zero. be always must address physical any of for address comparison for incoming frames. Bit (00) 4-9 shows the bit format, and Table 4-9 describes the bit functions. 08 15 MBZ 07 06 05 04 03 02 01 00 0 0 0 0 0 1 0 0/1 | :PCBB+0 0 PA <15:00> :PCBB+2 PA <31:16> :PCBB+4 PA <47:32> :PCBB+6 TK-9067 Figure 4-9 Read/Write Physical Address, Ancillary Function Codes 4/5 Bit Format Table 4-9 Read/Write Physical Address, Ancillary Function Codes 4/5 Bit Descriptions Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 4 — Read the physical address out of the DELUA. Op code = 5 — Write the physical address into the DELUA. PCBB+2 (15:01) PA(15:01) Low-order address bits of the physical address. PCBB+-2 (00) PA(00) Must be zero for physical addresses. PCBB+4 (15:00) PA(31:16) Middle-order address bits of the physical address. PCBB+6 (15:00) PA(47:32) High-order address bits of the physical address. Read/Write Multicast Address List 6/7 4.5.6 Read/Write Multicast Address List, Ancillary Function Codes 6/7 multicast address table. A These two function codes enable the port driver to read and write the DELUA stations respond. The multicast address is an Ethernet address to which a group of logically related function causes ancillary list DELUA can store up to ten multicast addresses. The read multicast address the DELUA to write its current multicast address list into host memory. bit functions. Figure 4-11 shows the bit Figure 4-10 shows the bit format, and Table 4-10 describes theaddress in host memory. format of the multicast address list starting at the UDB base 4-11 Read/Write Multicast Address List 6/7 15 08 MBZ 07 06 05 04 03 02 01 00 0 0 0 0 0 1 1 0/1 uDBB <15:01> MLTLEN :PCBB+0 MBZ | :PCBB+2 MBZ <L1”7):?g> IGNORED :PCBB+4 :PCBB+6 TK-9063 Figure 4-10 Table 4-10 Read/Write Multicast Address List, Ancillary Function Codes 6/7 Bit Format Read/Write Multicast Address List, Ancillary Function Codes 6/7 Bit Descriptions Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 6 — Read multicast address table out of the DELUA. Op code = 7 - Write multicast address table into the DELUA. PCBB+2 (15:01) UDBB (15:01) UNIBUS data block base address bits (15:01). PCBB+2 (00) MBZ Bit (00) of the UNIBUS data block base must be zero. PCBB+4 (15:08) MLTLEN Multicast address table length. The number of multicast addresses to be read or written in the UNIBUS data block. Not more than 10. Since each address takes three words, the length of the UNIBUS data block is three times MLTLEN. Issuing the write multicast address ancillary function MLTLEN equal to 0 clears the multicast addresses. with If the host issues a read multicast address ancillary function with MLTLEN less than the number of multicast addresses in the DELUA, returns a truncated list. PCBB+4 (07:02) MBZ PCBB+4 (01:00) UDBB (17:16) the DELUA Must be zero. The high-order two address bits of the UNIBUS data block base. 4-12 Read/Write Multicast Address List 6/7 00 01 15 ‘UDBB+0 1 LA <15:01> LA <31:16> :UDBB+2 LA <47:32> :UDBB+4 T | | | LA 15 1 <15:01> . LA <31:16> :UDBB+0+ 3 MTLEN :UDBB+2+ 3 MTLEN :UDBB+4+ 3 MTLEN 132> LA <47:32 MKV85-0347 Figure 4-11 Multicast Address List UDB Bit Format Read/Write Descriptor Ring Format 10/11 4.5.77 Read/Write Descriptor Ring Format, Ancillary Function Codes 10/11 of the When initializing the DELUA, the port driver tells the DELUA the size, number, and location function. format ring descriptor write the with memory host transmit and receive descriptor ring entries in Issuing the read descriptor ring format function causes the DELUA to write the current value of these parameters into the UDB. Figure 4-12 shows the bit format, and Table 4-11 describes the bit functions of the read/write descriptor ring format function. Figure 4-13 shows the bit format, and Table 4-12 describes the bit functions of the descriptor ring format information starting at the UDB base address in host memory. 08 15 MBZ 07 06 05 04 03 02 01 00 0 0 0] 0 1 0 0 0/1 :PCBB+0 MBZ :PCBB+2 uDBB <15:01> IGNORED MBZ uDBB <17:16> :PCBB+4 IGNORED TK-9060 Figure 4-12 Read/Write Descriptor Ring Format, Ancillary Function Codes 10/11 Bit Format 4-13 Read/Write Descriptor Ring Format 10/11 Table 4-11 Read/Write Descriptor Ring Format, Ancillary Function Codes 10/11 Bit Description s Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 10 - Read descriptor ring specification out of the DELUA. Op code = 11 — Write descriptor ring specification into the DELUA. PCBB+2 (15:01) UDBB Bits (15:01) of the UNIBUS data block base address. (15:01) PCBB+2 (00) MBZ Bit (00) of the UNIBUS data block base address must be zero. PCBB+4 (15:08) IGNORED Not used. PCBB-+4 (07:02) MBZ Must be zero. PCBB+4 {01:00) UDBB The high-order two address bits of the UNIBUS data (17:16) 15 block base. 08 07 06 05 04 03 02 01 TDRB <15:01> TELEN 00 MBZ| MBZ <T15)fig> :UDBB+0 :UDBB+2 TRLEN :UDBB+4 RDRB <15:01> RELEN MBZ | :UDBB+6 MBZ RDRB <17.16> RRLEN | :UDBB+10 :UDBB+12 MKV85-0348 Figure 4-13 Read/Write Descriptor Ring Format UDB Bit Format 4-14 Read/Write Descriptor Ring Format 10/11 Table 4-12 Read/Write Descriptor Ring Format UDB Bit Descriptions Word Bits Field Description UDBB+0 (15:01) TDRB Address bits (15:01) of the transmit descriptor ring UDBB+0 (00) MBZ Must be zero. UDBB+-2 (15:08) TELEN Number of words in each entry in the transmit base. descriptor ring. TELEN must be greater than or equal to 4. UDBB+2 (07:02) MBZ Must be zero. UDBB+2 (01:00) TDRB The high-order two address bits of the transmit UDBB+4 (15:00) TRLEN Number of entries in the transmit descriptor ring. UDBB+6 (15:01) RDRB Address bits (15:01) of the receive descriptor ring base UDBB+6 (00) MBZ Must be zero. UDBB+10 (15:08) RELEN Number of words in each entry in the transmit ' (17:16) descriptor ring base address. address. descriptor ring. RELEN must be greater than or equal to 4. UDBB+10 (07:02) MBZ Must be zero. UDBB+10 (01:00) RDRB The high-order two address bits of the receive UDBB+12 (15:00) RRLEN Number of entries in the receive descriptor ring. Must (17:16) descriptor ring base. be 2 or more. Read and Clear Counters 12/13 4.5.8 Read/Read and Clear Counters, Ancillary Function Codes 12/13 The Read Counters function is used by the port driver to read the counters held by the DELUA. The read and clear counters function sets the counters to zero after reading them. Figure 4-14 shows the bit format, and Table 4-13 describes the bit functions. 4-15 Read and Clear Counters 12/13 15 08 MBZ 07 06 05 04 03 02 01 00 0 0 0 0 1 0 1 0/1 UDBB <15:01> MB2Z CTRLEN <15:01> :PCBB+0 MBZ | :PCBB+2 UDBB <17:16> . :P cBB +4 MBZ | :PCBB+6 MKV85-1853 Figure 4-14 Read/Read and Clear Counters, Ancillary Function Codes 12/13 Bit Format Table 4-13 Read/Read and Clear Counters, Ancillary Function Codes 12/13 Bit Descriptions Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 12 - Read counters out of the DELUA. Op code = 13 - Read counters out of the DELUA and clear counters. PCBB+2 (15:01) UDBB PCBB+2 (00) MBZ Bits (15:01) of the UNIBUS data block base. These are written by the port driver and unchanged by the DELUA. Bit (00) of the UNIBUS data block base. Must be Zero. PCBB+4 (15:02) MBZ Must be zero. PCBB+4 (01:00) UDBB The high-order address bits (17:16) of the UNIBUS data block base. PCBB+6 (15:01) CTRLEN Counter List Length — Length of the UNIBUS data block in words, up to 55 decimal. With a length of less than 55, the DELUA returns a truncated list. PCBB+6 (00) MBZ Must be zero. 4-16 Read and Clear Counters 12/13 Counter values are unsigned integers. Counters latch at their maximum values to indicate overflow. Figure 4-15 shows the bit format, and Table 4-14 describes the bit functions of the counter list starting at the UDB base address in host memory. 00 15 B UNIBUS DATA BLOCK LENGTH :UDBB+0 SECONDS SINCE LAST ZEROED <15:00> :UDBB+2 FRAMES RECEIVED <15:00> :UDBB+4 o .UDBB+6 FRAMES RECEIVED <31:16> :UDBB+10 MULTICAST FRAMES RECEIVED <15:00> - :UDBB+12 MULTICAST FRAMES RECEIVED <31:16> :UDBB+14 FRAMES RECEIVED WITH ERROR STATUS BITS OVRN |MLEN| FRAM} <15:04>=0 B FRAMES RECEIVED WITH ERROR <15:00> :UDBB+16 DATA BYTES RECEIVED <15:00> :UDBB+20 DATA BYTES RECEIVED <31:16> MULTICAST DATA BYTES RECEIVED <15:00> B B MULTICAST DATA BYTES RECEIVED <31:16> o .UDBB+22 :UDBB+24 ] :UDBB+26 RECEIVED FRAMES LOST- INTERNAL BUFFER ERROR <15:00> RECEIVE FRAMES LOST- LOCAL BUFFER ERROR <15:00> :UDBB+30 FRAMES TRANSMITTED <15:00> :UDBB+34 FRAMES TRANSMITTED <31:16> MULTICAST FRAMES TRANSMITTED <15:00> MULTICAST FRAMES TRANSMITTED <31:16> — CRC FRAMES TRANSMITTED - 3+ ATTEMPTS <15:00> FRAMES TRANSMITTED - 3+ ATTEMPTS <31:16> ‘UDBB+32 | .UDBB+36 :UDBB+40 | :UDBB+42 — :UDBB+44 .UDBB+46 MKV86-1855 Figure 4-15 Read/Read and Clear Counters UDB Bit Format (Sheet 1 of 2) 4-17 Read and Clear Counters 12/13 B B FRAMES TRANSMITTED - 2 ATTEMPTS <15:00> -UDBB4+50 FRAMES TRANSMIT - 2 ATTEMPTS TED <31:16> N :UDBB+52 FRAMES TRANSMITTED - DEFERRED <15:00> :UDBB+54 FRAMES TRANSMIT - DEFERRED TED <31:16> N :UDBB+56 DATA BYTES TRANSMITTED <15:00> B :UDBB+60 DATA BYTES TRANSMITTED <31:16> B :UDBB+62 MULTICAST DATA BYTES TRANSMITTED <15:00> B :UDBB+64 MULTICAST DATA BYTES TRANSMITTED <31:16> N :UDBB+66 TRANSMIT FRAMES ABORTED - BIT MAP <15:06> =0 LCOL|MLEN| :UDBB+70 © 0 |[LCAR|RTRY TRANSMIT FRAMES ABORTED <16:00> :UDBB+72 TRANSMIT COLLISION CHECK FAILURE <15:00> .UDBB+74 <15:00> = 0 :UDBB+76 PORT DRIVER ERROR <15:00> :UDBB+100 BABBLE COUNTER <15:00> :UDBB+102 MKV85-0351 Figure 4-15 Read/Read and Clear Counters UDB Bit Format (Sheet Table 4-14 2 of 2) Read/Read and Clear Counters UDB Bit Descriptions Word Name Description UDBB+0 UNIBUS Data Block Length Length in words of the UNIBUS data block. UDBB+2 Seconds Since Last Zeroed UDBB+4 UDBB+6 UDBB+10 UDBB+12 16 bits for the number of seconds since the counters were last zeroed. Frames Received 32 bits for the total number of error-free frames received. Multicast Frames Received 32 bits for the total number of error-free multicast frames received. 4-18 Read and Clear Counters 12/13 Table 4-14 Read/Read and Clear Counters UDB Bit Descriptions (Cont) Word Name Description UDBB+14 Frames Received with Error Status Indicates the types of receive errors that have occurred since the last time the counters were cleared. Bits Status Bits Name Bit(s) Description Not used. (15:04) (03) OVRN (02) MLEN Overrun Error - The DELUA lost part or all of one or more frames because the LANCE system was unable to write the data into internal memory as fast as it received the frame from the network. Overrun error is also reported by OVRN bit (12) of word RDRB+6 in the receive descriptor ring entry. Message Length Error — A frame was larger than 1518 bytes. FRAM (01y Framing Error - A frame did not contain a multiple of 8 bits. Also reported by FRAM bit (13) of word RDRB+4 in the receive descriptor ring entry. CRC (00 Block Check Error — A frame failed the CRC check. Also reported by CRC bit (11) of word RDRB+4 in the receive descriptor ring entry. UDBB+16 Frames Received 16 bits for the total number of frames received with one or with Error more¢ €rrors. 32 bits for the total number of data bytes received error-free. UDBB+20 UDBB+22 Data Bytes Received UDBB+24 UDBB+26 Multicast Bytes Received received. UDBB+30 Receive Frame Lost — Internal Buffer Error 16 bits for the total number of times there was a discard of an incoming frame due to lack of internal buffer space. Incoming frames must be error-free to be counted. 32 bits for the total number of error-free multicast data bytes 4-19 Read and Clear Counters 12/13 Table 4-14 Read/Read and Clear Counters UDB Bit Descriptions (Cont) Word Name Description UDBB+32 Receive Frames Lost — Local Buffer Error 16 bits for the total number of times there was a problem with a receive ring data buffer. This counter is incremented on one or more of the following occurrences: ° Buffer unavailable — A frame was lost because there was no available buffer on the receive ring. ) Buffer too small — A frame was truncated because it was larger than the available buffer space on the receive ring. UDBB+34 UDBB+36 Frames Transmitted 32 bits for the total number of frames successfully transmitted, including transmissions in which the collision test signal failed to assert. UDBB+40 UDBB+42 Multicast Frames Transmitted 32 bits for the total number of multicast frames successfully transmitted, including transmissions in which the collision test signal failed to assert. 32 bits for the total number of frames successfully transmitted on three or more attempts, including transmissions in which the collision test signal failed to assert. UDBB+44 Frames Transmitted UDBB+46 3+ Attempts UDBB+50 Frames Transmitted 2 Attempts 32 bits for the total number of frames successfully transmitted on two attempts, including transmissions in which the collision test signal failed to assert. UDBB+56 Frames Transmitted Deferred 32 bits for the total number of frames successfully transmitted on the first attempt after deferring, including transmissions in which the collision test signal failed to assert. UDBB+60 UDBB+62 Data Bytes Transmitted 32 bits for the total number of data bytes successfully transmitted, including transmissions in which the collision test signal failed to assert. UDBB+64 UDBB-+66 Multicast Bytes Transmitted 32 bits for the total number of multicast data bytes successfully transmitted, including transmissions in which the collision test signal failed to assert. UDBB+70 Transmit Frames Indicates the types of transmit errors that have occurred since the last time the counters were cleared. UDBB+52 UDBB+54 Aborted Status Bits Status Bits Bit(s) Name Description (15:06) Not Used Zero. 4-20 Read and Clear Counters 12/13 Table 4-14 Word Read/Read and Clear Counters UDB Bit Descriptions (Cont) Name Description (05) LCOL Late collision — A collision occurred after all nodes on the network should have known there was a frame being transmitted. Suggests that the collision detection circuitry of some node may have failed. Also reported in LCOL bit (12) of word TDRB+6 in the transmit descriptor ring entry. (04) MLEN Data block too long — The DELUA aborted a transmission because the frame exceeded the maximum frame size. h (03) Not Used Zero. (02) Not Used Zero. (01) LCAR Loss of carrier — Carrier went away while transmission was in progress. Also reported in LCAR bit (11) of word TDRB+6 in the transmit descriptor ring entry. (00) RTRY Excessive collisions — Retry error, 16 unsuccessful transmission attempts. Also reported in RTRY bit (10) of word TDRB+6 in descriptor ring entry. UDBB+72 Transmit Frames Aborted the transmit 16 bits for the total number of frames that were aborted during transmission for one or more of the errors reported in UDBB+70. UDBB+74 Transmit Collision Check Failure 16 bits for the total number of times the collision test signal failed to assert following an apparently successful transmission. The DELUA occasionally increments this counter when there has not been a collision test signal failure. The number of transmit collision checks that can be expected varies with network message traffic, but one check in 10,000 frames transmitted is typical. If the DELUA logs as many as one check in 100 frames transmitted, a fault in the network transceiver should be suspected. Some network transceivers made by other companies do not have a collision test signal. In this case, you will see one failure for every frame transmitted. 4-21 Read and Clear Counters 12/13 Table 4-14 Read/Read and Clear Counters UDB Bit Descriptions (Cont) Word Name Description UDBB+76 Not Used Zeros. UDBB+100 Port Driver Error 16 bits for the total number of times the host attempted to issue a port command or ancillary function while one was still being processed. UDBB+102 16 bits for the total number of times the LANCE truncated Babble Counter an excessively long frame transmission. The LANCE contains a timer that stops transmission if the transmitter is on for a time longer than the time to transmit a maximum length frame. Read/Write Mode Register 14/15 4.5.9 Read/Write Mode Register, Ancillary Function Codes 14/15 This ancillary function is used by the port driver to read or write the DELUA mode register. The mode register is used to program the operation of the DELUA while the DELUA is in the running state. Figure 4-16 shows the bit format, and Table 4-15 describes the bit functions. 15 14 13 12 11 10 09 08 MBZ PROM|ENALIDRDC|TPAD | ECT | MBZ [DMNT 07 06 05 04 03 02 01 00 0 0 0 0 1 1 0 01 MBZ INTL { MBZ | MBZ |DTCR|LOOP| MBZ | IGNR]| :PCBB+0 :PCBB+2 IGNORED :PCBB+4 IGNORED :PCBB+6 MKV85-0352 Figure 4-16 Read/Write Mode Register, Ancillary Function Codes 14/15 Bit Format Table 4-15 Read/Write Mode Register, Ancillary Function Codes 14/15 Bit Descriptions Word Bit(s) Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 14 - Read the mode out of the DELUA. Op code = 15 — Write the mode into the DELUA. 4-22 Read/Write Mode Register 14/15 Table 4-15 Read/Write Mode Register, Ancillary Function Codes 14/15 Bit Descriptions (Cont) Word Bit(s) Field Description PCBB+2 (15) PROM Promiscuous Mode - Instructs the DELUA to accept all incoming frames regardless of their destination address field. This bit is clear after powerup. PCBB+2 (14) ENAL Enable All - Instructs the DELUA to accept all incoming frames with multicast destinations. This bit is clear after powerup. PCBB+2 (13) DRDC Disable data chaining mode on received frames. When the DELUA is in this mode, it will truncate frames that do not fit in a single buffer. This bit is clear after powerup. PCBB+2 (12) TPAD Transmit Pad Enable — Causes the DELUA to add zeros to the data field of frames with a data field less than 64 bytes long. PCBB+2 (11) ECT Enable Collision Test — When set, the collision test error (CERR) bit (12) of word PCBB+2 of the extended status information generates an interrupt to the host. The host can read this extended status information with the read and clear status, ancillary function codes 16/17. This bit is clear after powerup. PCBB+2 (10) MBZ Must be zero. PCBB+2 (09) DMNT Disable Maintenance Message — Instructs the DELUA not to transmit a response to, and to discard all incoming loop, boot, and request ID messages. In addition, the DELUA does not issue the system ID message. This is an aid in running on-line diagnostics. PCBB+-2 (08:07) MBZ Must be zero. PCBB+2 (06) INTL Internal Loopback - Used with the LOOP (02) bit to determine where the loopback is to be done. Internal loopback allows DELUA/LANCE to receive its own transmitted frame. The frame size is limited to the silo size in the LANCE. The number of bytes that can be looped also depends on the state of the DTCR bit in the mode register. See Section 5.5. INTL is only valid if LOOP = 1. 4-23 Read/Write Mode Register 14/15 Table 4-15 Read/Write Mode Register, Ancillary Function Codes 14/15 Bit Descriptions (Cont) Description Field Bit(s) Word Loop Intl Loopback 0 0 Normal operation, no loopback Port command error External loopback Internal loopback 1 0 1 0 1 1 This bit is clear after powerup. PCBB+2 (05:04) MBZ Must be zero. PCBB+2 (03) DTCR Causes the DELUA to omit the CRC bytes when transmitting frames. Also disables the processing of maintenance messages such as loopback, system ID, and boot messages. This bit is clear after powerup. Causes the DELUA to receive frames that it transmits. LOOP (02) PCBB+2 The maximum frame size is 32 bytes if DTCR is O or 36 bytes if DTCR is a 1. See Section 5.5. Also disables the processing of maintenance messages such as loopback, system ID, and boot messages. This bit is clear after powerup. PCBB+2 (01) MBZ Must be zero. PCBB+2 (00) IGNORED This bit is ignored by the DELUA. Read and Clear Status 16/17 4.5.10 Read/Read and Clear Status, Ancillary Function Codes 16/17 This function is used by the port driver to read and clear status from the DELUA. Function code 17 clears the high byte of PCBB+2. Figure 4-17 shows the bit format, and Table 4-16 describes the bit functions. 15 14 13 11 12 09 10 MBZ ERRS|MERR|BABL|CERR|TMOT| 0 08 07 06 05 04 03 02 01 00 0 0 0 0 1 1 1 0/1 | :PCBB+0 |RRNG|TRNG|PTCH|RRAM RREV MAXMLT CURMLT MAXCTR :PCBB+2 :PCBB+4 :PCBB+6 MKV85-0322 Figure 4-17 Read/Read and Clear Status, Ancillary Function Codes 16/17 Bit Format 4-24 Read and Clear Status 16/17 Table 4-16 Read/Read and Clear Status, Ancillary Function Codes 16/17 Bit Descriptions Word Bit(s) Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 16 — Read status out of the DELUA. Op code = 17 - Read status out of the DELUA and clear status in the DELUA. PCBB+2 (15) ERRS Error Summary - Logical OR of MERR (14), BABL (13), CERR (12), TMOT (11), RRNG (09), and TRNG (08). Also sets SERI bit (15) in PCSRO, which generates an interrupt. PCBB+2 (14) MERR Multiple Errors — Indicates that one or more of the following error conditions reoccurred before the host read status with the read and clear status ancillary function: TMOT (11), RRNG (09), or TRNG (08). PCBB+2 (13) BABL Indicates that the transmitter has been on longer than the time required to send the maximum length frame. PCBB+2 (12) CERR Collision Test Error — The transceiver failed to send the collision test signal at the end of a transmission. Occasionally the DELUA detects this condition erroneously. See the transmit collision check failure counter in word UDBB+74 of the read and clear counters, ancillary function codes 12/13. This bit is only active when enabled by ECT, bit (11) of word PCBB+2 of the write mode register, ancillary function code 15. PCBB+2 (11) TMOT Timeout Error — UNIBUS timeout error encountered PCBB+2 (10) MBZ Must be zero. PCBB+2 (09) RRNG Receiver Ring Error — The DELUA encountered an error while accessing the receive descriptor ring. PCBB+2 (08) TRNG Transmit Ring Error — The DELUA encountered an (07) PTCH PCBB+2 while performing a ring access. This bit indicates that either a nonexistent UNIBUS address was accessed or the DELUA timed out waiting for a DMA request on the UNIBUS. error while accessing the transmit descriptor ring. ROM Patch - When set, indicates that a change or modification has been made to the DELUA operational microcode. 4-25 Read and Clear Status 16/17 Table 4-16 Read/Read and Clear Status, Ancillary Function Codes 16/17 Bit Descriptions (Cont) Word Bit(s) Field Description PCBB+2 (06) RRAM RAM Microcode Operational - The DELUA is PCBB+2 (05:00) RREV ROM Revision — The revision number of the DELUA PCBB+4 (15:08) CURMLT The current number of multicast addresses residing in PCBB-+4 (07:00) MAXMLT Maximum number of multicast addresses (10) the PCBB+6 (15:00) MAXCTR Maximum length in words of the data block reserved for executing out of RAM rather than ROM microcode. on-board microcode. the DELUA; zero upon powerup. DELUA will support. counters (34). Dump/Load Internal Memory 20/21 4.5.11 Dump/Load Internal Memory, Ancillary Function Codes 20/21 These functions allow the host to read the contents of DELUA internal memory and to write new microcode into DELUA internal memory. Figure 4-18 shows the bit format, and Table 4-17 describes the bit functions. Figure 4-19 shows the bit format, and Table 4-18 describes the bit functions of the associated parameters starting at the UDB base address in host memory. 08 15 MBZ 07 06 05 04 03 02 01 - 00 0 0 0 1 0 0 0 0/1 MBZ | :PCBB+2 UDBB <15:01> MBZ IGNORED :PCBB+0 uDBB <17:16> IGNORED -PCBB+4 :PCBB+6 TK-9973 Figure 4-18 Dump/Load Internal Memory, Ancillary Function Codes 20/21 Bit Format 4-26 Dump/Load Internal Memory 20/21 Table 4-17 Dump/Load Internal Memory, Ancillary Function Codes 20/21 Bit Descriptions Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 20 — Dump DELUA internal memory. Op code = 21 — Load DELUA internal memory. PCBB+2 (15:01) UDBB Address bits (15:61) of the UNIBUS data block base. PCBB+2 (00) MBZ Must be zero. PCBB+4 (15:08) IGNORED Ignored by the DELUA. PCBB+4 (07:02) MBZ Must be zero. PCBB+4 (01:00) UDBB The high-order address bits (17:16) of the UNIBUS data block base. PCBB+6 (15:00) IGNORED Ignored by the DELUA. 5 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 FLEN <15:01> MBZ | :UDBB+0 HDBB <15:01> MBZ | :UDBB+2 MBZ <$7D:?g> IDBB <15:01> MBZ :UDBB+4 MBZ | :UDBB+6 IDBB<23:16> :UDBB+10 MKV85-1851 Figure 4-19 Dump/Load Internal Memory UDB Bit Format 4-27 Dump/Load Internal Memory 20/21 Table 4-18 Dump/Load Internal Memory UDB Bit Descriptions Word Bits Field UDBB+0 (15:01) FLEN UDBB+0 (00) MBZ Must be zero. UDBB+2 (15:01) HDBB Host Data Block Base - Bits (15:01) of the starting UDBB+-2 (00) MBZ Must be zero. UDBB+4 (15:02) MBZ Must be zero. UDBB+4 (01:00) HDBB Host Data Block Base — Bits (17:16) of the starting UDBB+6 (15:01) IDBB Description Field Length — The number of words to be transferred between host memory and DELUA internal memory. address of the data buffer in host memory. address of the data buffer in host memory. Internal Data Block Base — Bits (15:01) of the starting address of the data buffer in the DELUA internal memory. The host can read addresses 0 to 1FFFE and 80000 to 83FFE. When the DELUA is in the port halted state, the host can write addresses 4400 to 1FFFE. When the DELUA is in the ready state, the host can only write addresses 4400 to 6400 hex. UDBB+6 (00) MBZ Must be zero. UDBB+10 (15:08) MBZ Must be zero. UDBB+10 (07:00) IDBB Internal Data Block Base — Bits (23:16) of the starting address of the data buffer in the DELUA internal memory. Read/Write System 1D 22/23 4.5.12 Read/Write System ID Parameters, Ancillary Function Codes 22/23 This function allows the host to read or write the parameters that the DELUA sends in the request program and system ID frames and the verification code for boot functions. Figure 4-20 shows the bit format, and Table 4-19 describes the bit functions. Figure 4-21 shows the bit format, and Table 4-20 describes the bit functions of the system ID parameter list that starts at the UDB base address in host memory. 4-28 Read/Write System ID 22/23 08 MBZ 07 06 05 04 03 02 01 00 0 0 0 1 0 0 1 0/1 UDBB <15:01> MBZ :PCBB+0 MBZ | :PCBB+2 UDBB | .pcBB+4 <17:16> PLTLEN :PCBB+6 MKV85-1852 Figure 4-20 Read/Write System ID Parameters, Ancillary Function Codes 22/23 Bit Format Table 4-19 Read/Write System ID Parameters, Ancillary Function Codes 22/23 Bit Descriptions Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 22 — Read system ID parameter list out of the DELUA. Op code = 23 - Write system ID parameter list into the DELUA. PCBB+-2 (15:01) UDBB The low-order address bits (15:01) of the UNIBUS data block base. PCBB+2 (00) MBZ Must be zero. PCBB+4 (15:02) MBZ Must be zero. PCBB+4 (01:00) UDBB The high-order address bits (17:16) of the UNIBUS data block base. PCBB+6 (15:00) PLTLEN System ID Parameter List Length — The length in words of the UNIBUS data block. The maximum value of PLTLEN is 100 decimal. When reading the system ID parameter list and the PLTLEN field is less than 100 (decimal) words, the DELUA returns, without error, a truncated list equal to the number asked for, starting with the first entry in the list. When reading or writing the system ID parameter list and the PLTLEN field is greater than 100 (decimal) words, the DELUA aborts the command and sets the appropriate error status. 4-29 Read/Write System ID 22/23 00 07 08 VC <15:00> 15 :UDBB+4 VC <47:32> :UDBB+6 VC <63:48> SOFTID MBZ -UDBB+10 UNDEFINED :UDBB+12 UNDEFINED :UDBB+14 UNDEFINED :UDBB+16 UNDEFINED :UDBB+20 UNDEFINED :UDBB+22 UNDEFINED :UDBB+24 TYPE :UDBB+26 :UDBB+30 CCOUNT CODE MBZ :UDBB+32 RECNUM :UDBB+34 MVTYPE :UDBB+36 MVLEN MVVER MVECO MVUECO :UDBB+40 :UDBB+42 :UDBB+44 FTYPE FLEN FVALT HATYPE <07:00> HALEN :UDBB+46 FVAL2 :UDBB+50 HATYPE <15:08> :UDBB+52 HA <15:00> :UDBB+54 HA <31:16> :UDBB+56 HA <47:32> :UDBB+60 DTYPE :UDBB+62 DLEN DVALUE :UDBB+64 PARAM :UDBB+66 PARAM :UDBB+70 PARAM :UDBB+72 i PARAM [ :UDBB+0 :UDBB+2 VC <31:16> | :ubsB+306 TK-9067 Figure 4-21 Read/Write System ID Parameters UDB Bit Format 4-30 Read/Write System ID 22/23 Table 4-20 Read/Write System ID Parameters UDB Bit Format Word Bits Field Description UDBB+0 (15:00) VC(15:00) Word 0 of the boot verification code. UDBB+2 (15:00) VC(31:16) Word 1 of the boot verification code. UDBB+4 (15:00) VC(47:32) Word 2 of the boot verification code. UDBB+6 (15:00) VC(63:48) Word 3 of the boot verification code. When the DELUA receives a boot frame, it checks the verification code in the boot frame against this verification code. If the codes do not match, the DELUA ignores the boot frame. If this code is zero, the DELUA accepts any verification code. The default value is zero. UDBB+10 (15:08) MBZ Must be zero. UDBB+10 (07:00) SOFTID Software Identification — Specifies the type of software the DELUA asks for in a request program frame in response to a BOOT port command in PCSRO. The default value is zero. UDBB+12 UDBB+14 UDBB+16 UDBB+20 UDBB+22 UDBB+24 (15:00) (15:00) (15:00) (15:00) (15:00) (15:00) Undefined Undefined Undefined Undefined Undefined Undefined UDBB+26 (15:00) TYPE The message type field that the DELUA sends in its system ID frame. The value is 260 hex. This is a readonly field. UDBB+30 (15:00) CCOUNT Character Count — The character count field that the DELUA sends in its system ID frame. This number should be 28 decimal plus the number of bytes in the additional parameters field in words UDBB+66 UDBB+306. UDBB+32 (15:08) MBZ Zeros. UDBB+32 (07:00) CODE Code — The code field that the DELUA sends in its system ID frame. The value is 7 indicating that the frame is a system ID frame. This is a read-only field. UDBB+34 (15:00) RECNUM Receipt Number — The receipt number field that the DELUA sends in its normal system ID frame. The value is 0. 4-31 Read/Write System ID 22/23 Table 4-20 Word Bits Read/Write System ID Parameters UDB Bit Format (Cont) Field Description When the DELUA sends a system ID frame in response to a request ID frame from another node, the DELUA includes the receipt number from the request ID frame. Such special receipt numbers cannot be read by the host. This is a read-only field. UDBB+36 (15:00) MVTYPE MOP Version Type — The MOP version type field that the DELUA sends in its system ID frame. The value is 1. This is a read-only field. UDBB+40 (15:08) MVVER MOP Version-Version — The MOP version-version field that the DELUA sends in its system ID frame. The value is 3. This is a read-only field. UDBB+40 (07:00) MVLEN MOP Version Length — The MOP version length field that the DELUA sends in its system ID frame. The value is 3. This is a read-only field. UDBB+42 (15:08) MVUECO MOP Version User ECO - The MOP version user ECO field that the DELUA sends in its system ID frame. The value is 0. This is a read-only field. UDBB+42 (07:00) MVECO MOP Version ECO -~ The MOP version ECO field that the DELUA sends in its system ID frame. The value is 0. This is a read-only field. UDBB-+44 (15:00) FTYPE Function Type - The function type field that the DELUA sends in its system ID frame. The value is 2. This is a read-only field. UDBB+46 (15:08) FVALI1 Function Value 1 — The function value 1 field that the DELUA sends in its system ID frame. The value is 15 hex if the boot select switches are set to enable remote boots, and 5 if remote boots are disabled. This is a readonly field. UDBB+46 (07:00) FLEN Function Length — The function length field that the DELUA sends in its system ID frame. The value is 2. This is a read-only field. UDBB+50 (15:08) HATYPE Byte 0 of the hardware address type field that the DELUA sends in its system ID frame. The value is 7. This is a read-only field. (07:00) UDBB+50 (07:00) FVAL2 Function Value 2 - The function value 2 field that the DELUA sends in its system ID frame. The value is O. This is a read-only field. 4-32 Read/Write System ID 22/23 Table 4-20 Read/Write System ID Parameters UDB Bit Format (Cont) Word Bits Field Description UDBB+52 (15:08) HALEN Hardware Address Length — The hardware address length field that the DELUA sends in its system ID frame. The value is 6. This is a read-only field. UDBB+52 (07:00) HATYPE Byte 1 of the hardware address type field that the DELUA sends in its system ID frame. The value is O. This is a read-only field. (15:08) UDBB+54 (15:00) HA(15:00) Word 0 of the hardware address field that the DELUA sends in its system ID frame. This is the Ethernet physical address assigned to the DELUA during manufacture. This is a read-only field. UDBB+56 (15:00) HA(31:16) Word 1 of the hardware address field that the DELUA sends in its system ID frame. This is the Ethernet physical address assigned to the DELUA during manufacture. This is a read-only field. UDBB+60 (15:00) HA(47:32) Word 2 of the hardware address field that the DELUA sends in its system ID frame. This is the Ethernet physical address assigned to the DELUA during manufacture. This is a read-only field. UDBB+62 (15:00) DTYPE Device Type — The device type field that the DELUA sends in its system ID frame. The value is 64 hex. This is a read-only field. ' UDBB+64 (15:08) DVALUE " Device Value — The device value field that the DELUA sends in its system ID frame. The value is 11 decimal. This is a read-only field. .UDBB+64 (08:00) DLEN Device Length — The device length field that the DELUA sends in its system ID frame. The value is 1. This is a read-only field. UDBB+66 - UDBB+306 (15:00) PARAM Additional Parameters — Up to 146 bytes of data that the DELUA sends in the parameters field of the system ID frame described in Section 5.9. The length of this parameter list is determined by the PLTLEN field in word PCBB+6 of this ancillary function. 4-33 Read/Write Load Server Address 24/25 4.5.13 Read/Write Load Server Address, Ancillary Function Codes 24/25 These ancillary functions are used to read or change the load server address. When the DELUA receives a boot frame from another node on the network, it loads the host operating system. The boot frame is described in Section 5.1. The load server address is the Ethernet physical address of the preferred network node from which the DELUA should get its host’s operating system. The default load server address is the load server multicast address. Figure 4-22 shows the bit format, and Table 4-21 describes the bit functions. 15 08 MBZ 07 06 05 04 03 02 01 00 0 0 0 1 0 1 0 0/1 :PCBB+0 LSA <15:00> :PCBB+2 LSA <31:16> :PCBB+4 LSA <47:32> :PCBB+6 MKV86-1849 Figure 4-22 Read/Write Load Server Address, Ancillary Function Codes 24/25 Bit Format Table 4-21 Read/Write Load Server Address, Ancillary Function Codes 24/25 Bit Descriptions Word Bits Field Description PCBB+0 (15:08) MBZ Must be zero. PCBB+0 (07:00) OP CODE Op code = 24 - Read load server address. Op code = 25 — Write load server address. PCBB+2 (15:00) LSA The low-order 16 address bits of the load server address. (15:00) PCBB+4 (15:00) LSA (31:16) The middle-order 16 address bits of the load server address. PCBB+6 (15:00) LSA The high-order 16 address bits of the load server address. (47:32) Transmit Descriptor Ring Entry 4.6 TRANSMIT DESCRIPTOR RING ENTRY A transmit descriptor ring entry points to a data buffer that the port driver wants the DELUA to send on the network. It specifies the size and starting address of the data buffer. After the DELUA sends the data, it writes status information in the transmit descriptor ring entry. The port driver points to the base address of the transmit descriptor ring (TDRB) with the write descriptor ring format, ancillary function code 11. 4-34 Transmit Descriptor Ring Entry Figure 4-23 shows the bit format, and Table 4-22 describes the bit functions of an entry in the transmit descriptor ring. 5 OWN 14 13 12 [ERRS [MTCH|MORE| 11 10 09 08 07 05 04 03 02 01 00 SLEN <15:00> :TDRB+0 SEGB <15:00> :TDRB+2 ONE | DEF | STF | ENF BUFL [UBTO |UFLO| LCOL |LCAR|RTRY 06 MBZ | SEGB <17:16> TDR | :TDRB+4 :TDRB+6 MKV85-1850 Figure 4-23 Format of an Entry in the Transmit Descriptor Ring Table 4-22 Bit Descriptions of a Transmit Descriptor Ring Entry Word Bit(s) Field Description TDRB+0 (15:00) SLEN Segment Length — Length of the transmit data buffer in bytes. TDRB+2 (15:00) SEGB The low-order 16 address bits of the segment pointed to by the descriptor. TDRB+4 (15) OWN Port Ownership — Set by the host to indicate that the DELUA owns the ring entry and should transmit the data buffer on the network. Cleared by the DELUA after it has transmitted the frame and written status into the descriptor ring entry. TDRB+4 (14) ERRS Error Summary - The logical OR of BUFL (15), UBTO (14), UFLO (13), LCOL (12), LCAR (11), and RTRY (10) in word TDRB+6. TDRB+4 (13) MTCH Station Match - Set by the DELUA when the destination address of the frame matches the physical address, the broadcast address, or a multicast address of the DELUA. Indicates that the DELUA would have received this message if it had not been transmitting at the same time. TDRB+4 (12) MORE Multiple Retries Needed — Set by the DELUA when more than one (and up to 16) retries were needed to transmit a frame. TDRB+4 (11) ONE One Collision — Set by the DELUA when exactly one retry was needed to transmit a frame. TDRB+4 (10) DEF Deferred — Set when the DELUA had to wait for another node to finish transmitting a frame before the DELUA could transmit this frame. TDRB+4 (09) STF Start of Frame — Set by the host to indicate that this data buffer is the first data buffer of the frame. 4-35 Transmit Descriptor Ring Entry Table 4-22 Bit Descriptions of a Transmit Descriptor Ring Entry (Cont) Word Bit(s) Field Description TDRB+4 (08) ENF End of Frame — Set by the host to indicate that this data buffer TDRB+4 (07:02) MBZ Must be zero. TDRB+4 (01:00) SEGB The high-order two address bits of the segment pointed to by the TDRB+6 (15) BUFL Buffer Length Error — Set by one or more of the following is the last data buffer of the frame. descriptor. conditions: 1. The total length of the frame, including chained buffers, is less than the length of the minimum allowable frame. This is 14 bytes if transmit pad enable (TPAD) bit (12) is set in word PCBB+2 of the write mode register, ancillary function code 15. If the DELUA is not in the data padding mode, the minimum length is 60 bytes. If disable transmit CRC (DTCR) bit (03) is set in word PCBB+2 of the write mode register, ancillary function code 15, the minimum length is 64 bytes. 2. The total length of the frame, including chained buffers, exceeds the length of the maximum allowable frame, 1514 bytes. If disable transmit CRC (DTCR) bit (03) is set in word PCBB+2 of the write mode register, ancillary function code 15, then the maximum length is 1518 bytes. 3. The DELUA was in data chaining mode and found an entry with the STF bit set, but it encountered a buffer it did not own before finding a buffer with the ENF bit set. The DELUA sets the BUFL bit in the transmit descriptor ring entry before the entry it does not own. 4. The DELUA was in the data chaining mode and found an entry with the STF bit set, but it encountered another buffer with the STF bit set before finding a buffer with the ENF bit set. The DELUA sets the BUFL bit in the transmit descriptor ring entry before the second entry with the STF bit set. The DELUA does not transmit the frame if BUFL is set for one or more of the buffers that make up the frame. +6 (14) UBTO UNIBUS Timeout — A UNIBUS timeout was encountered while accessing the buffer pointed to by the descriptor ring entry. Transmission of the frame does not occur if UBTO is set for one of the buffers that make up the frame. 4-36 Transmit Descriptor Ring Entry Table 4-22 Bit Descriptions of a Tfansmit Descriptor Ring Entry (Cont) Word Bit(s) Field Description TDRB+6 (13) UFLO Underflow Error — Indicates that the transmitter has truncated a frame. The LANCE system was unable to fetch data words from internal memory fast enough to keep up with the transmit data rate. TDRB+6 (12) LCOL Late Collision — A collision occurred after all nodes on the network should have known that there was a frame being transmitted. Suggests that the collision detection circuitry of some node may have failed. TDRB+6 (11) LCAR Loss of Carrier — The carrier was not present on the channel during transmission, indicating a ‘“‘shorted” cable, the carrier was lost during transmission, or a faulty carrier detect circuit exists. TDRB+6 (10) RTRY Retry — Transmitter has failed in 16 attempts to transmit the (09:00) TDR TDRB+6 frame due to collisions on the medium. Time Domain Reflectometry Value - Indicates the amount of time between the start of transmission and the detection of the collision. This value indicates the distance down the cable to the reflective point if the collision is due to the transmitted frame reflecting back from a point of impedance mismatch in the network cable and colliding with itself. Valid only when RTRY (10) is set. Receive Descriptor Ring Entry 4.7 RECEIVE DESCRIPTOR RING ENTRY A receive descriptor ring entry points to a data buffer into which the DELUA places a frame that it receives on the network. It specifies the size and starting address of the data buffer. After the DELUA receives a frame and writes it into the data buffer, it writes status information in the receive descriptor ring entry. The port driver points to the base address of the receive descriptor ring (RDRB) with the write descriptor ring format, ancillary function code 11. Figure 4-24 shows the bit format, and Table 4-23 describes the bit functions of an entry in the receive descriptor ring. 4-37 Receive Descriptor Ring Entry 5 14 13 12 11 10 owN |ERRs [FRAM|OFLO| cRc| BUFL 09 08 07 06 05 04 03 02 01 00 SLEN - 15:01 MBZ | :RDRB+0 SEGB MBZ | :RDRB+2 " 15:01 . 0 | STF | ENF MBZ [UBTO|NCHN[OVRN MLEN 5°GB | :RORBH4 'RDRB+6 MKV85-1848 Figure 4-24 Table 4-23 Format of an Entry in the Receive Descriptor Ring Bit Descriptions of a Receive Descriptor Ring Entry Word Bits Field Description RDRB+0 (15:01) SLEN Segment Length — Length of the receive data buffer in bytes. RDRB+2 (15:01) SEGB The low-order 16 address bits of the segment pointed to by the descriptor. RDRB+4 (15) OWN Port Ownership — Set by the host to indicate that the DELUA owns the ring entry and can use the associated data buffer to store a frame that it may receive on the network. Cleared by the DELUA after it has received a frame and written it into the data buffer and written status into the descriptor ring entry. RDRB+4 (14) ERRS Error Summary — The logical OR of FRAM (13) and CRC (11) in word RDRB+4 and BUFL (15), UBTO (14), and OVRN (12) in word RDRB+6. RDRB+4 (13) FRAM Frame Error - Indicates that the length of the frame is not a multiple of 8 bits. RDRB+4 (12) OFLO RDRB+4 (11) CRC Frame Overflow - The frame received was longer than the maximum allowable Ethernet frame of 1500 data bytes. Data chaining was not attempted and, therefore, the frame may be truncated to fit in the buffer. Cyclical Redundancy Check - Frame check error, data is not valid. RDRB+4 (10) MBZ Must be zero. RDRB+4 (09) STF Start of Frame - Set by the DELUA to indicate that this data buffer is the first data buffer of the frame. RDRB+4 (08) ENF End of Frame - Set by the DELUA to indicate that this data RDRB+4 (07:02) MBZ Must be zero. buffer is the last data buffer of the frame. 4-38 Receive Descriptor Ring Entry Table 4-23 Bit Descriptions of a Receive Descriptor Ring Entry (Cont) Word Bits Field Description RDRB+4 (01:00) SEGB The high-order two address bits of the segment pointed to by the RDRB+6 (15) BUFL Buffer Length Error — The frame does not fit in the current RDRB+6 (14) UBTO UNIBUS Timeout - A UNIBUS timeout was encountered while RDRB+6 (13) NCHN No Data Chaining - Indicates that disable receive data chaining (17:16) descriptor. receive buffer and the DELUA does not own the next buffer. The DELUA has truncated the message to fit into the current buffer. moving data into the buffer pointed to by the descriptor entry. (DRDC) bit (13) in word PCBB+2 of the write mode register, ancillary function code 15 was set. The frame may be truncated to fit in the single buffer. RDRB+6 (12) OVRN Overrun Error - The DELUA lost part or all of the frame because RDRB+6 (11:00) MLEN Message Length — The total length of the frame that the DELUA the LANCE system was unable to write the data into internal memory as fast as it received the frame from the network. received. This field is only valid in the entry in which ENF (08) of word RDRB+4 is set. 4-39 Transmit Data Buffer Format 4.8 TRANSMIT DATA BUFFER FORMAT Transmit data buffers may begin on arbitrary byte boundaries. Figure 4-25 shows the format of a buffer when it starts on an odd-byte boundary. Figure 4-26 shows the format of a buffer when it starts on an even-byte boundary. 15 08 07 00 FIRST BIT TO BE TRANSMITTED — DESTINATION ADDRESS FIELD LOADED BY THE PORT DRIVER 6 BYTES [~ SOURCE ‘ADDRESS FIELD — RESERVED BY THE PORT DRIVER, 6 BYTES FIELD INSERTED BY THE DELUA TYPE FiELD—2BYTES LOADED BY THE PORT DRIVER — A D— DATA FIELD —] 46 — 1500 BYTES W \\\ | LOADED BY THE PORT DRIVER, MAY BE AN ODD NUMBER OF BYTES } LLAST DATA BIT TO BE TRANSMITTED MKV85-0346 Figure 4-25 Transmit Data Buffer Starting on an Even-Byte Boundary 4-40 Transmit Data Buffer Format FIRST BIT TO BE TRANSMITTED 00 08 07 15 27 LOADED BY THE PORT DRIVER DESTINATION ADDRESS FIELD 6 BYTES RESERVED BY THE PORT DRIVER, FIELD INSERTED BY THE DELUA SOURCE ADDRESS FIELD 6 BYTES TYPE FIELD LOADED BY THE PORT DRIVER TYPE FIELD LOADED BY THE PORT DRIVER DATA FIELD 46 — 1500 BYTES . I LAST DATABIT TO BE TRANSMITTED MKV85-0353 Figure 4-26 Transmit Data Buffer Starting on an Odd-Byte Boundary 4-41 Receive Data Buffer Format 4.9 RECEIVE DATA BUFFER FORMAT Receive data buffers must begin on an even-byte boundary. Figure 4-27 shows the format of a receive data buffer. 15 00 l«—FIRST BIT RECEIVED — DESTINATION ADDRESS FIELD LOADED BY THE DELUA 6 BYTES — SOURCE ADDRESS FIELD — LOADED BY THE DELUA 6 BYTES TYPE FIELD — 2 BYTES | LOADED BY THE DELUA DATA FIELD - 46 — 1500 BYTES ' LOADED BY THE DELUA CRC - 4BYTES - - — - - LOADED BY THE DELUA — — LLAST BIT RECEIVED MKV85-0354 Figure 4-27 Receive Data Buffer Format 4-42 CHAPTER 5 MAINTENANCE OPERATIONS 5.1 REMOTE BOOT AND DOWN-LINE LOAD The remote boot and down-line load features of the DELUA allow the PDP-11 system, in which the DELUA is installed, to be booted by another node on the network. Switch settings on the DELUA module determine whether the DELUA loads the host by transferring the operating system across the network from another node, or the DELUA signals the host to load itself from its own mass storage system. With the optional M9312 boot module and ROM set (order number MR11K-AE), the DELUA loads the host operating system by transferring the operating system across the network from another node during powerup. The DELUA cannot load a VAX host. 5.1.1 Remote Boot Disabled When remote boot is disabled, the DELUA ignores any boot frames on the network and, thus, cannot be booted by another node. _ Remote booting is disabled when the switches on the switch pack at E69 (see Figure 2-6) are configured as follows: E69 switch 2 (BOOT SEL 0) = ON E69 switch 3 (BOOT SEL 1) = ON or E69 switch 2 (BOOT SEL 0) = OFF E69 switch 3 (BOOT SEL 1) = OFF 5.1.2 Remote Boot from System Boot ROM When remote boot from system boot ROM is selected, the DELUA boots its host system by starting the system boot module when it receives a boot frame from another node on the network. Remote boot from system boot ROM is enabled when the switches on the switch pack at E69 (see Figure 2-6) are configured as follows: E69 switch 2 (BOOT SEL 0) = ON E69 switch 3 (BOOT SEL 1) = OFF The system boot module must be set up to boot on powerup. The following sequence of events occurs when a boot frame is received from another node on the network. 1. The DELUA receives a boot frame, that is, a frame having the remote console value in its type field and the boot value in its code field. If disable maintenance message (DMNT) bit (09) of word PCBB+2 of the mode register is set, the frame is discarded. If the CRC is invalid and the DELUA is in the running state, the frame is treated as a normal frame and sent to the host. If the CRC is invalid and the DELUA is not in the running state, the frame is discarded. Otherwise, boot processing of the frame continues. If the character count, processor, control, and software ID fields of the boot frame are within expected limits, boot processing of the frame continues. Otherwise, the frame is discarded. The DELUA compares the verification code in the boot frame with the verification code last supplied by the port driver. The port driver writes the verification code with the write system ID parameters, ancillary function code 23. If the code does not match, the DELUA ignores the boot frame. If the port driver has not supplied a verification code or has supplied a code of 0, the DELUA accepts any verification code. The DELUA asserts and releases ACLO on the UNIBUS, which starts the system boot module. The DELUA ignores any additional boot frames on the network for 40 seconds to give the system time to start. 5.1.3 Remote Boot and System Load When remote boot and system load is selected, the DELUA loads the host with an operating system transferred from another node on the network when it receives a boot message from another node. Remote boot and system load is enabled when the switches on the switch pack at E69 (see Figure 2-6) are configured as follows: E69 switch 2 (BOOT SEL 0) = OFF E69 switch 3 (BOOT SEL 1) = ON The system processor must be set up so that it does not boot on powerup. The following sequence of events occurs when a boot frame is received from another node on the network. l. The DELUA receives a boot frame, that is, a frame having the remote console value in its type field and the boot value in its code field. If disable maintenance message (DMNT) bit (09) of word PCBB+2 of the mode register is set, the frame is discarded. If the CRC is invalid and the DELUA is in the running state, the frame is treated as a normal frame and sent to the host. If the CRC is invalid and the DELUA is not in the running state, the frame is discarded. Otherwise, boot processing of the frame continues. If the character count, processor, control, and software ID fields of the boot frame are within expected limits, boot processing of the frame continues. Otherwise, the frame is discarded. 5-2 The DELUA compares the verification code in the boot frame with the verification code last supplied by the port driver. The port driver writes the verification code with the write system ID parameters, ancillary function code 23. If the code does not match, the DELUA ignores the boot frame. If the port driver has not supplied a verification code or has supplied a code of 0, the DELUA accepts any verification code. The DELUA decodes the processor field of the boot frame to determine whether to request system processor type software or communication processor type software. The DELUA enters the primary load state and sets the unsolicited state change interrupt (USCI) bit (08) of PCSRO. To keep the host busy and prevent it from interfering with the operating system load, the DELUA forces the host into executing a branch self instruction in memory address 2. To accomplish this, the DELUA loads the following program into host memory: 2/ 4/ 6/ 10/ 12/ 14/ 16/ 20/ 22/ 24/ 26/ 30/ 32/ 34/ 777 PCSRO address of the DELUA 0 12 0 16 0 22 0 30 340 012706 1000 762 Branch self Powerup at location 30 Set priority to 7 Set up the stack pointer 1000 to avoid stack limit traps Branch to location 2 to do Branch self The DELUA asserts the ACLO signal on the UNIBUS, which causes the host processor to perform a power-fail trap. This causes the host to read the processor status word from location 26 and jump to the address in location 24. After a few instructions, the host is stuck on the branch self instruction at address 2. The DELUA blocks UNIBUS INIT to itself. 10. The DELUA forms a request program frame. The DELUA copies the software ID field of the boot frame into the software ID field of the request program frame. The DELUA copies the address in the source address field of the boot frame to the destination address field of the request program frame if bit (00) of the control field of the boot frame equals 1. If bit (00) of the control field of the boot frame equals 0, the DELUA writes the load server address into the destination address field of the request program frame. The host sets the load server address with the write load server address, ancillary function code 25. If the host has not set the load server address, the DELUA uses the load assistant multicast address. 1. The DELUA transmits the request program frame and waits for a memory load with transfer address frame. The memory load with transfer address frame contains the secondary loader program. 5-3 12. If, after 5 seconds, the DELUA receives an incorrect memory load with transfer address frame, or does not receive any memory load with transfer address frame, it retransmits the request program frame. The DELUA repeats this procedure up to eight times. During this time, the DELUA discards any incoming boot frame. If the DELUA does not receive a memory load with transfer address frame after eight tries, it takes the following action: a. If the boot message instructed the DELUA to request communication processor type software, the DELUA enters the ready state and sets the unsolicited state change interrupt (USCI) bit (08) of PCSRO. - b. If the boot message instructed the DELUA to request system processor type software, it changes the software ID field of the request program frame to zero (to ask for any type of system processor software) and it changes the destination address field to the load assistant multicast address. The DELUA sends this request program frame every 30 seconds until it receives a memory load with transfer address frame. During this time the DELUA accepts any incoming boot frame. 13. The DELUA receives a memory load with transfer address frame. If the DELUA transmitted the request program frame to a specific node, then it will only accept a memory load with transfer address frame from that node. If the DELUA transmitted the request program frame to a multicast address, then it will accept any error-free memory load with transfer address frame. 14. The memory load with transfer address frame contains the secondary loader program. The DELUA loads the data field of the memory load with transfer address frame into its memory starting at the load address supplied in the frame. 15. The DELUA starts the secondary loader program by jumping to the transfer memory load with transfer address frame. 16. The secondary loader program requests a tertiary loader program from another host memory, and starts it. 17. address supplied in the node, loads it into The tertiary loader program in host memory contains a DELUA port driver program. It resets and initializes the DELUA and uses it to transfer an operating system into the host from another node. The tertiary loader program then starts the host operating system. 5.1.4 Remote Boot on Powerup A PDP-11 system can be set up so that the DELUA performs a remote boot when the system powers up. You must install an M9312 boot module with ROM set (order number MR11K-AE ). You must also set the boot select switches to either remote boot and system load or disable remote boot. At system powerup, the program code in the boot ROM executes. This program resets the DELUA and then waits for it to finish selftest and enter the ready state. The program sets up a PCB and issues a read default physical address, ancillary function code 2. It prints the Ethernet physical address of the DELUA on the system console terminal. Then it writes a BOOT port command into PCSRO. This causes the DELUA to perform a remote boot as described in Section 5.1.5. 3.1.5 BOOT Port Command The BOOT port command causes the DELUA to request an operating system from another node on the network, to load the operating system into the host, and start it. 5-4 The following events occur when the host writes a BOOT port command into PCSRO. 1. The DELUA receives the BOOT port command. 2. The DELUA enters the primary load state and sets the done interrupt (DNI) bit (11) in PCSRO. The DELUA forms a request program frame. The DELUA writes the software ID field of the request program frame with the SOFTID field bits (07:00) of word UDBB+10 supplied with the last write system ID parameters, ancillary function code 23. The DELUA writes the load server address into the destination address field of the request program frame. The host sets the load server address with the write load server address, ancillary function code 25. If the host has not set the load server address, the DELUA uses the load assistant multicast address. The DELUA transmits the request program frame and waits for a memory load with transfer address frame. The remainder of the BOOT port command sequence is the same as the remote boot and system load sequence described in Section 5.1.3. It is assumed that the host processor will be in an appropriate state so that it will not interfere with loading and starting the tertiary loader program. 5.2 BOOT FRAME FORMAT Figure S-1 shows each byte in the boot frame, and Table 5-1 describes the function of each byte. 00 07 DESTINATION ADDRESS/6 BYTES SOURCE ADDRESS/6 BYTES TYPE/2BYTES CHARACTER COUNT/2 BYTES CODE/1BYTE PAD/1BYTE VERIFICATION/B8 BYTES PROCESSOR/1BYTE CONTROL/1BYTE SOFTWARE ID/1 BYTE PAD DATA/32BYTES CRC/4BYTES MKV85-0355 Figure 5-1 Boot Frame Format 5-5 Table 5-1 Boot Frame Description Field Length (Bytes) Description Destination Address 6 The physical address of the DELUA. Source Address 6 The physical address of the requesting station. Type 2 The remote console type. Value = (0260) 60-02 hex. Character Count 2 The number of bytes following the character count field, less pad data and CRC. Value = 000D hex. Code | The function code for the boot frame. Value = 06 hex. PAD 1 The constant 0. Verification 8 The code to be compared against the port-driver-supplied verification code. The codes must match before the DELUA will honor the boot. If the DELUA has not been supplied with a verification code by the port driver or supplied with a code of 0, the DELUA accepts any value in the boot frame verification field. Processor 1 Value = 00 hex - System boot, enter the primary load state. Value = 01 hex - Boot the DELUA, enter the primary load state. Control 1 Bit (00) = 0 - Boot from the system default. Bit (00) = 1 - Boot from the requesting system. Software ID 1 Value = 00 hex - No ID. Value = FF hex - Operating system. Value = FE hex - Diagnostics. PAD Data 32 CRC 4 Pad characters, zeros are added to pad the frame to 64 bytes. | Incoming block check character. 5.3 REQUEST PROGRAM FRAME FORMAT Figure 5-2 shows each byte in the request program frame, and Table 5-2 describes the function of each byte. 00 07 | | | DESTINATION ADDRESS/6 BYTES 00 07 SOURCE ADDRESS/6 BYTES MOP VERSION — USER ECO/1 BYTE TYPE/2 BYTES FUNCTION — TYPE/2BYTES CHARACTER COUNT/2BYTES FUNCTION — LENGTH/1 BYTE CODE/1 BYTE FUNCTION — VALUE 1/1 BYTE DEVICE TYPE/1BYTE FUNCTION — VALUE 2/1 BYTE FORMAT VERSION/1 BYTE HARDWARE ADDRESS — TYPE/2 BYTES PROGRAM TYPE/1 BYTE HARDWARE ADDRESS — LENGTH/1 BYTE SOFTWARE ID/1BYTE HARDWARE ADDRESS — VALUE/6 BYTES PROCESSOR/1BYTE DEVICE — TYPE/ 2 BYTES MOP VERSION — TYPE/2 BYTES DEVICE — LENGTH/1 BYTE MOP VERSION — LENGTH/1 BYTE DEVICE — VALUE/1 BYTE MOP VERSION — VERSION/1 BYTE PAD/14 BYTES MOP VERSION — ECO/1 BYTE CRC/4 BYTES ! | | | Figure 5-2 ] TK-9050 Request Program Frame Format 5-7 Table 5-2 Field Length (Bytes) Destination 6 Request Program Frame Description Description The address supplied by the write load server ancillary function or the source address of a received boot frame. The default address is the load assistant multicast address . Load assistant multicast address value = AB-00 -00-01-00-00 hex. (00AB) (0100) (0000) Source Address 6 The physical address of the DELUA. Type 2 The dump/load type. Value = (0160) 60-01 hex. Character Count 2 The number of bytes following the chara cter count field, less pad data and CRC. Value = (001E) 1E-00 hex. Code 1 Value = 08. Device Type 1 Value = 11 decimal - The DELUA Format Version 1 Value = 01. Program Type | Value = 00, DELUA microcode (seco Software ID 1 Value = 0 or any negative number. Processor 1 Value = 00 - System boot, enter the prim ndary loader). ary load state. Value = 01 - Boot the DELUA, enter MOP Version - Type 2 Value = (0001) 01-00 hex. MOP Version - Length 1 Value = 03. MOP Version - Version 1 Value = 03. MOP Version - ECO 1 Value = 00. MOP Version - User ECO 1 Value = 00. Function - Type 2 Value = (0002) 02-00 hex. Function - Length code. Value = 02. 5-8 the primary load state. Table 5-2 Request Program Frame Description (Cont) Length Field (Bytes) Description Function - Value 1 1 If remote boot is enabled with the boot select switches, then the DELUA supports the following maintenance functions: loop, primary loader, boot. Value = 15 hex. If remote boot is disabled with the boot select switches, then the DELUA supports the following maintenance functions: loop, primary loader. Value = 05 hex. Function - Value 2 1 Value = 00. Hardware Address — Type 2 Value = (0007) 07-00 hex. Hardware Address — Length 1 Value = 06. Hardware Address — Value 6 The physical address of the DELUA. Device - Type 2 Value = (0064) 64-00 hex. Device — Length 1 Value = 01. Device - Value 1 Value = 11 decimal - The DELUA code. PAD Bytes 14 14 bytes of zeros to pad the frame to 64 bytes. CRC 4 DELUA-generated block check character. 5-9 5.4 MEMORY LOAD WITH TRANSFER ADDRESS FRAME FORMAT Figure 5-3 shows each byte in the memory load with transfer address frame, and Table 5-3 describes the function of each byte. 07 00 DESTINATION ADDRESS/6 BYTES SOURCE ADDRESS/6 BYTES TYPE/2 BYTES CHARACTER COUNT/2 BYTES CODE/1 BYTE LOAD NUMBER/1BYTE LOAD ADDRESS/4 BYTES IMAGE DATA/2-1488 BYTES TRANSFER ADDRESS/4 BYTES PADBYTES/32-0BYTES | CRC/4BYTES MKV85-1847 Figure 5-3 Memory Load with Transfer Address Frame Format Table 5-3 Memory Load with Transfer Address Frame Description Length Field (Bytes) Description Destination Address 6 The physical address of the DELUA. Source Address 6 The physical address of the load server. Type 2 The dump/load type. Character Count 2 The number of bytes following the character count field, not Value = (0160) 60-01 hex. counting the pad bytes or the CRC. Value = 12 to 1498. 1 Value = 00. Load Number 1 Value = 00. Load Address 4 The starting address in DELUA infernal memory for storage Image Data 2-1488 The image data of the secondary loader program to be stored Transfer Address 4 The internal memory address at which the DELUA starts Pad Bytes 32-0 CRC 4 | Code 5.5 of the image data. in DELUA internal memory. executing the secondary loader program. Pad bytes used when necessary to increase length of frame to the 64-byte minimum. Received block check character. INTERNAL AND EXTERNAL LOOPBACK MODE The DELUA enters loopback mode when LOOP bit (02) is set in word PCBB+2 of the write mode register, ancillary function code 15. If INTL bit (06) is also set, then the LANCE system loops the data internally within the DELUA. If INTL bit (06) is not set, the LANCE system loops the data externally by transmitting the frame on the network and reading it back at the same time. A loopback frame must be set up just like a normal frame, complete with destination address, source address, type, and data fields. The destination address must be the physical address for the DELUA unit or a broadcast or multicast address that the DELUA is enabled to receive. The data field can be no larger than 32 bytes, due to the size of the data silo within the LANCE chip. If the disable transmitter CRC (DTCR) bit (03) of the mode register is set, the DELUA does not generate and send the 4-byte CRC field with the loopback frame. It does, however, perform the normal CRC check while it is reading the loopback frame. The port driver must provide a frame with 28 bytes of data and a 4byte CRC in the data field. If DTCR bit (03) is not set, the DELUA generates a CRC and appends it to the 32 bytes of data, but it does not perform the normal CRC check while it is reading the loopback frame. Thus, the port driver receives 36 bytes of data (32 data bytes plus 4 CRC bytes). It must check that the DELUA hardware generated the correct CRC field. 5-11 In external loopback mode, the RUNT frame filter is disabled so that the DELUA is able to receive frames smaller than 64 bytes. 5.6 CHANNEL LOOPBACK The DELUA microcode supports maintenance operations protocol (MOP) loop operations. Loop frames have the Ethernet configuration test (ECT) in the type field. The DELUA does not check the type field of multicast address frames that it receives. The port driver must check the type field of multicast frames. The DELUA processes a loopback frame in the following manner: The DELUA receives a loopback frame, that is, a frame having the Ethernet communications test (ECT) type value in its type field. If disable maintenance message (DMNT) bit (09) of word PCBB+2 of the mode register is set, the frame is discarded. If the CRC is invalid and the DELUA is in the running state, the frame is treated as a normal frame and sent to the host. If the CRC:is invalid and the DELUA is not in the running state, the frame is discarded. Otherwise, loopback processing continues. If the destination address of the frame is a multicast address and the DELUA is in the running state, the frame is treated as a normal frame and sent to the host. If it contains a multicast address and the DELUA is not in the running state, the frame is discarded. The DELUA locates the function field by adding the value in the skip count field to the location of the skip count field plus 1. If the function value is not 1 or 2 and the DELUA is in the running state, the frame is treated as a normal frame and sent to the host. If the function value is not 1 or 2 and the DELUA is not in the running state, the frame is discarded. If the function value is 1, this indicates that the loopback frame was originally sent by the host and has now been looped back by one or more other nodes. If the DELUA is in the running state, it sends the frame to the host. If the DELUA is not in the running state, the frame is discarded. If the function value is 2, indicating that the DELUA should forward the frame to another node, the DELUA does the following: Lt 1. Inserts the contents of the forward address field into the destinati b. Replaces the source address field with the physical address C. Adds eight to the value of the skip count d. Strips the last 4 bytes (the CRC) from the frame e. Transmits the resulting frame, generating and appendi on address field of the DELUA ng 4 bytes of CRC 5-12 5.7 : LOOPBACK FRAME FORMAT of nodes and then returned to the A loopback frame is set up so that it can be forwarded by a seriesa function code associated with each with s addresse node originating node. The frame contains a list of to forward the frame to node the tells which code, function address. Each address will have the forward originating node so that the of address the be should list the the next address on the list. The last address on entry with just a reply an is list the on address last the the frame will come back to that node. After code, it passes the function reply the with frame loopback a function code. When the DELUA receives has now been and host the with ed originat that frame frame to the host because this is a loopback returned. Figure 5-4 shows each byte in the loopback frame, and Table 5-4 describes the function of each byte. 00 07 DESTINATION ADDRESS/6 BYTES SOURCE ADDRESS/6 BYTES TYPE/2BYTES SKIP COUNT/2BYTES FORWARD FUNCTION/2 BYTES INSTRUCTIONS FOR FIRST FORWARDING NODE FORWARD ADDRESS/6 BYTES FORWARD FUNCTION/2 BYTES INSTRUCTIONS FOR SECOND FORWARDING NODE FORWARD ADDRESS/6 BYTES FORWARD FUNCTION/2 BYTES INSTRUCTIONS FOR LAST NODE TO RETURN TO ORIGINATING NODE FORWARD ADDRESS/6 BYTES INSTRUCTION FOR ORIGINATING NODE PASS FRAME TO HOST. } TO REPLY FUNCTION/2 BYTES PAD OR TEST DATA/34-1490 BYTES CRC/4 BYTES MKV86-0242 Figure 5-4 Loopback Frame Format 5-13 Table 5-4 Field Length (Bytes) 'Destination Address 6 Loopback Frame Description Description Inbound ~ The physical address of the DELUA, or the broadcast address. Outbound - The forward address. Source Address 6 Inbound - The physical address of the loop requesting station. Outbound - The physical address of the DELUA. Type 2 Ethernet communications test (ECT) indicating a loopba ck type frame. Value = (0090) 90-00 hex. Skip Count 2 The number of bytes to skip after this field to find the appropriate function field. . If this field specifies a forward type operation, the DELUA adds 8 to the skip count before transmitting the frame. Forward Function 2 Value = (0002) 02-00 hex. Forward Address 6 The physical address of the node to which the frame should be sent next. The DELUA copies this addres s into the destination address field and then transmits the frame. Reply Function 2 Value = (0001) 01-00 hex. Pad or Test Data 34 to 1490 Pad bytes of zeros to increase the frame to 64 bytes or a loopback test data pattern. 4 Inbound - Block check character. CRC Outbound - CRC generated by the DELUA. 5.8 REQUEST ID FRAME When the DELUA receives a request ID frame , it sends 5-14 a system ID frame to the requesting node. Figure 5-5 shows each byte in the request 1D frame, and Table 5-5 describes the function of each byte. 00 : 07 DESTINATION ADDRESS/6 BYTES SOURCE ADDRESS/6 BYTES TYPE/2 BYTES CHARACTER COUNT/2BYTES CODE/1 BYTE PAD OF ZERO/1 BYTE RECEIPT NUMBER/2BYTES PAD DATA/43 BYTES CRC/4BYTES TK-9053 Figure 5-5 Request 1D Frame Format Table 5-5 Length - Request ID Frame Description Field (Bytes) Description Destination Address 6 The physical address of the DELUA. Source Address 6 The physical address of the requesting station. Type 2 The remote console type. Character Count 2 The number of bytes following the character count field, less Value = (0260) 60-02 hex. pad data and CRC. Value = 04 hex. Code 1 "~ The function code for the request ID frame. Value = 05 hex. 5-15 Table 5-5 Request ID Frame Description (Cont) Léngth Field (Bytes) Description Pad of Zero ] Value = 00 hex. Receipt Number 2 A receipt number to identify the request. Pad Data 43 Characters inserted, as required, to pad the frame to 64 bytes. CRC 4 Incoming block check character. 5.9 SYSTEM ID FRAME FORMAT The DELUA transmits a system ID frame to the remote console service multicast address every 10 minutes. The DELUA also sends a system ID frame to a specific node in response to a request ID frame. Figure 5-6 shows each byte in the system ID frame, and Table 5-6 describes the function of each byte. l 07 00 I I 07 ' DESTINATION ADDRESS/6 BYTES FUNCTION — TYPE/2 BYTES SOURCE ADDRESS/6 BYTES FUNCTION — LENGTH/1 BYTE TYPE/2BYTES 00 | FUNCTION — VALUE 1/1 BYTE CHARACTER COUNT/2BYTES FUNCTION — VALUE 2/1 BYTE CODE/1BYTE HARDWARE ADDRESS — TYPE/2 BYTES PAD OF ZERO/1BYTE HARDWARE ADDRESS — LENGTH/1BYTE RECEIPT NUMBER/2 BYTES HARDWARE ADDRESS — VALUE/6 BYTES MOP VERSION — TYPE/2 BYTES DEVICE — TYPE/2BYTES MOP VERSION — LENGTH/1BYTE DEVICE — LENGTH/1 BYTE MOP VERSION — VERSION/1 BYTE DEVICE - VALUE/1BYTE MOP VERSION — ECO/1 BYTE PAD/PARAMETERS/16-146 BYTES MOP VERSION - USER ECO/1BYTE CRC/4 BYTES TK-9062 Figure 5-6 System ID Frame Format 5-16 Table 5-6 Length System ID Frame Description Field (Bytes) Description Destination Address 6 The physical address of the ID requesting station or the remote console service multicast address. Remote console service multicast address value = AB-00-00-02-00-00 hex. (00AB) (0200) (0000) Source Address 6 The physical address of the DELUA. Type 2 The remote console type. Character Count 2 The number of bytes following the character count field, less Value = (0260) 60-02 hex. pad data and CRC. Value = (001C) 1C-00 to (05DA) DA-05 hex. Code 1 The function code for the system ID frame. Pad of Zero 1 Value = 00 hex. Receipt Number 2 A receipt number to identify the request. MOP Version - Type 2 Value = (0001) 01-00 hex. MOP Version — Length 1 Value = 03 hex. MOP Version - Version 1 Value = 03 hex. MOP Version - ECO 1 Value = 00 hex. MOP Version - User ECO 1 Value = 00 hex. Function — Type 2 Value = (0002) 02-00 hex. Value = 07 hex. Function - Length Value = 02 hex. Function — Value 1 If remote boot is enabled with the boot select switches, then the DELUA supports the following maintenance functions: loop, primary loader, boot. Value = 15 hex. If remote boot is disabled with the boot select switches, then the DELUA supports the following maintenance functions: loop, primary loader. Value = 05 hex. 5-17 Table 5-6 System ID Frame Description (Cont) Length Field (Bytes) Description Function - Value 2 1 Value = 00. Hardware Address - Type 2 Value = (0007) 07-00 hex. Hardware Address - Length ] Value = 06 hex. Hardware Address — Value 6 The default physical address of the DELUA. Device - Type 2 Value = (0064) 64-00 hex. Device - Length 1 Value = 01. Device - Value 1 Value = 11 decimal - the DELUA code. PAD/Parameters 146 The set of additional parameters supplied by the host in words UDBB+66 through UDBB+306 of the write system ID parameters, ancillary function code 23. If not supplied, the DELUA adds 16 bytes of zeros to pad the frame to 64 bytes. CRC 4 Outgoing block check character. 5.10 MICROCODE LOADING To load custom microcode into the DELUA, the port driver must put the DELUA into the port halted state or the ready state by issuing a HALT or STOP port command. When the DELUA is in the halted state, internal memory from address 4400 to 1 FFFE is available for loading. When the DELUA is in the ready state, internal memory from address 4400 to 6400 hex is available for loading. The recommended procedure to load and start microcode is as follows: 1. 2. Reset the DELUA by writing the RESET bit (05) in PCSRO. Wait for the done interrupt bit (11) in PCSRO to be set and the DELUA to enter state. the ready Write a HALT port command into PCSRO. Wait for the done interrupt bit (11) in PCSRO to be set and the DELUA to enter the port halted state. Use the load internal memory, ancillary function code 21 to load a memory. block of code into DELUA Use the dump internal memory, ancillary function code 20 to dump the same block of code from internal memory and perform a word-by-word comparison. 5-18 5.11 7. If the comparison produces no errors, repeat the load, dump and compare until the entire microcode is loaded. 8. Issue the start microaddress, ancillary function code 1 to start the DELUA executing at a specified address. MICROCODE UPDATE PROCESS The DELUA has a provision for accepting updates or patches to its microcode without replacing the ROM containing the microcode. Updates can be included as a part of the DELUA port driver software in new releases of the host’s operating system. [f the port driver has a DELUA microcode patch, it loads the patch whenever it initializes the DELUA. The microcode patch file consists of the standard RSX label blocks followed by data blocks as shown in Figure 5-7. LABEL BLOCK O LABEL BLOCK 1 DATA BLOCK 0 CC CC ) 2 D) DATA BLOCK 1 DATA BLOCK n TK-10110 Figure 5-7 Microcode Patch File Format Figure 5-8 shows the format of data blocks in a patch file. The first word of a data block is a byte count of the number of data bytes to be transferred into the DELUA. The second word is the address to begin loading the data inside the DELUA. Each data block can contain a number of microcode patches. Unused space at the end of a data block must be filled with zeros. No single patch can extend beyond a data block. Large patches must be divided into a series of smaller patches. The two words after the last patch in the file must be a word containing negative one and a word containing the internal starting address to begin microcode execution. The DELUA must be in the port halted state or the ready state to accept microcode patches. During DELUA initialization, the port driver loads each microcode patch into the DELUA with the load internal memory, ancillary function code 21. The port driver uses the byte count and internal address supplied in the patch file. When the port driver finds a patch in the patch file with a byte count of zero indicating pad data at the end of a data block, it skips to the beginning of the next data block. When the port driver finds a byte count of negative one, it uses the next word as the starting microaddress and issues the start microaddress, ancillary function code 1. BYTE COUNT OF TRANSFER DELUA INTERNAL LOAD ADDRESS Av DATA v . ~N . W BYTE COUNT OF TRANSFER DATA DELUA INTERNAL LOAD ADDRESS BLOCK 0 A DATA A ~N_ : nr/ 0 ~ r}/ . ~ . Y 0 BYTE COUNT OF TRANSFER DELUA INTERNAL LOAD ADDRESS ~ DATA A ’Ty . av > BYTE COUNT = —1 DATA BLOCKn DELUA START ADDRESS 0 ~, Y, . ~ : 'V 0 J MKV85-1041 Figure 5-8 Patch File Data Block Format 5-20 CHAPTER 6 SERVICE 6.1 MAINTENANCE PHILOSOPHY The maintenance philosophy for the DELUA is isolation of the field replaceable unit (FRU). The FRUs for the DELUA are the M7521 module, the UNA bulkhead assembly, and the UNA bulkhead cable. Faults that appear to be in the DELUA can be caused by faults in the network: the transceiver, the transceiver cable, or the network coaxial cable. Faults that are isolated to the network should be referred to network service personnel. 6.2 TROUBLESHOOTING PROCEDURE The troubleshooting procedure is shown in the flowchart in Figure 6-1. 6.2.1 Selftest To run the DELUA selftest, turn the power off and then back on. The simplest way to do this is to use the circuit breaker for the cabinet containing the DELUA. When the test has completed successfully, only one LED, D8, should be on. This indicates that the DELUA is in the ready state. LED DS, the activity indicator, may also be flickering. Figure 6-2 shows the selftest LEDs, and Table 6-1 lists the selftest error and status codes. The selftest checks the DELUA module’s internal circuitry, reads and writes the four UNIBUS registers in the DELUA, and sends messages on the network and reads them back. If the DELUA fails its external loopback test, check the LED on the UNA bulkhead assembly that monitors the —15 V supply to the transceiver. There is also a circuit breaker on the UNA bulkhead assembly for the —15 V power to the transceiver. If the LED is on, check for a bad transceiver by attaching an H4080 loopback transceiver (shown in Figure 2-9) and running the test again. If the external loopback test still fails, replace the FRUs in the following order: 1. 2. 3. The UNA bulkhead cable The UNA bulkhead assembly The DELUA module (M7521) If the DELUA selftest fails any test other than the external loopback test, the most likely failure is within the DELUA module (M7521). 6-1 1S FAILING NODE KNOWN? RUN NI EXERCISER TEST YES | REFER PROBLEM TO NETWORK SERVICE PEOPLE NO 1) CHECK BULKHEAD s BULKHEAD LED CIRCUIT BREAKER | 2) CHECK/REPLACE: s« BULKHEAD CABLE ON? e -15V POWER SUPPLY PIN FB2 VISUALLY CHECK 1) TRANSCEIVER CABLE 2) BULKHEAD CABLE RESET CABLES oK? 1) TRANSCEIVER CABLE 2) BULKHEAD CABLE MKVES-0883 Figure 6-1 Troubleshooting Flowchart (Sheet 1 of 2) 6-2 \ RUN FUNCTIONAL DIAGNOSTICS SEE NOTE 1 NO PASS ? SEE NOTE 2 SEE NOTE 3 REPLACE MOST LIKELY FRU YES INSTALL HA4080 RUN EXTERNAL LOOPBACK TEST OF FUNCTIONALS NOTE 1. ON VAX SYSTEMS RUNNING VMS, RUN ON-LINE FUNCTIONAL PASS DIAGNOSTICS FIRST. NO NOTE 2: IF THE FAILED TEST IS OTHER THAN AN EXTERNAL LOOPBACK FAILURE, THE MOST LIKELY FAILED FRU IS THE M7521. YES RECONNECT HARDWARE NOTE 3: IF THE FAILED TEST IS THE EXTERNAL LOOPBACK TEST THEN THE ORDER OF FRU TO NETWORK REPLACEMENT IS; A) TRANSCEIVER CABLE B) BULKHEAD CABLE RUN USER’'S C) BULKHEAD CONNECTOR OPERATING D) M7521 SYSTEM REFER PROBLEM TO NETWORK SERVICE PEOPLE MKVE5-0582 Figure 6-1 Troubleshooting Flowchart (Sheet 2 of 2) 6-3 DUUZULIOED 22291 D3 D5 | \N§938 D7 'nmnmnm D9 NOTE: LED D2 IS NOT USED. MKV85-1841 Figure 6-2 Table 6-1 D3 LEDs (1=0ON) DS Dé6 D7 Selftest Error and Status Codes D8 D9 Meaning 0 0 0 X 0 0 0 X 0 0 0 0 0 0 0 0 Reset state 0 1 1 1 1 0 Primary load state Ready state Running state 0 X 0 0 0 0 0 X 0 X 0 0 0 0 X X 0 0 0 0 X X 0 0 — D4 Selftest and Status LEDs L 1 1 0 | 1 1 1 0 1 UNIBUS halted state NI halted state NI and UNIBUS halted state 0 0 1 0 1 1 Port halted state Secondary load state 0 | 0 0 1 0 0 0 0 0 0 | 1 1 0 0 0 0 0 0 1 0 0 0 1 0 e 0—0— | 0 0 1 0 0~ 0 1 | |— [ Q— 1 1 1 0 1 0 0 0 0 0 1 0 0 1 0 | | 0 0 0 1 | 0 0 1 0 0 1 Activity Indicator Unsolicited trap LANCE interrupt but no bits set in CSRO LANCE memory error Parity error Port command 0 interrupt 1 Transmit error ——mo—H MOP error Receive error, dequeue from empty queue Receive error, bad buffer being returned Receive error, bad buffer being queued 6-4 Selftest Error and Status Codes (Cont) 4 Table 6-1 LEDs (1=0N) DS D6 D7 D8 D9 Meaning - 0 0 0 0 0 0 0 0 0 1 1 0 ROM CRC test RAM checkerboard test 1 0 0 0 0 0 0 0 0 0 0 0 1 1 Nair, Thatte, and Abraham’s memory test 0 0 0 1 | 1 1 0 1 | 1 1 0 1 RAM parity memory test CPU microprocessor exception test RAM parity interrupt test 0 1 0 0 0 | 0 0 0 0 0 1 Timer interrupt test 1 1 0 0 1 1 0 0 1 1 1 0 0 0 1 1 1 0 0 0 0 1 1 1 1 | | 0 1 0 1 0 1 0 1 LANCE internal loopback test LANCE IBUS parity error test LANCE CRC logic test LANCE collision detection test LANCE multicast address test LANCE broadcast address test LANCE physical address reject test LANCE external loopback test D3 1 1 1 | Physical address ROM test 1 0 1 1 1 0 0 | 1 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 DMA block mover IBUS address register bit test 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 ] 0 1 DMA block mover HBUS address register bit test DMA block mover word count register bit test DMA word mover HBUS address register bit test 1 1 0 0 1 0 0 DMA block mover ITEST test 1 1 1 | 0 0 0 0 | | | | 0 1 DMA UNIBUS access test DMA failure DMA UNIBUS access test UNIBUS NXM error 1 1 0 0 1 1 0 1 0 0 0 DMA word mover data register bit test 1 1 0 1 0 0 1 DMA word mover PCSRO test 1 1 1 | 1 1 1 1 0 0 0 0 1 | 1 1 0 0 | 1 1 1 0 0 0 1 0 1 1 1 1 0 0 0 0 DMA word mover PCSR1, 2, 3 test DMA block mover HBUS to IBUS test DMA block mover IBUS to HBUS test Port command interlock DELUA IBUS loading test 6.2.2 DELUA VAX On-Line Functional Diagnostic (EVDYB¥*) The DELUA VAX on-line functional diagnostic, EVDYB*, verifies all the DELUA functions that the VMS port driver program is capable of using. It is a VAX/VMS Level 2R (on-line only) diagnostic that runs under the VAX diagnostic supervisor (VDS). 6-5 Table 6-2 describes the tests performed by this diagnostic. Table 6-2 DELUA VAX On-Line Functional Diagnostic (EVDYB*) Test Summary No. Name 1 Read Internal ROM Test The internal 16K byte ROM can be read and there are no CRC errors. 2 Read/Write Internal RAM Data patterns can be written to and read from internal RAM memory. 3 Transmit CRC The transmit CRC logic functions properly. 4 Receive CRC The receive CRC logic functions properly. 5 Promiscuous Address The DELUA in the promiscuous mode accepts all frames regardless of the destination address. 6 Enable All Multicast The DELUA in the enable all multicast mode accepts all frames with multicast destination addresses. 7 Station Address The DELUA recognizes the physical, multicast, and broadcast addresses of the node and discards frames with other addresses. 8 No Receive Buffers Available The appropriate error will be flagged if a loopback is attempted and there are no receive buffers in host memory currently available (owned) by the DELUA. 9 DELUA Stress The DELUA functions properly during heavy-traffic loading conditions. 6.2.3 DELUA PDP-11 Functional Diagnostic (CZUAD¥*) The DELUA PDP-11 functional diagnostic, CZUAD, verifies all of the DELUA functions that the port driver program is capable of using. This diagnostic runs under the PDP-11 Diagnostic Supervisor and runs only in stand-alone mode. The DELUA must be connected to an H4080 loopback transceiver to run this diagnostic. The diagnostic program assumes that the only frames to and from the transceiver are the frames that it has sent. If the DELUA is connected to a network and the diagnostic receives a frame sent by another node on the network, it reports errors. Table 6-3 describes the tests performed by the DELUA PDP-11 functional diagnostic CZUAD*. 6-6 Table 6-3 DELUA PDP-11 Functional Diagnostic (CZUAD*) Test Summary No. Name Test | PCSRO READ ACCESS A device is present at the PCSRO UNIBUS address specified. 2 PCSR1 READ ACCESS A device is present at the specified. 3 PCSR1 DELUA ID BIT PCSR1 UNIBUS address Bit (04), and no other bits in the PCSR1 device ID field are set. 4 PCSR2 READ ACCESS A device is present at the PCSR2 UNIBUS address specified. 5 PCSR3 READ ACCESS A device is present at the PCSR3 UNIBUS address specified. 6 PCSR2 STATIC BIT The test reads and writes each bit in PCSR2. 7 PCSR3 STATIC BIT The test reads and writes each bit in PCSR2. 8 SELF TEST Signals the DELUA to run its ROM-based diagnostic selftest. 9 PORT COMMAND No errors occur when a DELUA port command is issued. 10 INTERRUPT LOGIC The DELUA can generate an interrupt. 11 READ INTERNAL ROM Internal ROM. 12 READ/WRITE Internal RAM can be written and read. INTERNAL MEMORY 13 INTERNAL LOOPBACK No errors occur when a frame is transmitted and received in internal loopback mode. 14 CRC CHECKING CRC checking logic is operational. 15 FORCE CRC ERROR CRC error detection is operational. 16 NO RECEIVE BUFFER The appropriate error is flagged if a loopback is attempted and there are no receive buffers in host memory currently available (owned) by the DELUA. 17 DISABLE RECEIVE The appropriate error is flagged if CHAINING the receive buffer in host memory is too small and receive chaining is disabled so that the DELUA cannot place the rest of the frame in another receive buffer. 18 TRANSMIT CHAINING ERROR The DELUA can set the buffer length error (BUFL) in the transmit descriptor ring. 6-7 Table 6-3 DELUA PDP-11 Functional Diagnostic (CZUAD*) Test Summary (Cont) No. Name Test 19 DATA CHAINING The DELUA can chain together more than one transmit data buffer and send the data as a single frame. Also, when the DELUA receives a frame that is larger than the receive data buffer, it continues the frame into the next receive data buffer. 20 PHYSICAL ADDRESS When the DELUA is set to ignore multicast frames, it receives only frames sent to its Ethernet physical address. 21 MULTICAST ADDRESS When the DELUA is set to receive multicast frames, it receives frames of the specified multicast groups. 22 PROMISCUOUS ADDRESS When the DELUA is set to receive frames from all Ethernet addresses, it does. 23 ENABLE ALL MULTICAST The DELUA in multicast mode accepts all frames with multicast destination addresses. 24 INTERNAL LOOPBACK TRANSMIT LENGTH ERROR The DELUA flags an error when the diagnostic attempts to send an internal loopback frame that is longer than 36 bytes or 32 bytes if DTCR is 0. See Section 5.1. 25 SIMULTANEOUS OPERATIONS Simultaneous operations can be performed. 26 EXTERNAL LOOPBACK (Manual Intervention Required) Using an external loopback connector, this ensures that no errors occur when a frame is transmitted and received in 27 PRINT DEVICE external loopback mode. Prints the default physical address, PARAMETERS the microcode revision, and the switch pack settings. 6.2.4 DEC/X11 DELUA Test CXUAD* The DEC/X11 DELUA test achieves maximum UNIBUS activity by transmitting many frames of data. The DELUA must be connected to an H4080 loopback transceiver to run this diagnostic. The diagnostic program assumes that only the frames to and from the transceiver are the frames that it has sent. If the DELUA is connected to a network and the diagnostic receives a frame sent by another node on the network, it reports errors. 6.2.5 NI Exerciser CZUAC* /EVDWC* The Network Interconnect Exerciser (NIE) sets up frame traffic between many nodes on the network. Refer to the Network Interconnect Exerciser User’s Guide (order number AA-HIO6A-TE) for information on the NI Exerciser diagnostic test. 6-8 APPENDIX A FLOATING DEVICE ADDRESSES AND VECTORS A.1 FLOATING DEVICE ADDRESSES AND VECTOR ADDRESSES UNIBUS addresses from 760010 through 763776 are floating device addresses (see Figure A-1) used as register addresses for devices interfacing with a PDP-11 or VAX system. 777 777 DIGITAL EQUIPMENT 2K WORDS CORPORATION (FIXED ADDRESSES) 770 000 DR11-C 767 777 1K WORDS t USER ADDRESSES 764 000 763 777 1. 1K WORDS FLOATING ADDRESSES DIGITAL EQUIP CORP (DIAGNOSTICS) 760 010 760 006 760 000 757 777 001 000 000 777 80 1 VECTORS FLOATING VECTORS 000 300 000 277 48 TRAP & INTERRUPT VECTORS VECTORS 000 000 MK-2190 Figure A-1 UNIBUS Address Map A.2 FLOATING DEVICE ADDRESSES Assign device addresses according to the following procedure to allow the auto-configuration program to properly configure the operating system to communicate with all devices that use the floating addresses. Assign addresses to devices according to the order in which they are shown in Table A-1. The floating address space starts at 760010. The DJ11 option is the first device in the table. If the system has a DJ11 option, assign it address 760010. If the system has another DJ11 option, add the octal modulus shown in Table A-1 to determine the address (760020 in this case). Leave a gap of octal 10 unused addresses when switching to a new device type. Leave a gap of octal 10 unused addresses for each type of device that does not exist in the system. The example in Section A.4 shows how this address assignment procedure is used. Table A-1 Priority Rank Floating Device Address Ranking Sequence Option 1 2 DJ11 3 DQI11 4 DU11, DUV11 DH11 5 DUPI11 6 LK11-A 7 DMC11/DMRI11 8 9 DZ11*/DZV11, DZS11/DZ32 KMCl11 11 VMV2] 12 VMV3l1 DWR70 13 14 15 16 KW11-C 17 Reserved 18 20 21 22 23 24 25 RX11/RX211 RXVI1/RXV21 DR11-W DR11-B DMPI11 DPV11 ISB11 DMV11 DEUNA/DELUA 26 27 28 29 UDASO0 DMF32 DMSI11 VS100 19 RL11,RLV11 LPA11-K Decimal Size 4 Octal Modulus 8 10 20 4 10 4 10 4 10 4 10 4 10 (DMC11 before DMR11) 10 (DZ11 before DZ32) 4 4 10 4 10 8 4 4 8 20 10 10 (after first) 20 (after first) 4 10 4 10 4 10 (after first) (RX11 before RX211) 10 4 4 4 4 4 10 10 (after second) 10 10 8 20 4 10 (after first) 2 16 (DEUNA before DELUA) 4 (after first) 40 6 8 20 20 * DZ11-E and DZ11-F are considered as two DZ11 options. A-2 A.3 FLOATING VECTOR ADDRESSES UNIBUS addresses from 300 to 777 are floating vector addresses used for devices interfacing with a PDP-11 or VAX system. Do not leave any gaps of unused addresses between floating vector addresses unless they are required by the physical hardware of the device. In data communications devices, the receive vector must be on a zero boundary; the transmit vector must be on an octal 4 boundary. Multiple devices of the same type should be assigned vectors sequentially. Table A-2 lists the floating vector assignment sequence. Table A-2 Priority Rank 1 1 2 2 2 2 2 3 4 5 6 7 8 9 10 11 12 13 14 14 14 15 16 17 17 18 19 20 21 22 23 24 25 26 26 27 Floating Vector Assignment Sequence Option Decimal Size Octal Modulus DCl11* TUS8* KL11+ DL11-A¥} DL11-B¥ DLV11-Jt DMVI11, DLVII-Ft DPI11 DMI11-A DNI11 DM11-BB/BA DH11 modem control DR11-A, DRVI1I1-B DR11-C, DRV11] PA611 (reader+punch) LPDI11 DTO07 DX11 DL11-C DL11-D DL11-E/DLVI1I1-E DJ11 DH11 GT40 VSV11 LPS11 DQIl11 KWI11-W, KWV1l DU11, DUV11 DUP11 DV11+modem control LKI11-A DWUN DMCIl11 4 4 4 4 4 16 4 4 4 2 2 2 4 4 8 4 4 4 4 4 4 4 4 8 8 12 4 4 4 4 6 4 4 4 10 10 10 10 10 10 10 10 10 4 4 4 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 DMRI11 DZ11/DZV1l1, 4 4 A-3 10 (DMC before DMR) 10 (DZ11 before DZ32) Table A-2 Floating Vector Assignment Sequence (Cont) Priority Rank Option Decimal Octal Size Modulus 28 KMCl11 29 4 LPP11 10 30 4 VMV2] 10 31 4 VMV3l] 10 4 10 32 VTVOl1 33 34 DWR70 RL11/RLV11 TS11 35 36 37 38 39 LPA1l-K IP11/1P300 46 KWI11-C RXI11/RX211 RXV11/RXV2l DR11-W DR11-B DMPI11 DPV11 MLI11 ISB11 DMVI11 47 DEUNA/DELUA 48 50 51 52 UDASO0 KMSI11 PCL11-B VS100 40 41 42 43 44 45 4 10 4 10 2 2 4 4 (after the first) 4 (after the first) 10 2 4 2 4 4 (after the first) 10 4 (after the first) (RX11 before RX211) 4 4 (after the first) 10 10 4 (MASSBUS device) 10 10 2 4 (after the first) 2 6 4 2 (DEUNA before DELUA) 4 (after the first) 10 10 4 2 2 4 4 2 4 * There is no standard configuration for systems that contain both a DC11 option and a TUS8 option. t A KL11 option or DL11 option used as the console, uses a fixed vector. A4 DEVICE AND VECTOR ADDRESS ASSIGNMENT EXAMPLE This section contains an example of how to assign floating device and vector addresses. This system contains the following devices to be assigned floating addresses. 1 DJ11 1 DHI1 2 DQIl1s 2 DUPI s 2 DMR11s 2 DELUAs The devices for this system should be assigned device and vector addresses as shown in Table A-3. Table A-3 Device and Vector Address Assignments Option Device Address Vector Address Comment DJ11 760010 300 Only one DJ11 option DH11 760020 Gap left between DJ11 option and the next device 760030 Gap - The next device, a DHI11 option, must start on an address boundary that is a multiple of 20 760040 310 760060 Only one DH1! option Gap left between DHI1 option and the next device DQIl1 760070 320 First DQ11 option DQI11 760100 330 Second DQI11 option 760110 Gap between last DQI11 option used and the next device 760120 Gap left for DU11 option (none in system) DUPI11 760130 340 First DUP11 option DUPI1 760140 350 Second DUPI11 option 760150 Gap left between last DUP11 option and the next device 760160 Gap left for LK11-A option (none in system) DMRI11 760170 360 First DMR11 option DMRI11 760200 370 Second DMR11 option 760210 Gap left between last DMR 11 option and the next device 760220 Gap left for DZ11 option (none in system) 760230 Gap left for KMCI11 option (none in system) 760240 Gap left for VMV21 option (none in system) 760260 Gap left for VMV31 option (none in system), must start on an address boundary that is a multiple of 20 and also leave a gap of 20 760300 Gap left for DWR70 option (none in system) 760310 Gap left for RL11 option (none in system) A-5 Table A-3 Option Device Address Device and Vector Address Assignments (Cont) Vector Address 760320 Comment Gap left for LPA11-K option (none in system), must start on an address boundary that is a multiple of 20 and also leave a gap of 20 760340 Gap left for KW11-C option (none in system) 760350 Gap left for reserved device 760360 Gap left for RX11 option (none in system) 760370 Gap left for DR11-W option (none in system) 760400 Gap left for DR11-B option (none in system) 760410 Gap left for DMP11 option (none in system) 760420 Gap left for DPV11 option (none in system) 760430 Gap left for ISB11 option (none in system) 760440 Gap left for DMV 11 option (none in system), must start on an address boundary that is a multiple of 20 and also leave a gap of 20 : DEUNA or DELUA 774510 120 First DEUNA/DELUA addresses DEUNA or 760460 400 Second DEUNA/DELUA uses floating device and vector DELUA addresses A-6 uses fixed device and vector INDEX D DC UNIBUS loads, 2-1 Descriptor ring read/write ring format ancillary A AC UNIBUS loads, 2-1 ‘Address fixed device address, 2-4 fixed vector address, 2-5 floating address assignment example, A-4 floating device address, A-2 floating vector address, A-3 read default physical ancillary function, 4-10 read/write multicast list ancillary function, 4-11 read/write physical address ancillary function, 4-11 Ancillary functions summary, 3-11 Ancillary functions overview, 3-1 Books, related, 1-11 Boot boot frame format, 5-5 boot option descriptions, 5-1 boot port command function sequence, 5-4 option selection switches, 2-7 fixed UNIBUS address, 2-4 floating address assignment example, A-4 floating UNIBUS address, A-2 Diagnostic tests DEC/X11, 6-8 NI Exerciser, 6-8 PDP-11 functional, 6-6 selftest, 6-1 VAX functional, 6-5 DMA subsystem overview, 1-9 Documents, related, 1-11 Dump/load internal memory ancillary function, 4-26 E Ethernet configuration, 1-2 frame format, 1-6 overview, [-1 remote boot function sequence, 5-1, 5-2 remote boot on powerup function sequence, 5-4 C Commands ancillary functions, overview, 3-1 interfering with message processing, 3-9 port command bit descriptions, 4-3 port commands, overview, 3-1 summary, 3-11 Configuration Ethernet, 1-2 Control and status registers bit descriptions, 4-1 hardware overview, 1-9 programming overview, 3-1 Counters, read and clear ancillary function, 4-15 CSRs, control and status registers bit descriptions, 4-1 hardware overview, 1-9 programming overview, 3-1 function, 4-13 receive data buffer format, 4-42 receive descriptor ring entry bit format, 4-37 transmit data buffer format, 4-40 transmit descriptor ring entry bit format, 4-34 Device F Floating address address assignment example, A-4 device address assignment, A-2 vector address assignment, A-3 Frame, Ethernet data frame format, 1-6 Functions ancillary, summary, 3-11 Functions ancillary functions, overview, 3-1 functional states, description, 3-3 functional states, status bits, 4-6 interfering with message processing, 3-9 port commands, overview, 3-1 H H4080 loopback transceiver setup, 2-11 INDEX-1 PCSRs, control and status registers bit descriptions, 4-1 hardware overview, 1-9 programming overview, 3-1 | ID read/write system ID parameters ancillary function, 4-28 request ID frame format, 5-14 system ID frame format, 5-16 Installation, 2-1 Physical address read default physical address ancillary function, 4-10 read/write physical address ancillary function, 4-11 L LANCE, subsystem overview, 1-9 LEDs bulkhead assembly, power to transceiver, 2-12 error and status codes, 6-4 Load/dump internal memory ancillary function, 4-26 Loopback internal and external loopback mode description, 5-11 loopback frame format, 5-13 loopback mode bit descriptions, 4-24 loopback on network, 5-12 loopback transceiver setup, 2-11 troubleshooting loopback failures, 6-1 M Memory Direct Memory Access (DMA) subsystem, -9 memory load with transfer address frame format, 5-10 memory subsystem overview, 1-8 Microcode dump/load internal memory ancillary function, 4-26 loading procedure, 5-18 start microaddress ancillary function, 4-9 Update (patch) description, 5-19 Microprocessor microprocessor subsystem overview, 1-8 Mode register, read/write ancillary function, 4-22 Multicast address list, read/write ancillary function, 4-11 N Network configuration, 1-2 No-op ancillary function, 4-8 P PCB (port control block) bit descriptions, 4-7 overview, 3-1 Port control block (PCB) bit descriptions, 4-7 overview, 3-1 Powerup sequence, 3-8 Program request frame format, 5-7 Programming Overview, 3-1 R Read default physical address ancillary function, 4-10 Receive data frame, sequence, 3-2 LANCE subsystem overview, 1-9 receive data buffer format, 4-42 Registers, PCSR bit descriptions, 4-1 hardware overview, 1-9 programming overview, 3-1 Request ID frame format, 5-14 Request program frame format, 5-7 Reset sequence, 3-8 Restart and stop sequence, 3-9 Ring, descripto receive data buffer format, 4-42 receive descriptor ring entry bit format, 4-37 transmit descriptor ring entry bit format, 4-34 Ring, descriptor read/write ring format ancillary function, 4-13 transmit data buffer format, 4-40 ROM, memory subsystem overview, 1-8 S Selftest error and status codes, 6-4 Specifications, 1-10 Start microaddress ancillary function, 4-9 States, functional, description, 3-3 States, functional, status bits, 4-6 Static electricity cautions, 2-2 Status information PCSRO interrupt status bits, 4-1 read and clear counters ancillary function, 4-15 INDEX-2 read and clear status ancillary function, 4-24 Stop and restart sequence, 3-9 System ID frame format, 5-16 T address assignment example, A-4 fixed device address, 2-4 fixed vector address, 2-5 floating device address, A-2 floating vector address, A-3 Transceiver, loopback setup, 2-11 Transmit data frame, sequence, 3-2 LANCE subsystem overview, 1-9 transmit data buffer format, 4-40 Troubleshooting flowchart, 6-1 U Vv Vector fixed address, 2-5 floating address, A-3 floating address assignment example, A-4 VelostatTM static discharge system, 2-2 UNIBUS INDEX-3
Home
Privacy and Data
Site structure and layout ©2025 Majenko Technologies