Documente Academic
Documente Profesional
Documente Cultură
6534-6541
© Research India Publications. http://www.ripublication.com
Murali .M.
M.Tech (VLSI Design), School of Electronics Engineering (SENSE),VIT University Chennai Campus, Chennai, India.
Umadevi. S
Assistant Professor (Sr.G), School of Electronics Engineering (SENSE), VIT University Chennai Campus, Chennai, India.
Orcid Id: 0000-0001-7742-9209
Sakthivel.S.M.
Assistant Professor (Sr.G), School of Electronics Engineering (SENSE),VIT University Chennai Campus, Chennai, India.
Orcid Id: 0000-0002-8486-3238
6534
International Journal of Applied Engineering Research ISSN 0973-4562 Volume 12, Number 17 (2017) pp. 6534-6541
© Research India Publications. http://www.ripublication.com
bridges, large memory access and high backward Read Transaction Phase
compatibility with peripherals. Also the AXI bus architecture
In the read transaction phase, the read address (AR) and read
is having separate read and write data phases with individual
data response(R) signals are involved in the data
data channels, unaligned data transactions and burst mode
communication and synchronization process. In the read
access. This section explains the bus architecture of AXI
transaction the first the valid address (AR)and Read channel
protocol used for the data communication and synchronization
access is communicated by master to initialize the transactions
operations. In this bus architecture the data transactions are
and then the slave responds with a signal AR ready(i.e making
established in two phases as i) Read Transaction phase and ii)
the address ready for the communication). After the reception
Write Transaction phase in the bus. The corresponding phases
of AR ready the master checks the address and then receives
of operation are explained in the subsections with the master –
the RVALID and read channel data signals. Following to that
slave configurations.
the master establishes the channel communication with
control signal with a valid RR ready and establishes the read
transactions. The entire architecture/operation of the read
transaction is pictorially represented in the fig.1.
6535
International Journal of Applied Engineering Research ISSN 0973-4562 Volume 12, Number 17 (2017) pp. 6534-6541
© Research India Publications. http://www.ripublication.com
Write Transaction Phase constrained random mode. The test-case is of the form
constrained random mode or direct random test-case. The test
The write transactions are happening in the following three
is regressively performed on the design and analyzed. It
modes as i)Write address channel, ii)Write data channel and
normally contains set of stimulus for running the design.
iii)Write response channel. In the write address channel mode,
the master starts the communication with the control signals Virtual Sequencer
AW VALID and Write channel access/address to the slave(i.e
Generally the sequencer generates random sequences for
it sends the valid address and channel control and address).
verifying the key properties of the design. The generated
Immediately the slave responds with a valid AW ready. In the
sequence is called as top level sequence and splitted into
same manner during the Write data channel mode, the master
corresponding level base and primitive sequences. Thus the
initializes the transactions with a WVLAID and Write channel
virtual sequencer verifies the functionality of each sub-
data, following to that the slave acknowledges by a valid
component by driving/forcing them with the set of sequences.
WREADY signal. Similar to the data and address mode, the
Write response channel mode involves the transaction started Sequencer
by master with the control signals BVALID and write
Sequencer is a component, which generates set of sequences.
response channel. Upon receiving the control signal, the slave
The generated sequences are of two types active and passive.
establishes the communication by a valid BREADY signal.
The active sequence drives the signal whereas the passive
The operation of the write transactions are shown in the fig.2
does not drive the signal. The sequencer aligns and generates
the sequence accordingly to the criteria of functionality
checks.
PROPOSED VERIFICATION ENVIRONMENT
Driver
The verification environment is a standard method of
verifying the DUV in code coverage mode. The following Driver is the component which interfaces or forces all other
components are present in the proposed verification components to respond accordingly to the feeded stimulus (i.e
environment i) Test-suite, ii) Virtual sequencer, iii) simply it drives the input to the corresponding blocks).
Sequencer, iv) Driver, v) AXI-Monitor, vi) Protocol checker,
Monitor
vii) Bus Monitor, viii) Coverage Collector and xi)Scoreboard.
The monitor watches all the data transactions of the all the
components and reports the result to the coverage collector. It
has a TLM port for analysis and virtual interface to handle the
points of the DUV signals.
Protocol checker
In this module, the DUV functionality is verified, the interface
compliance is also checked with the temporal behavior of the
inputs. Also the responses are monitored for all the
combinations of the input sequences.
Bus monitor
Bus monitor screens the functional operation of individual
components and connects the master/slave monitor. Finally
the transactions are collected in the coverage collector as
database.
Coverage Collector
Coverage collector collects all the code coverage information
like branch, statement and FSM in the DUV is covered by the
specified test-case or not. Normally the verification engineers
aim for 100% of coverage during the functional verification.
Figure - 3 Verification Environment
6536
International Journal of Applied Engineering Research ISSN 0973-4562 Volume 12, Number 17 (2017) pp. 6534-6541
© Research India Publications. http://www.ripublication.com
given as follows Then during the routing stage the bus data occupancy
structure is verified by the bus utilization and efficiency.
Finally the data integrity is noted for every transactions and
module top; the functionality check pass is carried out for each of the
stage.
reg clk, rst;
In this AXI protocol, the verifications plan focuses the
axi_intf vif(clk, rst);
coverage of the following scenarios as
axi_slave dut(
Read phase
clk,
Write Phase
rst,
Write & Read Phase from same address
vif.awid,
Write & Read Phase from different address
vif.awaddr,
Overlapped transactions
.......
For the corresponding scenarios the test-cases are generated
....... and the simulation is carried out for the functionality
verification. Using the following bus performance metrics
);
Valid Count, Busy Count and Bus Utilization factor, the
axi_tb tb(); performance of the bus is assessed. If the bus is not verified
axi_assertion axi_assert(); accurately in the corresponding test-cases, then the test-cases
are modified accordingly to reach the specific property
....... checks.
....... Also in the verification, the code coverage based verification
....... mode analysis is carried out for the DUV; if the 100%
coverage is not achieved during the analysis the test-case is
initial begin altered to cover all the code parts of the design.
$value$plusargs("test_no=%d",
axi_config::test_no);
RESULTS & DISCUSSIONS
->axi_config::e;
This section discusses the simulation results of the AMBA
end AXI protocol for the five different test-scenarios and the
endmodule performance assessment using the quality metrics for the data
metrics. For carrying out the simulation analysis, fist the
individual modules AXI Master/Slave is modeled using
In the same manner the AXI Master/Slave and the individual System Verilog and integrated with the modeled test-
components of the verification environment are modeled environment for the verification. In the verification
using System Verilog. The instances of the AXI top module environment, the DUV is integrated with sequencer, interface,
pseudo-code is given partially as above. The above prescribed driver and monitor to assess the performance in constrained
Verification Environment is used for the functional mode. After the integration of the top module with DUV the
verification of the AMBA Bus protocol. simulation is carried out using the Mentor Graphics
QuestaSim®. Here the test-case is written for five different
scenarios as i) Read phase, ii) Write phase, iii) Read & Write
Verification Plan from the same address, iv) Read & Write from the different
address and finally v)Overlapped Transactions.
The verification plan tells the property has to be verified and
drives the coverage criteria to be satisfied. A good plan Verification of Read Phase
contains measurable metrics and successful test-case to In this phase the read data transactions of the AMBA AXI
achieve the coverage and functionality check. The plan of protocol is verified with the Master/Slave configuration mode.
verification tells what to be verified, how to verify it. In this During the ready cycle transactions the signals ARVALID,
AMBA AXI verification the properties to be verified are ARREADY, RVALID, RREADY, RLAST, RDATA and
i)System connectivity during read and write cycle, ARSIZE are monitored and verified. Here the functionality
ii)Transaction routing and iii)finally the Data integrity. In the check primarily involves two modes of operation namely i)
system connectivity checking test, the system integration is Read Address and ii) Read Response channel. For the every
monitored by the corresponding acknowledgement signals. positive edge of clock, the read address channel will fetch the
6537
International Journal of Applied Engineering Research ISSN 0973-4562 Volume 12, Number 17 (2017) pp. 6534-6541
© Research India Publications. http://www.ripublication.com
address at the high state values of ARVALID and The Write Transactions is pictorially represented in the fig.5.
ARREADY. Similarly after a time delay, the response will be
instantiated to high mode with the high values of the signal on
RVALID and RREADY. The last transaction of the read
operation is indicated by the high values of RLAST. The
values of ARSIZE and ARLEN are measured and indicate the
number of transactions occurred in read mode. For verifying
the read phase a test-case is generated and simulated to test
the functionality of the read operation. The working of the
read mode includes two channels as explained above with the
measure of the quality metrics for the read address, read
channel data with channel response. The entire operation of
the read phase is pictorially represented as a waveform in the
fig.4
6538
International Journal of Applied Engineering Research ISSN 0973-4562 Volume 12, Number 17 (2017) pp. 6534-6541
© Research India Publications. http://www.ripublication.com
Overlapped Transactions
In the overlapped transactions both the read and write will
happen the using the shared address in burst mode. Here the
AXI protocol is operating in the burst mode of read and write.
The burst modes of the overlapped read and write operations
for the AXI Bus protocol is shown in the fig7. From the
simulation waveform it is inferred that the overlapped
transaction is also supported by the AXI bus.
6539
International Journal of Applied Engineering Research ISSN 0973-4562 Volume 12, Number 17 (2017) pp. 6534-6541
© Research India Publications. http://www.ripublication.com
6540
International Journal of Applied Engineering Research ISSN 0973-4562 Volume 12, Number 17 (2017) pp. 6534-6541
© Research India Publications. http://www.ripublication.com
6541