0% found this document useful (0 votes)
200 views8 pages

User Sequence Item

This document describes a test plan for a tri-mode Ethernet MAC device. It includes 17 test cases to verify the functionality of the MAC registers, basic data transfers at different speeds and duplex modes, packet handling for normal and error frames, and multicast/broadcast behavior. The test cases will check the MAC's behavior during reset, register fields, signal toggling, frame transmission for various packet types and conditions, and address/packet formatting.

Uploaded by

sureshchandra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
200 views8 pages

User Sequence Item

This document describes a test plan for a tri-mode Ethernet MAC device. It includes 17 test cases to verify the functionality of the MAC registers, basic data transfers at different speeds and duplex modes, packet handling for normal and error frames, and multicast/broadcast behavior. The test cases will check the MAC's behavior during reset, register fields, signal toggling, frame transmission for various packet types and conditions, and address/packet formatting.

Uploaded by

sureshchandra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

TOP

TEST

USER SEQUENCE ITEM USER SEQUENCE

ENV

REGISTER BLOCK

USER AGENT
REG ADAPTER

SEQUERNCER DRIVER

USER
MONITOR INTF

S
C PHYSICAL AGENT
O
SEQUERNCER DRIVER
DUT
R
E
B PHYSICAL
MONITOR
O INTF
A
R
D
CONFIG AGENT
SEQUERNCER DRIVER

MONITOR CONFIG
INTF

PHYSICAL SEQUENCE ITEM PHYSICAL SEQUENCE

CONFIGURATION SEQUENCE ITEM CONFIGURATION SEQUENCE


1.) Trimode Ethernet MAC -DUT
10_100_1000 Mbps tri-mode ethernet MAC implements a MAC controller conforming to IEEE
802.3 specification. It is designed to use less than 2000 LCs/LEs to implement full function. It
will use inferred RAMs and PADs to reduce technology dependance.

2.) USER_SEQ_ITEM/PHYSICAL_SEQ_ITEM/CONFIGURATION_SEQ_ITEM
Is the basic building block for Stimulus generation and Coverage (can be data, address, delay,
constraints, etc), provides lowest level transaction and can be combined into a sequence.
Describes the transaction level items for the stimulus driving. For USER part it has address data
like items. For PHYSICAL part we have properties like data and address for physical
transactions and for CONFIGURATION part we have properties like data and address for
physical transactions.

3.) USER/PHYSICAL/CONFIGURATION SEQUENCE


Builds transaction from sequence items, builds higher level transaction from sequences and
coordinates execution of its items/sub-items.

4.) USER/PHYSICAL/CONFIGURATION SEQUENCER


It selects multiple sequences and serves as an arbiter for controlling transaction flow of UVM. It
uses TLM port for connection (Sequencer Driver) and handshake (Sequencer Driver) during
communication.

5.) USER/PHYSICAL/CONFIGURATION DRIVER


It drives the stimulus on to the DUT interface. Requests sequence items from sequencer and drives
sequence items into interface. When operating on RTL model interface, converts transactions level to
signal level and has a virtual interface to connect to DUT interface

6.) USER/PHYSICAL/CONFIGURATION MONITOR


Gets transactions from collector or TLM interface, provides coverage, checking and makes
transactions available for consumption. It samples the DUT interface and captures the
information there in transactions that are sent out to the scoreboard and functional coverage
monitors for further analysis.

7.) USER/PHYSICAL/CONFIGURATION AGENTS


For Trimode ethernet MAC, we have two different signal interfaces, each of which have their
own protocol. The UVM agent collects together a group of uvm_components focused around a
specific pin-level interface. The purpose of the agent is to provide a verification component
which allows users to generate and monitor pin level transactions.

8.) Scoreboard
It compares the data coming from USER and PHYSICAL interface. Receives transactions from
interface UVCs and checks transactions for expected device behavior. It is likely to include an
abstract reference model and is located inside module UVC.
10.) Environment
The environment, or env, is a container component for grouping together sub-components
orientated around a block, or around a collection of blocks at higher levels of integration.

TEST PLAN

TRI-MODE ETHERNET MAC TEST PLAN


DUT: TRI-MODE ETHERNET MAC
SL
DESCRIPTI IMPLEMENTATI STATU PASS/FAI
N TEST CASE
ON ON S L
O
REGISTER CHECKING
During reset
Checking the
condition the
default values
1 reset_check registers will be
set in the
configured to some
register block
default modes

