Jump to content

uvm_mem backdoor access

Recommended Posts


I'm now building a uvm_mem model and try the frontdoor access with burst_write and burst_read,

all works fine.

And I tried to test the backdoor access with peek/poke,

after searching for some information, it seems to have uvm_reg_backdoor extension set to uvm_mem first, then I need to implement the virtual task/func "write" and "read_func" in child class

of uvm_reg_backdoor.

I confused that how to implement those two overloaded "write" and "read_func" ?

Seems that should directly write to and read from uvm_mem object, but should they still use

frontdoor access "read/write" APIs of uvm_mem or the backdoor way (still peek or poke) ?

I ever tried the frontdoor access but it then call to "reg2bus" again,

and the simulation is hanged in backdoor way.

Can anyone give me some hints or examples ?

Thanks in advance !

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...