Jump to content


  • Content Count

  • Joined

  • Last visited

  1. There is a new API to turn off recording in the base sequence from the driver: is_auto_item_recording_enabled(). But it is only applied at the item level. The sequence itself is still recorded (in the start() task) regardless this switch. Should this switch be applied there as well? Also it seems to me recording a sequence is not quite useful. There is not much information contained in the sequence except it establishes a linkage with the sequence items. I have encountered an issue with the way sequence recording done currently: once the body() task exit, the "recorder" for the sequence is gone. But if driver (pipelined driver) want to recording the original sequence item UVM will generate runtime error. The workaround from me is to implement some kind of mechanism to flush the driver (in my case, driver is DMA engine, and wait all completions comeback).