Verification methodologies have evolved over the years from a simple HDL task-based methodology to a complete verification automation system. With designs today reaching a few million gates, verification automation systems are now required to maximize productivity of the verification process. “e” provides dynamic inheritance that allows the environment to be built in an object oriented manner. e has constructs for constraint-driven generation, temporal language, and functional coverage. These constructs help the engineer quickly build various components in the environment. e automates the generation of stimuli.
e allows the drivers in a verification environment to be created in an object oriented manner. This allows maximum reusability.
Interface with the simulator (Verilog, HDL simulator).Coordinate all procedural code that drives the DUT. Conform to input protocol for DUT. Convert abstract data structures into a list of bits. Drive the bits onto the DUT.
Wireless USB Verification methodology using Spec man, provides various test scenarios in verifying the functionalities of DUT as well as the WUSB protocol, ECMA 369 standards, AES-128 Standard protocols.
A verification plan is required to describe what is to be verified and how it will be verified. It should address the three aspects of verification: coverage measurement, stimulus generation, and response checking. The verification environment will be developed in e.
Data Object (Stimulus Generation)
The generation component of verification uses data objects for stimulus generation. These data objects are structs that represent the abstract form of input stimulus. This struct is the basic form of stimulus.
Driver Object (Stimulus Driver)
The driver object performs the function of taking the stimulus data objects one at a time and applying them to the DUT until all stimuli has been applied. Typically, the driver object is similar to an HDL bus functional model.
Receiver Object (Output Receiver)
The receiver object is responsible for collecting the data at output of the DUT. The receiver object performs the function of taking the raw output data from the DUT based on the output protocol and converting the data to an abstract object for comparison. Typically, the receiver object is similar to an HDL bus functional model.
Data Checker Object (Expected Value Comparison)
The data_checker object stores expected values for each input data object injected into the DUT. When the receiver object receives one data object, it passes it to the data_checker for comparison against the expected values.
Monitor Object (Protocol Checker)
Coverage Object (DUT and e Coverage)
WUSB Device Controller Verification Test Plan:
Wireless USB Verification Goals
Implemented Verification Methodology
GeneratorGenerator wusb_device_gen.e comprises following structs for the following:
All struct members are the WUSB spec derivatives and are virtual in nature. Also comprises of various MMC scenarios, data payloads.
Existing Wireless USB verification environment using Spec man provides the test engineer fullest possibility in verifying the WUSB end device functionalities, WUSB protocol rules, ECMA 369 and AES 128 standards, device enumeration process comprising four way handshaking, device authentication, Data transfers like (Control, Bulk OUT, Bulk IN). Also ramping advancements will occur there after in the entire environment for highly automated system giving the user or the test engineer to verify the look and corner test cases.
|If you have any suggestion/feedback please email it to firstname.lastname@example.org|