17.05.2015 Views

~ National ~ Semiconductor - Al Kossow's Bitsavers

~ National ~ Semiconductor - Al Kossow's Bitsavers

~ National ~ Semiconductor - Al Kossow's Bitsavers

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

10.0 Transceiver (Continued)<br />

{also in the (NCFl register) indicates different information<br />

depending on the selected protocol. In 3270 and 3299;<br />

[DEME) is set when B10 of the received frame does not<br />

match the locally generated odd parity on bits B2-B9 of the<br />

received frame. This flag is not part of the receiver error<br />

logic, it functions only as a status flag to the CPU. These<br />

flags are decoded from the last location in the FIFO and are<br />

valid only when [DA VI is asserted; they are cleared by reading<br />

{RTR I and should be checked before accessing that<br />

register.<br />

5250 Modes<br />

The biphase data is inverted in the 5250 protocol relative to<br />

3270/3299 (see the Protocol section-IBM 5250). Depending<br />

on the external line interface circuitry, the transceiver's<br />

biphase inputs and outputs may need to be inverted by asserting<br />

the [RIN) (Receiver INvert) and [TIN) (Transmitter<br />

INvert) control bits in {TMR!.<br />

For information on how data must be organized in {TCR I<br />

and {RTR I for input to the transmitter, and how data extracted<br />

from a received frame is organized by the receiver<br />

and mapped into {TSR I and {RTR l. See Figure 43.<br />

To transmit a 5250 message, the least significant 4 bits of<br />

{TCR I must first be set up with the correct address and<br />

parity control information. The station address field (B4-B6)<br />

is defined by {TCR[0-2)l. and [OWPI controls the type of<br />

parity (even or odd) calculated on B4-B15 and transmitted<br />

as B3. When the a-bit data byte is written to {RTR I, the<br />

resulting composite 12-bit word is loaded into the transmit<br />

FIFO, starting the transmitter. The same {TCRI contents<br />

can be used for more than one frame of a multi-frame transmission,<br />

or changed for each frame.<br />

The 5250 protocol defines bits BO-B2 as fill bits which the<br />

transmitter automatically appends to the parity bit (B3) to<br />

form the 16-bit frame. Additional fill bits may be inserted<br />

between frames of a multi-frame transmission by loading<br />

the fill bit register, {FBR I, with the one's compliment of the<br />

number of fill bits to be transmitted. A value of FF (hex),<br />

corresponding to the addition of no extra fill bits. At the<br />

conclusion of a message the transmitter will return to the<br />

idle state after transmitting the 3 fill bits of the last frame (no<br />

additional fill bits will be transmitted).<br />

As shown in Table XXVI, the transceiver can operate in 2<br />

different 5250 modes, designated "promiscuous" and "nonpromiscuous".<br />

The transmitter operates in the same manner<br />

in both modes.<br />

In the promiscuous mode, the receiver passes all received<br />

data to the CPU via the FIFO, regardless of the station address.<br />

The CPU may determine which station is being addressed<br />

by reading ITSR [0-211 before reading {RTR!.<br />

In the non-promiscuous mode, the station address field<br />

(B4-B6) of the first frame must match the 3 least significant<br />

bits of the Auxiliary Transceiver Register, (ATR[0-2) I, before<br />

the receiver will pass the data on to the CPU. II no<br />

match is detected in the first frame of a mes!!age, and if no<br />

errors were found on that frame, the receiver will reset to<br />

idle, looking for a valid start sequence. If an address match<br />

is detected in the first frame of a message, the received<br />

data is passed on to the CPU. For the remainder of the<br />

message all received frames are decoded in the same manner<br />

as the promiscuous mode.<br />

To maintain maximum flexibility, the receiver logic does not<br />

interpret the station address or command fields in determining<br />

the end of a 5250 message. The message typically ends<br />

with no further line transitions after the third fill bit of the last<br />

frame. This end of message must be distinguished from a<br />

loss of synchronization between frames of a multi-byte<br />

transmission condition by looking for line activity some time<br />

after the loss of synchronization occurs. When the loss of<br />

synchronization occurs during fill bit reception, the receiver<br />

monitors the Line Active flag, [LAI, for up to 11 biphase bit<br />

times (11 p.s at the 1 MHz data rate). If [LA) goes inactive at<br />

any point during this period, the receiver returns to the idle<br />

state, de-asserting [RA) and asserting [L T<strong>Al</strong>. II, however,<br />

[LA) is still asserted at the end of this window, the receiver<br />

interprets this as a real loss of synchronization and flags the<br />

appropriate error condition to the CPU. (See the Receiver<br />

Errors section in this Chapter.)<br />

7 654 3 2 I 0<br />

RTR I B71 881 B9IBIOUl1lB12IBI3IBI41<br />

7 6 5 4 3 2 0<br />

lowpi 84 1 85 1 86 ITeR<br />

Twlnax tranltnlalon<br />

T<br />

tranltnit<br />

*<br />

Sync DO DI D2 D3 D4 D5 D6 D7 AD AI A2 Par<br />

T<br />

reoelve<br />

*<br />

7 6 543 2 I 0 7 6 543 2 I 0<br />

RTR I 871 881 B9IBIOUl1lB12IB13IBI41<br />

IB41BSIB61TCR<br />

FIGURE 43. 5250 Frame Assembly/Disassembly Description<br />

TUF 19336-49<br />

2-177

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!