NXP Semiconductors LPC1768 - Receive Status Vector Register; 0 X5000 0160)

UM10360 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
User manual Rev. 3 — 19 December 2013 165 of 841
NXP Semiconductors
UM10360
Chapter 10: LPC176x/5x Ethernet
purposes, because the communication between driver software and the Ethernet block
takes place primarily through the frame descriptors. The status register contents are valid
as long as the internal status of the MAC is valid and should typically only be read when
the transmit and receive processes are halted.Table 161
lists the bit definitions of the
TSV1 register.
10.12.15 Receive Status Vector Register (RSV - 0x5000 0160)
The Receive status vector register (RSV) is a read-only register with an address of
0x5000 0160. The receive status vector register stores the most recent receive status
returned by the MAC. This register is provided for debug purposes, because the
communication between driver software and the Ethernet block takes place primarily
through the frame descriptors. The status register contents are valid as long as the
internal status of the MAC is valid and should typically only be read when the transmit and
receive processes are halted.
Table 162
lists the bit definitions of the RSV register.
Table 161. Transmit Status Vector 1 register (TSV1 - address 0x5000 015C) bit description
Bit Symbol Function Reset
value
15:0 Transmit byte count The total number of bytes in the frame, not counting the
collided bytes.
0x0
19:16 Transmit collision
count
Number of collisions the current packet incurred during
transmission attempts. The maximum number of collisions
(16) cannot be represented.
0x0
31:20 - Unused 0x0
Table 162. Receive Status Vector register (RSV - address 0x5000 0160) bit
description
Bit Symbol Function Reset
value
15:0 Received byte count Indicates length of received frame. 0x0
16 Packet previously
ignored
Indicates that a packet was dropped. 0
17 RXDV event
previously seen
Indicates that the last receive event seen was not long
enough to be a valid packet.
0
18 Carrier event
previously seen
Indicates that at some time since the last receive statistics,
a carrier event was detected.
0
19 Receive code
violation
Indicates that received PHY data does not represent a
valid receive code.
0
20 CRC error The attached CRC in the packet did not match the
internally generated CRC.
0
21 Length check error Indicates the frame length field does not match the actual
number of data items and is not a type field.
0
22 Length out of range
[1]
Indicates that frame type/length field was larger than
1518 bytes.
0
23 Receive OK The packet had valid CRC and no symbol errors. 0
24 Multicast The packet destination was a multicast address. 0
25 Broadcast The packet destination was a broadcast address. 0