Jump to content

burst_read() (uvm_mem) doesn't actually burst

Recommended Posts

The documentation is very unclear how to specify the length of a burst read.

The UVM Cookbook from Mentor Graphics implies that the size of the value[] array indicates the length of the read.

However, the argument isn't ref so this information is lost; as well, the actual implementation of burst_read() creates a uvm_reg_item object and doesn't initialize the rw.value item so it stays at a size of 1.

I'm fairly new to the land of UVM (I'm coming from Vera) - how does one raise this up the chain and get this fixed in the standard implementation?



Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...