![](http://datasheet.mmic.net.cn/Exar-Corporation/XRT94L33IB-L_datasheet_100163/XRT94L33IB-L_129.png)
xr
XRT94L33
3-CHANNEL DS3/E3/STS-1 TO STS-3/STM-1 MAPPER IC DATA SHEET
Rev.1.2.0.
129
1.3.2.2
DATA ACCESS MODES
As mentioned earlier, the Microprocessor Interface block supports data transfer between the XRT94L33 and
the
C/P (e.g., “Read” and “Write” operations) via two modes: the “Programmed I/O” and the “Burst” Modes.
Programmed I/O access is discussed within this revision of the data sheet.
Burst Mode access will be
discussed in the next revision of this data sheet.
1.3.2.3
DATA ACCESS USING PROGRAMMED I/O
“Programmed I/O” is the conventional manner in which a microprocessor exchanges data with a peripheral
device. However, it is also the slowest method of data exchange between the XRT94L33 and the
C/P; as
will be described in this text.
The next two sections present detailed information on Programmed I/O Access, when the XRT94L33 is
operating in the “Intel Mode” and in the “Motorola Mode”.
1.3.3
PROGRAMMED I/O ACCESS IN THE “INTEL” MODE
If the XRT94L33 is interfaced to an “Intel-type”
C/P (e.g., the 80x86 family, etc.), then it should be
configured to operate in the “Intel” mode (by tying the “MOTO” pin to ground). Intel-type “Read” and “Write”
operations are described below.
1.3.3.1
THE INTEL MODE READ CYCLE
Whenever an Intel-type
C/P wishes to read the contents of a register or some location within the Transmit
or Receive Extraction Memory or the J0/J1 Message Buffers, within the XRT94L33, it should do the following.
1. Place the address of the “target” register or buffer location (within the UNI) on the Address Bus input pins
A[14:0].
2. While the
C/P is placing this address value on the Address Bus, the Address Decoding circuitry (within
the user’s system) should assert the CS* (Chip Select) pin of the XRT94L33, by toggling it “l(fā)ow”. This action
enables further communication between the
C/P and the XRT94L33 Microprocessor Interface block.
3. Toggle the ALE_AS (Address Latch Enable) input pin “high”. This step enables the “Address Bus” input
drivers, within the Microprocessor Interface block of the XRT94L33.
4. After allowing the data on the Address Bus pins to settle (by waiting the appropriate “Address” Data Setup
time”), the
C/P should toggle the ALE_AS pin “l(fā)ow”. This step causes the XRT94L33 to “l(fā)atch” the contents
of the “Address Bus” into its internal circuitry. At this point, the address of the register or buffer locations
within the XRT94L33, has now been selected.
5. Next, the
C/P should indicate that this current bus cycle is a “Read” Operation by toggling the RdB_DS
(Read Strobe) input pin “l(fā)ow”.
This action also enables the bi-directional data bus output drivers of the
XRT94L33. At this point, the “bi-directional” data bus output drivers will proceed to drive the contents of the
“l(fā)atched addressed” register (or buffer location) onto the bi-directional data bus, D[7:0].
6.
Immediately after the
C/P toggles the “Read Strobe” signal “l(fā)ow”, the XRT94L33 will toggle the
Rdy_Dtck output pin “l(fā)ow”. The XRT94L33 does this in order to inform the
C/P that the data (to be read
from the data bus) is “NOT READY” to be “l(fā)atched” into the
C/P.
7. After some settling time, the data on the “bi-directional” data bus will stabilize and can be read by the
C/P. The XRT94L33 will indicate that this data can be read by toggling the Rdy_Dtck (READY) signal
“high”.
8. After the
C/P detects the Rdy_Dtck signal (from the XRT94L33 UNI), it can then terminate the Read
Cycle by toggling the RdB_DS (Read Strobe) input pin “high”.
Figure 4 presents a timing diagram which illustrates the behavior of the Microprocessor Interface signals,
during an “Intel-type” Programmed I/O Read Operation.