Transaction-Level interface

上一篇 / 下一篇 2006-07-18 13:24:18 / 天气: 晴朗 / 心情: 高兴 / 个人分类：Writing Testbenches

Autonomous Monitors

Decouple the monitoring of the physical interface signals from the retrieval of the output data.

Transaction-Level interface

The purpose of bus-functional models is to remove the testbench from the repetitive physical-level details. The bus-functional model lets the testbench concentrate on the data to be supplied, on the data that was produced and how it is supposed to have been transformed.
One procedure per transaction. Consider the balance between abstraction and controllablitity.
Write documentation for the bus-functional model.The documentation will have to describe the functinality and ineraction of each element, often highlighting inconsistencies or difficulties that were not considered when coding the interface.
Implementation. Find inconsistencies in the bus-functional model specification. Update the transaction interface and the documentation as required.

Variable-Length Transactions

In VHDL or Verilog, use the list emulation techniques for input data.
For the output data, the only remaining possibility is using an access to an uncontrained array type.