If an NCP transmit or receive operation is in progress, it continues until the CSP microcode stops recep-
tion of data for the receive command, or stops transmission of data and sets the transmission line to mark.
FESH Internal Checkers
Data Parity Checkers
All the microcode (DMA layer, CSP layer, bit-layer, byte-layer) and data are
checked for parity when the FESH internal buffers are read or written.
NCP Buffer Handling Logic Checker
In order to check that the hardware logic which calculates
the NCP buffer data area address from the NCP buffer prefix is working properly, the transmit and receive
byte layer microcodes perform a predetermined calculation during inactivity periods.
:
If there is a mis-
match between the result of the calculation and the predetermined result, the FESH hardware reports an
internal error condition.
Reporting
When any of the above checkers becomes active:
The FESH:
– Stores the corresponding error condition in an error register.
– Interrupts the CSP microcode at level 0.
The CSP microcode:
– Stops the transmit and receive operations in process.
– In case of transmit, puts the transmit data line at mark.
– In case of receive, stops the phase monitor.
Line Interface Check
A driver check function is implemented on the line interfaces of the FESH (V.35 / X.21).
When a driver check is detected, the hardware:
Sets the driver check bit in the transmission status register.
Interrupts the CSP.
No other action (no line interface disabling) is taken by the hardware.
Error Status
Error Status Byte ð
┌───────────┬────────────────┬──────────────────┬───────────────────────┐
│ Bit
│ Type 1
│ Type 2
│ Type 3
│
├───────────┼────────────────┼──────────────────┼───────────────────────┤
│ x... .... │ R/W (IOH)
│ R/W (AIO)
│ Always ON
│
│ .x.. .... │ I/O bus check
│ I/O bus check
│ Invalid lev.ð interr. │
│ ..x. .... │ Not used
│ Cycle steal grant│ Invalid lev.1 interr. │
│ ...x .... │ I/O bus tag I/O│ I/O bus tag I/O
│ Invalid lev.2 interr. │
│ .... x... │ Halt
│ Halt
│ Microcode check
│
│ .... .x.. │ TA
│ Not used
│ CS/CCU L2 stack overf.│
│ .... ..x. │ TD
│ TD
│ Reject: command on cmd│
│ .... ...x │ Not used
│ Not used
│ Disconnect state
│
└───────────┴────────────────┴──────────────────┴───────────────────────┘
5-28
IBM 3745 Models 130, 150, 160, 170, and 17A: Hardware Maintenance Reference
Содержание 3745 Series
Страница 2: ......
Страница 12: ...x IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 14: ...xii IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 18: ...xvi IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 21: ...3745 Models 130 150 160 and 170 Data Flow Chapter 1 General Information 1 3 ...
Страница 149: ...For RACs 241 to 244 ERR bits Data received from the adapter Chapter 3 Buses 3 57 ...
Страница 166: ...4 14 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 169: ...Chapter 4 Transmission Subsystem TSS 4 17 ...
Страница 255: ...The HPTSS in 3745 Models 130 150 160 and 170 Data Flow Chapter 5 High Performance Transmission Subsystem HPTSS 5 3 ...
Страница 303: ...Figure 6 8 Ring to Ring via Bridge Example 2 Typical Multi Floor Wiring Chapter 6 The Token Ring Subsystem 6 9 ...
Страница 322: ...6 28 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 348: ...7 26 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 625: ...The ESS in 3745 Models 130 150 160 and 170 Data Flow Chapter 12 Ethernet Subsystem ESS 12 3 ...
Страница 668: ...Problem Determination Aid 12 46 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 674: ...X 6 IBM 3745 Models 130 150 160 170 and 17A Hardware Maintenance Reference ...
Страница 708: ......
Страница 711: ......
Страница 712: ...IBM Part Number 03F5010 Printed in Denmark by IBM Danmark A S ð3F5ð1ð SY33 2ð66 4 ...