
MVTX2602
Data Sheet
30
Zarlink Semiconductor Inc.
Figure 9 - Memory Configuration for 1 Bank, 1 Layer, 2 MB
6.0 Frame Engine
6.1
Data Forwarding Summary
When a frame enters the device at the RxMAC, the RxDMA will move the data from the MAC RxFIFO to the FDB.
Data is moved in 8-byte granules in conjunction with the scheme for the SRAM interface.
A switch request is sent to the Search Engine. The Search Engine processes the switch request.
A switch response is sent back to the Frame Engine and indicates whether the frame is unicast or multicast and its
destination port or ports. A VLAN table lookup is performed as well.
A Transmission Scheduling Request is sent in the form of a signal notifying the TxQ manager. Upon receiving a
Transmission Scheduling Request, the device will format an entry in the appropriate Transmission Scheduling
Queue (TxSch Q) or Queues. There are 4 TxSch Q for each 10/100, one for each priority. Creation of a queue
entry either involves linking a new job to the appropriate linked list if unicast or adding an entry to a physical queue
if multicast.
When the port is ready to accept the next frame, the TxQ manager will get the head-of-line (HOL) entry of one of
the TxSch Qs, according to the transmission scheduling algorithm (to ensure per-class quality of service). The
unicast linked list and the multicast queue for the same port-class pair are treated as one logical queue. The older
HOL between the two queues goes first. For 10/100 ports multicast queue 0 is associated with unicast queue 0 and
multicast queue 1 is associated with unicast queue 2.
The TxDMA will pull frame data from the memory and forward it granule-by-granule to the MAC TxFIFO of the
destination port.
Memory
256 K
32 bits
SRAM
Memory
256 K
32 bits
Data LA_D[63:32]
Data LA_D[31:0]
Address LA_A[20:3]
Bank A (2 M One Layer)
Bootstraps: TSTOUT7 = Open, TSTOUT13 = Open, TSTOUT4 = Open