Electronic Components Datasheet Search
  English  ▼

X  

DP83952 Datasheet(PDF) 39 Page - National Semiconductor (TI)

[Old version datasheet] Texas Instruments acquired National semiconductor.
Part # DP83952
Description  Repeater Interface Controller with Security Features (RIC II)
PDF  90 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  NSC [National Semiconductor (TI)]
Direct Link  http://www.national.com
Logo NSC - National Semiconductor (TI)

DP83952 Datasheet(HTML) 39 Page - National Semiconductor (TI)

Back Button DP83952 Datasheet HTML 35Page - National Semiconductor (TI) DP83952 Datasheet HTML 36Page - National Semiconductor (TI) DP83952 Datasheet HTML 37Page - National Semiconductor (TI) DP83952 Datasheet HTML 38Page - National Semiconductor (TI) DP83952 Datasheet HTML 39Page - National Semiconductor (TI) DP83952 Datasheet HTML 40Page - National Semiconductor (TI) DP83952 Datasheet HTML 41Page - National Semiconductor (TI) DP83952 Datasheet HTML 42Page - National Semiconductor (TI) DP83952 Datasheet HTML 43Page - National Semiconductor (TI) Next Button
Zoom Inzoom in Zoom Outzoom out
 39 / 90 page
background image
50 Functional Description (Continued)
PROCESSOR ACCESS CYCLES
Access to the RIC II’s on-chip registers is made via its proc-
essor interface This utilizes conventional non-multiplexed
address (5-bit) and data (8-bit) busses The data bus is also
used to provide data and address information to off-chip
display latches during display update cycles While perform-
ing these cycles the RIC II behaves as a master of its data
bus Consequently a TRI-STATE bi-directional bus trans-
ceiver eg
74LS245 must be placed between the RIC II
and any processor bus
RIC II provides the following scheme to facilitate faster reg-
ister accesses Lower Event Information Register (Page 1H
Address 1FH) has Disable LED Update bit DLU which
when it is set then RIC II stops the LED updates This caus-
es the data bus to be no longer shared and therefore RIC II
is always in a slave access mode In this mode the maxi-
mum readwrite cycle time is reduced to approximately
400 ns
The processor requests a register access by asserting the
read ‘‘RD’’ or write ‘‘WR’’ input strobes The RIC II responds
by finishing any current display update cycle and asserts the
TRI-STATE buffer enable signal ‘‘BUFEN’’ If the processor
cycle is a write cycle then the RIC II’s data buffers are dis-
abled to prevent contention In order to interface to the
RIC II in a processor controlled system it is likely a PAL
device will be used to perform the following operations
1 locate the RIC II in the processor’s memory map (address
decode)
2 generate the RIC II’s read and write strobes
3 control the direction signal for the 74LS245
An example of the processor and display interfaces is
shown in
Figure 5-12
INTERRUPT HANDLING
The DP83952 RIC II offers an alternate method for a faster
access to determine the source of the Event Logging Inter-
rupt (ELI) then the DP83950 RIC
For an event logging interrupt due to flag found
the
DP83950 RIC
requires the following scheme
1 Read the Page Select Register (Address 10H) to locate
the source of Event Logging Interrupt
2 Read all the Port Event Recording Registers (Page 1H
Address 11H to 1DH) to find the port and the event re-
sponsible for Event Logging Interrupt
DP83952 RIC II
allows the following alternate scheme for a
faster access
1 Read Page Select Register (Address 10H) to locate the
source of Event Logging Interrupt
2 Read the Event Information Registers (Page 1H address-
es 1EH and 1FH) to locate the port responsible for inter-
rupt
3 Read the Event Recording register of that port to find
which specific event caused the Event Logging Interrupt
60 Hub Management Support
The RIC II provides information regarding the status of its
ports and the packets it is repeating This data is available in
three forms
1 Counted EventsNetwork events accumulated into the
RIC II’s 16-bit Event Counter Registers
2 Recorded EventsNetwork events that set bits in the
Event Record Registers
3 Hub Management Status packetsThis is information
sent over the Management Bus in a serial function to be
decoded by an Ethernet Controller board
The counted and recorded event information is available
through the processor interface This data is port specific
and may be used to generate interrupts via the Event Log-
ging Interrupt ‘‘ELI’’ pin Since the information is specific to
each port each repeater port has its own event record reg-
ister and event counter The counters and event record reg-
isters have user definable masks which enable them to be
configured to count and record a variety of events The
counters and record registers are designed to be used to-
gether so that detailed information ie a count value can
be held on-chip for a specific network condition More gen-
eral information ie the occurrence of certain types of
events may be retained in on-chip latches Thus the user
can configure the counters to increment upon a rapidly oc-
curring event (most likely to be used to count collisions)
and the record registers may log the occurrence of less
frequent error conditions such as jabber protect packets
61 EVENT COUNTING FUNCTION
The counters may increment upon the occurrence of one of
the categories of event as described below
Potential sources for Counter increment
Jabber Protection (JAB)
The port counter increments if
the length of a received packet from its associated port
causes the repeater state machine to enter the jabber pro-
tect state
Elasticity Buffer Error (ELBER)
The port counter incre-
ments if a Elasticity Buffer underflow or overflow occurs dur-
ing packet reception The flag is held inactive if a collision
occurs during packet reception or if a phase lock error de-
scribed below has already occurred during the repetition of
the packet
Phase Lock Error (PLER)
A phase lock error is caused if
the phase lock loop decoder looses lock during packet re-
ception Phase lock onto the received data stream may or
may not be recovered later in the packet and data errors
may have occurred This flag is held inactive if a collision
occurs
Non-SFD Packet (NSFD)
If a packet is received and the
start of frame delimiter is not found the port counter will
increment Counting is inhibited if the packet suffers a colli-
sion
Out of Window Collision (OWC)
The out of window colli-
sion flag for a port goes active when a collision is experi-
enced outside of the network slot time
Transmit Collision (TXCOL)
The transmit collision flag for
a port is enabled when a transmit collision is experienced by
the repeater Each port experiencing a collision under these
conditions is said to have suffered a transmit collision
39



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90


Datasheet Download

Go To PDF Page


Link URL



Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link to Datasheet    |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com