Electronic Components Datasheet Search
  English  ▼

X  

MPC8540 Datasheet(PDF) 756 Page - Freescale Semiconductor, Inc

Part # MPC8540
Description  MPC8540 PowerQUICC III??Integrated Host Processor Reference Manual
PDF  1302 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  FREESCALE [Freescale Semiconductor, Inc]
Direct Link  http://www.freescale.com
Logo FREESCALE - Freescale Semiconductor, Inc

MPC8540 Datasheet(HTML) 756 Page - Freescale Semiconductor, Inc

Back Button MPC8540 Datasheet HTML 752Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 753Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 754Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 755Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 756Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 757Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 758Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 759Page - Freescale Semiconductor, Inc MPC8540 Datasheet HTML 760Page - Freescale Semiconductor, Inc Next Button
Zoom Inzoom in Zoom Outzoom out
 756 / 1302 page
background image
MPC8540 PowerQUICC III Integrated Host Processor Reference Manual, Rev. 1
14-130
Freescale Semiconductor
Three-Speed Ethernet Controllers
14.6.4 Data Extraction to the L2 Cache
Some applications require the ability to identify selected portions of data within a frame’s data
payload. This process is called extraction; although, the data is not truly removed. Rather than
literarily extracting a section of the data and copying it into a new memory location, the data is
placed in the L2 cache. This allows the processor to quickly access critical frame information as
soon as the processor is ready without having to first fetch the data from main memory. This
reduction in latency can result in a substantial improvement in packet processing throughput.
Extraction functionality is controlled and configured with ATTR and ATTRELI. See
Section 14.5.3.9.1, “Attribute Register (ATTR),” and Section 14.5.3.9.2, “Attribute Extract
Length and Extract Index Register (ATTRELI),” for specific register information.
Offset + 0
8
BC
Broadcast. Written by TSEC. (Only valid if L is set.) Is set if the DA is broadcast
(FF-FF-FF-FF-FF-FF)
Offset + 0
9
MC
Multicast. Written by TSEC. (Only valid if L is set.) Is set if the DA is multicast and not BC
Offset + 0
10
LG
Rx frame length violation. Written by TSEC. (Only valid if L is set.) A frame length greater than
maximum frame length was recognized while MACCFG2[Huge Frame] was set. Note, if
MACCFG2[Huge Frame] is cleared, the frame is truncated to the value programmed in the
Maximum Frame Length register.
Offset + 0
11
NO
Rx non-octet aligned frame. Written by TSEC. (Only valid if L is set.) A frame that contained a
number of bits not divisible by eight was received.
Offset + 0
12
SH
Short frame. Written by TSEC. (only valid if L is set.) A frame length that was less than the
minimum length defined for this channel (MINFLR) was recognized, provided RCTRL[RSF] is
set.
Offset + 0
13
CR
Rx CRC error. Written by TSEC. (Only valid if L is set.) This frame contains a CRC error and
is an integral number of octets in length.This bit is also set if a receive code group error is
detected.
Offset + 0
14
OV
Overrun. Written by TSEC. (Only valid if L is set.) A receive FIFO overrun occurred during
frame reception. If this bit is set, the other status bits, M, LG, NO, SH, CR, and CL lose their
normal meaning and are zero.
Offset + 0
15
TR
Truncation. Written by TSEC. (Only valid if L is set.) Is set if the receive frame is truncated.
This can happen if a frame length greater than maximum frame length was received and the
MACCFG2[Huge Frame] is cleared. If this bit is set, the frame must be discarded and the other
error bits must be ignored as they may be incorrect.
Offset + 2 0–15
Data
Length
Data length. Written by TSEC. Data length is the number of octets written by the TSEC into
this BD’s data buffer if L is cleared (the value is equal to MRBL), or the length of the frame
including CRC, if L is set.
Offset + 4 0–31
Rx Data
Buffer
Pointer
Receive buffer pointer. Written by user. The receive buffer pointer, which always points to the
first location of the associated data buffer, must be 64-byte aligned. The buffer must reside in
memory external to the TSEC.
Table 14-121. Receive Buffer Descriptor Field Descriptions (continued)
Offset
Bits
Name
Description



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 91 92 93 94 95 96 97 98 99 100  ...More


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