Bitvis VIP GMII
Quick Access
BFM
This is a stripped-down version of GMII with only data lines.
BFM functionality is implemented in gmii_bfm_pkg.vhd
Signal Record
t_gmii_tx_if
Record element |
Type |
Description |
---|---|---|
gtxclk |
std_logic |
TX reference clock |
txd |
std_logic_vector(7 downto 0) |
TX data lines (to DUT) |
txen |
std_logic |
TX enable |
t_gmii_rx_if
Record element |
Type |
Description |
---|---|---|
rxclk |
std_logic |
RX reference clock |
rxd |
std_logic_vector(7 downto 0) |
RX data lines (from DUT) |
rxdv |
std_logic |
RX data valid |
Configuration Record
t_gmii_bfm_config
Default value for the record is C_GMII_BFM_CONFIG_DEFAULT.
Record element |
Type |
Default |
Description |
---|---|---|---|
max_wait_cycles |
integer |
12 |
The maximum number of clock cycles to wait for the DUT signals before reporting a timeout alert |
max_wait_cycles_severity |
ERROR |
The above timeout will have this severity |
|
clock_period |
time |
-1 ns |
Period of the clock signal |
clock_period_margin |
time |
0 ns |
Input clock period margin to specified clock_period. Will check ‘T/2’ if input clock is low when BFM is called and ‘T’ if input clock is high. |
clock_margin_severity |
TB_ERROR |
The above margin will have this severity |
|
setup_time |
time |
-1 ns |
Generated signals setup time. Suggested value is clock_period/4. An alert is reported if setup_time exceeds clock_period/2. |
hold_time |
time |
-1 ns |
Generated signals hold time. Suggested value is clock_period/4. An alert is reported if hold_time exceeds clock_period/2. |
bfm_sync |
SYNC_ON_CLOCK_ONLY |
When set to SYNC_ON_CLOCK_ONLY the BFM will enter on the first falling edge, estimate the clock period, synchronize the output signals and exit ¼ clock period after a succeeding rising edge. When set to SYNC_WITH_SETUP_AND_HOLD the BFM will use the configured setup_time, hold_time and clock_period to synchronize output signals with clock edges. |
|
match_strictness |
MATCH_EXACT |
Matching strictness for std_logic values in check procedures. MATCH_EXACT requires both values to be the same. Note that the expected value can contain the don’t care operator ‘-‘. MATCH_STD allows comparisons between ‘H’ and ‘1’, ‘L’ and ‘0’ and ‘-’ in both values. |
|
id_for_bfm |
t_msg_id |
ID_BFM |
Message ID used for logging general messages in the BFM |
Methods
All signals are active high.
All parameters in brackets are optional.
For clarity, data_array is required to be ascending, e.g.
variable v_data_array : t_slv_array(0 to C_MAX_BYTES - 1)(7 downto 0);
gmii_write()
Writes data to the DUT. The length and data are defined by the “data_array” argument, which is a t_slv_array. data_array(0) is written first, while data_array(data_array’high) is written last.
gmii_write(data_array, msg, gmii_tx_if, [action_when_transfer_is_done], [scope, [msg_id_panel, [config]]])
Object |
Name |
Dir. |
Type |
Description |
---|---|---|---|---|
constant |
data_array |
in |
t_slv_array |
An array of bytes containing the data to be written |
constant |
msg |
in |
string |
A custom message to be appended in the log/alert |
signal |
gmii_tx_if |
inout |
GMII TX signal interface record |
|
constant |
action_when_transfer_is_done |
in |
Whether to release or hold the TXEN line after the procedure is finished. Useful when transmitting a packet of data through several procedures, e.g. from Ethernet HVVC. Default value is RELEASE_LINE_AFTER_TRANSFER. |
|
constant |
scope |
in |
string |
Describes the scope from which the log/alert originates. Default value is C_BFM_SCOPE (“GMII BFM”). |
constant |
msg_id_panel |
in |
t_msg_id_panel |
Controls verbosity within a specified scope. Default value is shared_msg_id_panel. |
constant |
config |
in |
Configuration of BFM behavior and restrictions. Default value is C_GMII_BFM_CONFIG_DEFAULT. |
-- Examples:
gmii_write((x"01", x"02", x"03", x"04"), "Write 4 bytes", gmii_tx_if);
gmii_write(v_data_array(0 to v_num_bytes - 1), "Write v_num_bytes bytes", gmii_tx_if, HOLD_LINE_AFTER_TRANSFER, C_SCOPE, shared_msg_id_panel, gmii_bfm_config);
gmii_read()
Reads data from the DUT. The received data is stored in the data_array output, which is a t_slv_array. The number of valid bytes in the data_array is stored in data_len. data_array(0) is read first, while data_array(data_array’high) is read last.
gmii_read(data_array, data_len, msg, gmii_rx_if, [scope, [msg_id_panel, [config]]])
Object |
Name |
Dir. |
Type |
Description |
---|---|---|---|---|
variable |
data_array |
out |
t_slv_array |
An array of bytes containing the data to be read |
variable |
data_len |
out |
natural |
The number of valid bytes in the data_array. Note that the data_array can be bigger and that is why the length is returned. |
constant |
msg |
in |
string |
A custom message to be appended in the log/alert |
signal |
gmii_rx_if |
inout |
GMII RX signal interface record |
|
constant |
scope |
in |
string |
Describes the scope from which the log/alert originates. Default value is C_BFM_SCOPE (“GMII BFM”). |
constant |
msg_id_panel |
in |
t_msg_id_panel |
Controls verbosity within a specified scope. Default value is shared_msg_id_panel. |
constant |
config |
in |
Configuration of BFM behavior and restrictions. Default value is C_GMII_BFM_CONFIG_DEFAULT. |
-- Examples:
gmii_read(v_data_array, v_num_bytes, "Read GMII data", gmii_rx_if);
gmii_read(v_data_array, v_num_bytes, "Read GMII data", gmii_rx_if, C_SCOPE, shared_msg_id_panel, gmii_bfm_config);
gmii_expect()
Calls the gmii_read() procedure, then compares the received data with data_exp.
gmii_expect(data_exp, msg, gmii_rx_if, [alert_level, [scope, [msg_id_panel, [config]]]])
Object |
Name |
Dir. |
Type |
Description |
---|---|---|---|---|
constant |
data_exp |
in |
t_slv_array |
An array of bytes containing the data to be expected |
constant |
msg |
in |
string |
A custom message to be appended in the log/alert |
signal |
gmii_rx_if |
inout |
GMII RX signal interface record |
|
constant |
alert_level |
in |
Sets the severity for the alert. Default value is ERROR. |
|
constant |
scope |
in |
string |
Describes the scope from which the log/alert originates. Default value is C_BFM_SCOPE (“GMII BFM”). |
constant |
msg_id_panel |
in |
t_msg_id_panel |
Controls verbosity within a specified scope. Default value is shared_msg_id_panel. |
constant |
config |
in |
Configuration of BFM behavior and restrictions. Default value is C_GMII_BFM_CONFIG_DEFAULT. |
-- Examples:
gmii_expect((x"01", x"02", x"03", x"04"), "Expect 4 bytes", gmii_rx_if);
gmii_expect(v_data_array(0 to v_num_bytes - 1), "Expect v_num_bytes bytes", gmii_rx_if, ERROR, C_SCOPE, shared_msg_id_panel, gmii_bfm_config);
init_gmii_if_signals()
Initializes the GMII interface. All the BFM outputs are set to ‘0’, and BFM inputs are set to ‘Z’.
t_gmii_rx_if := init_gmii_if_signals
t_gmii_tx_if := init_gmii_if_signals
-- Examples:
gmii_rx_if <= init_gmii_if_signals;
gmii_tx_if <= init_gmii_if_signals;
Local BFM overloads
A good approach for better readability and maintainability is to make simple, local overloads for the BFM procedures in the TB process. This allows calling the BFM procedures with the key parameters only, e.g.
gmii_write(v_data_array(0 to 1), "msg");
rather than
gmii_write(v_data_array(0 to 1), "msg", gmii_tx_if, C_SCOPE, shared_msg_id_panel, C_GMII_BFM_CONFIG_DEFAULT);
By defining the local overload as e.g.
procedure gmii_write(
constant data_array : in t_slv_array;
constant msg : in string) is
begin
gmii_write(data_array, -- Keep as is
msg, -- Keep as is
gmii_tx_if, -- Signal must be visible in local process scope
C_SCOPE, -- Use the default
shared_msg_id_panel, -- Use global, shared msg_id_panel
C_GMII_BFM_CONFIG_LOCAL); -- Use locally defined configuration or C_GMII_BFM_CONFIG_DEFAULT
end procedure;
Using a local overload like this also allows the following – if wanted:
Set up defaults for constants. May be different for two overloads of the same BFM
Apply dedicated message ID panel to allow dedicated verbosity control
Compilation
This BFM package may only be compiled with VHDL-2008 or newer. It is dependent on the Utility Library, which is only compatible with VHDL-2008 or newer.
After UVVM-Util has been compiled, the BFM package can be compiled into any desired library.
See Essential Mechanisms - Compile Scripts for information about compile scripts.
Simulator compatibility and setup
See Prerequisites for a list of supported simulators.
For required simulator setup see UVVM-Util Simulator compatibility and setup.
Additional Documentation
Important
This is a simplified Bus Functional Model (BFM) for GMII.
The given BFM complies with the basic GMII protocol and thus allows a normal access towards a GMII interface.
This BFM is not a GMII protocol checker.
For a more advanced BFM please contact UVVM support at info@uvvm.org
VVC
VVC functionality is implemented in gmii_vvc.vhd
For general information see VVC Framework - Essential Mechanisms.
Entity
Generics
Name |
Type |
Default |
Description |
---|---|---|---|
GC_INSTANCE_IDX |
natural |
N/A |
Instance number to assign the VVC |
GC_GMII_BFM_CONFIG |
C_GMII_BFM_CONFIG_DEFAULT |
Configuration for the GMII BFM |
|
GC_CMD_QUEUE_COUNT_MAX |
natural |
C_CMD_QUEUE_COUNT_MAX |
Absolute maximum number of commands in the VVC command queue |
GC_CMD_QUEUE_COUNT_THRESHOLD |
natural |
C_CMD_QUEUE_COUNT_THRESHOLD |
An alert will be generated when reaching this threshold to indicate that the command queue is almost full. The queue will still accept new commands until it reaches GC_CMD_QUEUE_COUNT_MAX. |
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY |
C_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY |
Alert severity which will be used when command queue reaches GC_CMD_QUEUE_COUNT_THRESHOLD |
|
GC_RESULT_QUEUE_COUNT_MAX |
natural |
C_RESULT_QUEUE_COUNT_MAX |
Maximum number of unfetched results before result_queue is full |
GC_RESULT_QUEUE_COUNT_THRESHOLD |
natural |
C_RESULT_QUEUE_COUNT_THRESHOLD |
An alert will be issued if result queue exceeds this count. Used for early warning if result queue is almost full. Will be ignored if set to 0. |
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY |
C_RESULT_QUEUE _COUNT_THRESHOLD_SEVERITY |
Severity of alert to be initiated if exceeding GC_RESULT_QUEUE_COUNT_THRESHOLD |
Signals
Object |
Name |
Dir. |
Type |
Description |
---|---|---|---|---|
signal |
gmii_vvc_tx_if |
inout |
GMII TX signal interface record |
|
signal |
gmii_vvc_rx_if |
inout |
GMII RX signal interface record |
Configuration Record
vvc_config accessible via shared_gmii_vvc_config
Record element |
Type |
Default |
Description |
---|---|---|---|
inter_bfm_delay |
C_GMII_INTER_BFM_DELAY_DEFAULT |
Delay between any requested BFM accesses towards the DUT. TIME_START2START: Time from a BFM start to the next BFM start (a TB_WARNING will be issued if access takes longer than TIME_START2START). TIME_FINISH2START: Time from a BFM end to the next BFM start. Any insert_delay() command will add to the above minimum delays, giving for instance the ability to skew the BFM starting time. |
|
cmd_queue_count_max |
natural |
C_CMD_QUEUE_COUNT_MAX |
Maximum pending number in command queue before queue is full. Adding additional commands will result in an ERROR. |
cmd_queue_count_threshold |
natural |
C_CMD_QUEUE_COUNT_THRESHOLD |
An alert will be issued if command queue exceeds this count. Used for early warning if command queue is almost full. Will be ignored if set to 0. |
cmd_queue_count_threshold_severity |
C_CMD_QUEUE_COUNT_THRESHOLD_SEERITY |
Severity of alert to be initiated if exceeding cmd_queue_count_threshold |
|
result_queue_count_max |
natural |
C_RESULT_QUEUE_COUNT_MAX |
Maximum number of unfetched results before result_queue is full |
result_queue_count_threshold |
natural |
C_RESULT_QUEUE_COUNT_THRESHOLD |
An alert will be issued if result queue exceeds this count. Used for early warning if result queue is almost full. Will be ignored if set to 0. |
result_queue_count_threshold_severity |
C_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY |
Severity of alert to be initiated if exceeding result_queue_count_threshold |
|
bfm_config |
C_GMII_BFM_CONFIG_DEFAULT |
Configuration for the GMII BFM |
|
msg_id_panel |
t_msg_id_panel |
C_VVC_MSG_ID_PANEL_DEFAULT |
VVC dedicated message ID panel. See Scope of Verbosity Control for how to use verbosity control. |
unwanted_activity_severity |
C_UNWANTED_ACTIVITY_SEVERITY |
Severity of alert to be issued if unwanted activity on the DUT outputs is detected. It is enabled with ERROR severity by default. |
Note
cmd/result queue parameters in the configuration record are unused and will be removed in v3.0, use instead the entity generic constants.
The configuration record can be accessed from the Central Testbench Sequencer through the shared variable array, e.g.
shared_gmii_vvc_config(RX, C_VVC_IDX).inter_bfm_delay.delay_in_time := 50 ns;
shared_gmii_vvc_config(TX, C_VVC_IDX).bfm_config.id_for_bfm := ID_BFM;
Status Record
vvc_status accessible via shared_gmii_vvc_status
The current status of the VVC can be retrieved during simulation. This is achieved by reading from the shared variable from the test sequencer. The record contents can be seen below:
Record element |
Type |
Description |
---|---|---|
current_cmd_idx |
natural |
Command index currently running |
previous_cmd_idx |
natural |
Previous command index to run |
pending_cmd_idx |
natural |
Pending number of commands in the command queue |
Methods
All VVC procedures are defined in vvc_methods_pkg.vhd (dedicated to this VVC).
See Common VVC Methods for procedures which are common to all VVCs.
It is also possible to send a multicast to all instances of a VVC with ALL_INSTANCES as parameter for vvc_instance_idx.
All parameters in brackets are optional.
For clarity, data_array is required to be ascending, e.g.
variable v_data_array : t_slv_array(0 to C_MAX_BYTES - 1)(7 downto 0);
gmii_write()
Adds a write command to the GMII VVC executor queue, which will run as soon as all preceding commands have completed. When the command is scheduled to run, the executor calls the BFM gmii_write() procedure. data_array(0) is written first, while data_array(data_array’high) is written last.
gmii_write(VVCT, vvc_instance_idx, channel, data_array, msg, [action_when_transfer_is_done], [scope])
Object |
Name |
Dir. |
Type |
Description |
---|---|---|---|---|
signal |
VVCT |
inout |
t_vvc_target_record |
VVC target type compiled into each VVC in order to differentiate between VVCs |
constant |
vvc_instance_idx |
in |
integer |
Instance number of the VVC |
constant |
channel |
in |
t_channel |
The VVC channel of the VVC instance |
constant |
data_array |
in |
t_slv_array |
An array of bytes containing the data to be written |
constant |
msg |
in |
string |
A custom message to be appended in the log/alert |
constant |
action_when_transfer_is_done |
in |
Whether to release or hold the TXEN line after the procedure is finished. Useful when transmitting a packet of data through several procedures, e.g. from Ethernet HVVC. Default value is RELEASE_LINE_AFTER_TRANSFER. |
|
constant |
scope |
in |
string |
Describes the scope from which the log/alert originates. Default value is C_VVC_CMD_SCOPE_DEFAULT. |
-- Examples:
gmii_write(GMII_VVCT, 0, TX, (x"01", x"02", x"03", x"04"), "Write 4 bytes");
gmii_write(GMII_VVCT, 0, TX, v_data_array(0 to v_num_bytes - 1), "Write v_num_bytes bytes", HOLD_LINE_AFTER_TRANSFER, C_SCOPE);
gmii_read()
Adds a read command to the GMII VVC executor queue, which will run as soon as all preceding commands have completed. When the command is scheduled to run, the executor calls the BFM gmii_read() procedure.
The value read from DUT will not be returned in this procedure call since it is non-blocking for the sequencer/caller, but the read data will be stored in the VVC for a potential future fetch (see example with fetch_result below). If the data_routing is set to TO_SB, the read data will be sent to the GMII VVC dedicated scoreboard where it will be checked against the expected value (provided by the testbench).
gmii_read(VVCT, vvc_instance_idx, channel, [num_bytes], [data_routing,] msg, [scope])
Object |
Name |
Dir. |
Type |
Description |
---|---|---|---|---|
signal |
VVCT |
inout |
t_vvc_target_record |
VVC target type compiled into each VVC in order to differentiate between VVCs |
constant |
vvc_instance_idx |
in |
integer |
Instance number of the VVC |
constant |
channel |
in |
t_channel |
The VVC channel of the VVC instance |
constant |
num_bytes |
in |
t_channel |
Number of bytes to be read |
constant |
data_routing |
in |
Selects the destination of the read data |
|
constant |
msg |
in |
string |
A custom message to be appended in the log/alert |
constant |
scope |
in |
string |
Describes the scope from which the log/alert originates. Default value is C_VVC_CMD_SCOPE_DEFAULT. |
-- Examples:
gmii_read(GMII_VVCT, 0, RX, "Read data and store it in the VVC");
gmii_read(GMII_VVCT, 0, RX, 10, "Read 10 bytes of data", C_SCOPE);
gmii_read(GMII_VVCT, 0, RX, TO_SB, "Read data and send to Scoreboard for checking");
-- Example with fetch_result() call: Result is placed in v_result
variable v_cmd_idx : natural; -- Command index for the last read
variable v_result : work.vvc_cmd_pkg.t_vvc_result; -- Result from read.
...
gmii_read(GMII_VVCT, 0, RX, "Read data in VVC");
v_cmd_idx := get_last_received_cmd_idx(GMII_VVCT, 0, RX);
await_completion(GMII_VVCT, 0, RX, v_cmd_idx, 1 us, "Wait for read to finish");
fetch_result(GMII_VVCT, 0, RX, v_cmd_idx, v_result, "Fetching result from read operation");
Hint
t_vvc_result is defined in the corresponding vvc_cmd_pkg.vhd for the VIP.
gmii_expect()
Adds an expect command to the GMII VVC executor queue, which will run as soon as all preceding commands have completed. When the command is scheduled to run, the executor calls the BFM gmii_expect() procedure. The gmii_expect() procedure will perform a read operation, then check if the read data is equal to the expected data in the data parameter. If the read data is not equal to the expected data parameter, an alert with severity ‘alert_level’ will be issued. The read data will not be stored in this procedure.
gmii_expect(VVCT, vvc_instance_idx, channel, data_exp, msg, [alert_level, [scope]])
Object |
Name |
Dir. |
Type |
Description |
---|---|---|---|---|
signal |
VVCT |
inout |
t_vvc_target_record |
VVC target type compiled into each VVC in order to differentiate between VVCs |
constant |
vvc_instance_idx |
in |
integer |
Instance number of the VVC |
constant |
channel |
in |
t_channel |
The VVC channel of the VVC instance |
constant |
data_exp |
in |
t_slv_array |
An array of bytes containing the data to be expected |
constant |
msg |
in |
string |
A custom message to be appended in the log/alert |
constant |
alert_level |
in |
Sets the severity for the alert. Default value is ERROR. |
|
constant |
scope |
in |
string |
Describes the scope from which the log/alert originates. Default value is C_VVC_CMD_SCOPE_DEFAULT. |
-- Examples:
gmii_expect(GMII_VVCT, 0, RX, (x"01", x"02", x"03", x"04"), "Expect 4 bytes from DUT");
gmii_expect(GMII_VVCT, 0, RX, v_data_array(0 to v_num_bytes - 1), "Expect v_num_bytes from DUT", ERROR, C_SCOPE);
Activity Watchdog
The VVCs support a centralized VVC activity register which the activity watchdog uses to monitor the VVC activities. The VVCs will register their presence to the VVC activity register at start-up, and report when ACTIVE and INACTIVE, using dedicated VVC activity register methods, and trigger the global_trigger_vvc_activity_register signal during simulations. The activity watchdog is continuously monitoring the VVC activity register for VVC inactivity and raises an alert if no VVC activity is registered within the specified timeout period.
Include activity_watchdog(num_exp_vvc, timeout, [alert_level, [msg]])
in the testbench to start using the activity watchdog.
Note that setting the exact number of expected VVCs in the VVC activity register can be omitted by setting num_exp_vvc = 0.
More information can be found in Essential Mechanisms - Activity Watchdog.
Transaction Info
This VVC supports transaction info, a UVVM concept for distributing transaction information in a controlled manner within the complete testbench environment. The transaction info may be used in many different ways, but the main purpose is to share information directly from the VVC to a DUT model.
Info field |
Type |
Default |
Description |
---|---|---|---|
operation |
t_operation |
NO_OPERATION |
Current VVC operation, e.g. INSERT_DELAY, POLL_UNTIL, READ, WRITE |
data_array |
t_slv_array(0 to 2047)(7 downto 0) |
0x0 |
Data for GMII read or write transaction |
vvc_meta |
t_vvc_meta |
C_VVC_META_DEFAULT |
VVC meta data of the executing VVC command |
-> msg |
string |
“” |
Message of executing VVC command |
-> cmd_idx |
integer |
-1 |
Command index of executing VVC command |
transaction_status |
t_transaction_status |
INACTIVE |
Set to INACTIVE, IN_PROGRESS, FAILED or SUCCEEDED during a transaction |
More information can be found in Essential Mechanisms - Distribution of Transaction Info.
Scoreboard
This VVC has built in Scoreboard functionality where data can be routed by setting the TO_SB parameter in supported method calls, i.e. gmii_read(). Note that the data is only stored in the scoreboard and not accessible with the fetch_result() method when the TO_SB parameter is applied. The GMII scoreboard is accessible from the testbench as a shared variable GMII_VVC_SB, located in the vvc_methods_pkg.vhd, e.g.
GMII_VVC_SB.add_expected(C_GMII_VVC_IDX, v_expected, "Adding expected");
See the Bitvis VIP Scoreboard for a complete list of available commands and additional information. All of the listed Generic Scoreboard commands are available for the GMII VVC scoreboard using the GMII_VVC_SB.
Unwanted Activity Detection
This VVC supports detection of unwanted activity from the DUT. This mechanism will give an alert if the DUT generates any unexpected bus activity. It assures that no data is output from the DUT when it is not expected, i.e. read/receive/check/expect VVC methods are not called. Once the VVC is inactive, it starts to monitor continuously on the DUT outputs. When unwanted activity is detected, the VVC issues an alert.
The unwanted activity detection can be configured from the central testbench sequencer, where the severity of alert can be changed to a different value. To disable this feature in the testbench, e.g.
shared_gmii_vvc_config(RX, C_VVC_INDEX).unwanted_activity_severity := NO_ALERT;
The unwanted activity detection is ignored when the rxdv signal goes low within one clock period after the VVC becomes inactive. This is to handle the situation when the read command exits before the next rising edge, causing signal transitions during the first clock cycle after the VVC is inactive.
For GMII VVC, the unwanted activity detection is enabled by default with severity ERROR.
Note
This feature is only implemented on gmii_rx_vvc.
More information can be found in Essential Mechanisms - Unwanted Activity Detection.
Compilation
The GMII VVC must be compiled with VHDL-2008 or newer. It is dependent on the following libraries:
UVVM Utility Library (UVVM-Util)
UVVM VVC Framework
Bitvis VIP Scoreboard
GMII BFM
Before compiling the GMII VVC, assure that uvvm_util, uvvm_vvc_framework and bitvis_vip_scoreboard have been compiled.
See Essential Mechanisms - Compile Scripts for information about compile scripts.
Compile to library |
File |
Comment |
---|---|---|
bitvis_vip_gmii |
gmii_bfm_pkg.vhd |
GMII BFM |
bitvis_vip_gmii |
transaction_pkg.vhd |
GMII transaction package with DTT types, constants, etc. |
bitvis_vip_gmii |
vvc_cmd_pkg.vhd |
GMII VVC command types and operations |
bitvis_vip_gmii |
../uvvm_vvc_framework/src_target_dependent/td_target_support_pkg.vhd |
UVVM VVC target support package, compiled into this VVC library |
bitvis_vip_gmii |
../uvvm_vvc_framework/src_target_dependent/td_vvc_framework_common_methods_pkg.vhd |
Common UVVM framework methods compiled into the this VVC library |
bitvis_vip_gmii |
vvc_sb_pkg.vhd |
GMII VVC scoreboard |
bitvis_vip_gmii |
vvc_methods_pkg.vhd |
GMII VVC methods |
bitvis_vip_gmii |
../uvvm_vvc_framework/src_target_dependent/td_queue_pkg.vhd |
UVVM queue package for this VVC |
bitvis_vip_gmii |
../uvvm_vvc_framework/src_target_dependent/td_vvc_entity_support_pkg.vhd |
UVVM VVC entity support compiled into this VVC library |
bitvis_vip_gmii |
gmii_tx_vvc.vhd |
GMII TX VVC |
bitvis_vip_gmii |
gmii_rx_vvc.vhd |
GMII RX VVC |
bitvis_vip_gmii |
gmii_vvc.vhd |
GMII VVC wrapper for the TX and RX VVCs |
bitvis_vip_gmii |
vvc_context.vhd |
GMII VVC context file |
Simulator compatibility and setup
See Prerequisites for a list of supported simulators.
For required simulator setup see UVVM-Util Simulator compatibility and setup.
Additional Documentation
Important
This is a simplified Verification IP (VIP) for GMII.
The given VIP complies with the basic GMII protocol and thus allows a normal access towards a GMII interface.
This VIP is not a GMII protocol checker.
For a more advanced VIP please contact UVVM support at info@uvvm.org
Note
Disclaimer: This IP and any part thereof are provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with this IP.