Writing and reading


Checking the
data as sweep write,
2 register address check addressing of
sweep read to check
register fields
the address decoding
register field
Checking the configuration
register configuration configuration checking using
3
check of register frontdoor and
fields backdoor access
using RAL
SIGNAL CHECKING
all the interface
Toggling every signals have to be
4 signal toggle check bits of toggled and
interface response must be
checked
BASIC DATA TRANSFERS
checking different
Driving types of frames like
5 frame_types_check different types Basic, Q_tagged,
of packets Envelope frames,
jumbo frames
data transfer in
data transfer in
different duplex
6 mode_check different
modes like half and
duplex modes
full duplex
data transfer
data transfer in
checking in different
7 speed_check different speed
modes like 10Mbps,
modes
100Mbps, 1Gbps
TRANSMISSION PACKET HANDLING

driving normal transmitting normal


8 normal_frame_check
packets frames

driving
FCS_error_packet_chec transmitting frames
9 packets with
k with crc error
CRC error

driving
length_error_packet_che transmitting frames
10 packets with
ck with length error
length error
transmitting frames
driving with size less than
underframe_packet_che packets with the min size and
11
ck size less than check whether zero
minimum size padding is
happening
transmitting frames
driving
with size more than
overframe_packet_chec packets with
12 the max size and
k size more than
check the behaviour
maximum size
of MAC

driving transmitting frames


packets with with and without crc
14 CRC_check
and without attached from user
CRC side

driving transmitting frames


15 add_error_packet_check packets with with errors in
error address address field
driving transmitting
16 broadcast_frame_check broadcast
frames broadcast frames

transmitting frames
driving packet
with and without
with and
17 packet_wo_sa_check source address
without source
attached from user
address
side
RECEPTION PACKET HANDLING

driving normal receiving normal


18 normal_frame_check
packets frames

driving receiving frames


FCS_error_packet_chec
19 packets with with crc error and
k
CRC error check the output

driving receiving frames


length_error_packet_che
20 packets with with length error
ck
length error and check the output

driving receiving frames


underframe_packet_che packets with with size less than
21
ck size less than the min size and
minimum size check response

receiving frames
driving
with size more than
overframe_packet_chec packets with
22 the max size and
k size more than
check the response
maximum size
of MAC

receiving frames
driving
with error in SFD
23 start_error_check packets with
and check the
SFD error
response
driving
receiving frames
packets with
24 CRC_check with and without crc
and without
attached
CRC
driving receiving frames
packets with errors in
25 add_error_packet_check
with error address field and
address check the response

driving
receiving broadcast
26 broadcast_frame_check broadcast
frames
frames

driving packet receiving frames


with and with error in source
27 packet_wo_sa_check
without source address and check
address the response

driving receiving packets


packet_wo_preamble_ch packets without preamble
28
eck without and check the
preamble response

FLOW CONTROL CHECKING


checking the carrier sense will be
data transfer asserted in different
29 cs_error_check with the time stamps and
presence of check the behavior
carrier sense of MAC

frame lost errors


checking the
have to be generated
30 frame_lost_error frame lost
thereby checking the
error
response of MAC

collision detection
checking data will be asserted at
flow control different time
31 cd_check
when collision stamps and the
is detected behavior of MAC is
observed.
checking the
maximum collision detection
retry of a will be asserted for
32 max_retry_check packet at the long time and check
presence of the maximum retry
collision count of the MAC
detection
checking the
packet packet transfers
transfers with checking with
33 frame_gap_check
different different IFG values
interpacket set
frame gaps
different scenarios
checking the will be created for
control_frame_gen_chec generation of generation of control
34
k control frames frames like pause
from MAC frame and check the
behavior
checking the
collision will be
generation of
provided and the
35 jam_signal_check jam signals
propagation of jam
with different
signals will be tested
jam sizes
checking the
working of tx fifo
36 fifo_check data FIFOs of
and rx fifo is tested
MAC

late collision will be


Checking late asserted and the
37 late_collision_check
collision errors behavior of MAC is
tested
checking the
data transmission of
transmission packets are tested
38 source_add_check with different with different source
source addresses appended
addresses to it
configured
reception of
different packets
with different
checking data
destination
reception with
addresses are
39 dest_add_check different
allowed and and to
destination
check behavior. It
address
must take packets
with its own address
only
40 broadcast_filter_check checking broadcast packets
broadcast are transferred and
filtering checking its filter
parameters

You might also like