Thursday, April 30, 2009
VMM Planner
Friday, March 20, 2009
Coverage convergence technology (CCT)
The automatically generated functional coverage code can be used as the starting point for writing the functional coverage model and can be integrated with the DV enviroment. CCT also allows parallel test runs with each test run targetting different coverage points without having any overlap between them. parallel test runs without overlapping random values is achived by providing the tool with a bias file which is generated by the tool based on the functional coverage data base.
Sunday, March 1, 2009
Streaming operators --- System verilog
Following is an example on the usage of Streaming operators
byte stream[$]; // byte stream
class Packet
rand int header;
rand int len;
rand byte payload[];
int crc;
constraint G { len > 1; payload.size == len ; }
function void post_randomize; crc = payload.sum; endfunction
endclass
...
send: begin // Create random packer and transmit
byte q[$];
Packet p = new;
void’(p.randomize());
q = {<< byte{p.header, p.len, p.payload, p.crc}}; // pack
stream = {stream, q}; // append to stream
end
...
receive: begin // Receive packet, unpack, and remove
byte q[$];
Packet p = new;
{<< byte{ p.header, p.len, p.payload with [0 +: p.len], p.crc }} = stream;
stream = stream[ $bits(p) / 8 : $ ]; // remove packet
end
Thursday, February 19, 2009
Automated coverage closure
Sunday, February 15, 2009
Randomization of scalar variables -- System Verilog
System verilog has an option of randomizing scalar variables out side a class with constraints.
Example
integer a,b,c;
void'( std::randomize(a,b,c) with { a==b;b>0;c==10; } );
The above construct generates random values for a,b,c the constraint is provided in line. The variables a,b,c are out side the class scope.
Saturday, February 14, 2009
Coverage grading
Coverage grading is an option used to rank the test cases based on the number of functional coverage points hit by the individual test case. Grading option can be used to analyze and remove redundant test cases which is targeting the same functionality. This will help to optimize the regression run and save simulation time.
In random test run scenario it also helps in identifying the random seeds which provides maximum coverage.It will be a good idea to go for functional coverage grading when the verification environment and test cases are frozen and suitable functional coverage numbers are achieved. if your test bench is constantly in development and changing ,using the same seed that gave you good coverage before may not do so again since the randomization may have been affected by the changes in the source code.
Command to generate functional coverage grading in VCS is
urg -dir ( *.vdb )
Sunday, February 8, 2009
functional coverage
Adding functional coverage to a verification environment involves three steps.
( directly maps to your test plan )
2. Implementing the functional coverage monitors.
3. Running simulation to collect the functional coverage and functional coverage analysis.
Methodology of identifying functional coverage points and cross coverage points can be explained with a simple USB2.0 Bulk transfer example.

12 diffrent axis have been identified for a simple USB 2.0 bulk transfer. Total no of basic coverage points for this functional coverage group is 34 coverage points. Now we need to get the cross coverage points. So what is a cross coverage point ? Cross coverage is the valid combinations of the identified axis for example one cross coverage point can be
HS(speed) --> IN(direction) -->ACK(response) -->SMALL(length) --> No (data toggle error)
--> No (crc error) -->No ( pid error) --> SMALL (No of tokens per uframe)
--> No ( token error) --> ODD (payload) --> OFF (ping token)
We need to identify all the cross coverage points for this functional coverage group. Each of the cross coverage point is an test scenario. The way to find all the cross coverage point is to simply cross all the axis which will give you all the possible combinations, now eliminate the invalid combinations. Eliminating the invalid cross can be done using ignore construct or bad state construct in VERA/NTB.
example :: finding the cross coverage points for Axis1 and Axis2 alone. ( In the actual scenario all the axis should be taken in to account). possible cross coverage points
HS --> IN, HS -->OUT , FS --> IN , FS-->OUT
4 cross coverage points have been identifyed by crossing Axis 1 and Axis 2.
Now the identified functional coverage / cross coverage points need to be implemented in VERA/NTB/SV as a coverage group and integrated to the verification environment.
