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.

12.0 Loopback Diagnostics (Continued)<br />

Note 1: CDH is set, CRS is not set since it is generated by the external<br />

encoder/decoder.<br />

Note 1: CDH and CRS should not be set. The TSR however, could also<br />

contain 01 H,03H,07H and a variety of other values depending on whether<br />

collisions were encountered or the packet was deferred.<br />

Note 2.Will contain OSH if packet is not transmittable.<br />

Note 3: During externalloopback the NIC is now exposed to network traffic.<br />

it Is therefore possible for the contents of both the Receive portion of the<br />

FIFO and the RSR to be corrupted by any other packet on the network. Thus<br />

in a live network the contents of the FIFO and RSR should not be depended<br />

on. The NIC will still abide by the standard CSM<strong>Al</strong>CD protocol in extemal<br />

loopback mode. (i.e. The network will not be disturbed by the loopback<br />

packet).<br />

Nota 4: <strong>Al</strong>l values are hex.<br />

CRC AND ADDRESS RECOGNITION<br />

The next three tests exercise the address recognition logic<br />

and CRC. These tests should be performed using internal<br />

loop back only so that the N IC is isolated from interference<br />

from the network. These tests also require the capability to<br />

generate CRC in software.<br />

The address recognition logic cannot be directly tested. The<br />

CRC and FAE bits in the RSR are only set if the address of<br />

the packet matches the address filters. If errors are expected<br />

to be set and they are not set, the packet has been<br />

rejected on the basis of an address mismatch. The following<br />

sequence of packets will test the address recognition logic.<br />

The DCR should be set to 40H, the TCR should be set to<br />

03H with a software generated CRC.<br />

NETWORK MANAGEMENT FUNCTIONS<br />

Network management capabilities are required for maintenance<br />

and planning of a local area network. The NIC supports<br />

the minimum requirement for network management in<br />

hardware, the remaining requirements can be met with software<br />

counts. There are three events that software alone<br />

can not track during reception of packets: CRC errors,<br />

Frame <strong>Al</strong>ignment errors, and missed packets.<br />

Since errored packets can be rejected, the status associated<br />

with these packets is lost unless the CPU can access the<br />

Receive Status Register before the next packet arrives. In<br />

situations where another packet arrives very quickly, the<br />

CPU may have no opportunity to do this. The NIC counts<br />

the number of packets with CRC errors and Frame <strong>Al</strong>ignment<br />

errors. S-bit counters have been selected to reduce<br />

overhead. The counters will generate interrupts whenever<br />

their MSBs are set so that a software routine can accumulate<br />

the network statistics and reset the counters before<br />

overflow occurs. The counters are sticky so that when they<br />

reach a count of 192 (COH) counting is halted. An additional<br />

counter is provided to count the number of packets NIC<br />

misses due to buffer overflow or being offline.<br />

The structure of the counters is shown below:<br />

CIIlRO ,RAME ALIGNMENT ERRORS COUNTER<br />

r+<br />

CIIlRl CRC ERRORS COUNTER<br />

r+ MS8jo-<br />

MS8<br />

INTERRUPT<br />

CNlR2 MISSEO PACI

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

Saved successfully!

Ooh no, something went wrong!