![]() ![]() This information will be passed down to the jelly-bean functional coverage subscriber, referred to as the jelly_bean_fc_subscriber. The driver passes the jelly beans through the jelly-bean interface ( jelly_bean_if) to the jelly_bean_taster, which will check the jelly-bean taste.Ĭoncurrently, as the jelly beans are being created, the jelly_bean_monitor will capture the flavor and color of the recently produced. From the information provided in the recipe, the driver creates jelly beans. The jelly_bean_sequencer will create jelly-bean recipes and send them to the jelly_bean_driver. The jelly_bean_taster is the design-under-test (DUT) module. The left figure shows the relationship of the verification components. ![]() The verification components used in the process will be described below. This does not require the knowledge of any system bus. The test bench will generate many jelly-bean flavors in a constrained random manner and the system will evaluate palatable flavors. Rather than focusing on AXI, OCP, or other system buses in existence, this tutorial will be based on the hypothetical example of a jelly-bean generator. This post will provide a simple tutorial on this new verification methodology. Accellera’s recently released UVM may change the future of verification, as verification methodology seems to be consolidated in this UVM. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |