In SystemVerilog verification, the postponed region executes after the active region where all variables have their final values, and it handles special commands like $strobe and $monitor for printing variable information to the simulation log, while functional coverage can be collected from this region if explicitly configured using the strobe option; $display and $write are evaluated in the active region for immediate values, whereas $strobe and $monitor are evaluated in the postponed region for final values, and $monitor provides continuous monitoring that only triggers when its arguments change.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
Course : Systemverilog Verification 6 : L7.1 : Postponed Region
Added:postponed region so we have already seen that while coming into postponed region uh all the variables will have their final value in in the current time slot and there are no feedback from the postponed region once you've read the postpone region so in the postponed region there are a few set of events will happen one thing is it will execute the dollar strobe and volume monitor command so these are special commands used to print the variable information into into a simulation log and these two dollar stop and roller monitor will be executed in the postponed region and also the functional coverage will be collected in the past one region if it is using in the stop sampling option so by default it will not be there in this it will not be collected in the password region but if you are explicitly wanted to specify the functional cover items to be collected from the firstborn region you can set coverage option in the functional coverage while specifying the coverage while writing the coverage uh saying that typed option dot strobe is equal to one and in that case the functional coverage will be collected in from the postponed region so these are the functionality that is happening in the postponed region now uh before winding up this session we will quickly see what all are the display commands in systematic you know their dollar display dollar right total strobe and holder monitor and uh you've already seen that dollar display and dollar right will be executed or evaluated in the active region um in this region set and dollar stroke and dollar monitor will be evaluated in the final possible region so if you're interested in the immediate value of a variable update you can use a dollar display a dollar right function and if you wanted the updated value or the last value in the times current times load then it will be uh useful to use the dollar stop or dollar monitor uh functions and all of them will use the same string formatting options like percentages personality uh all those kind of things which is similar to c programming i'm not discussing uh that details this formatting options here in detail here but we'll quickly see what is functionality of how a dollar strawberry dollar monitor can be used so a dollar stop is exactly equal to the functionality of the dollar display the only difference is that it will be um evaluated in the postponed region so you will be getting the values printed with all this final value in the current times load and it is useful to use this dollar stop function to display the simulation data of a selected time at the end of the current simulation time and and finally the dollar monitor function it is used for continuous monitoring so this is somewhat special about um the the way in which this is working the if you use a develop monitor function so it will not be displayed at every time unit so it will be displayed only when there is a change is happening to any of its argument so for example if you are writing like dollar monitor then some formatting specification this is how you want to print the debug information and after that you specify a few arguments here so first one is a time argument next are a b and c so this dollar if even if you are writing dollar time within the dollar monitor uh the time will not be explicitly monitored because you know uh time will be getting changed in every time unit but apart from the dollar time functions any if there are any variables that is listed in as argument of a dollar monitor function whenever a change is happening to these variables then this this whole function will be called and evaluated so this will be implicitly called by the simulator you don't need to call you don't need to worry about when these values are getting changed so this is useful for continuous monitoring of a variable or or a bus and also its behavior can be controlled by using some implicit functions like some system functions like roller monitor on and roller monitor off in the code appropriately and to summarize dollar display and dollar right will be evaluated in the active region set and dollar strobe and roller monitor will be evaluated in the postponed region and dollar monitor is useful for continuous monitoring
Related Videos
LBF101 Creating an XML Changelog
liquibase7511
3K views•2026-06-15
Alta Labs Cloud Dashboard Real time Network & Xnet Insights!
ShinyTechThings
158 views•2026-06-17
Wait... Group Policy Not Applying? Check This First!
keeplearning_iT
144 views•2026-06-15
Leetcode Weekly Contest 506 | Life's boring these days
Pudeesht
2K views•2026-06-14
microJAM: MAKING A MICRO GAME FOR A GAME JAM IN CLOJURESCRIPT AND TOTALLY NOT C
janetacarr
156 views•2026-06-18
Partitioning vs Bucketing vs Clustering: How to Make Queries 100x Faster
thedataandaiguy
194 views•2026-06-16
Design Claude Code Like a Senior Engineer
hayk.simonyan
344 views•2026-06-19
Linus Torvalds: AI Won’t Replace Understanding Code
SavvyNik
140 views•2026-06-19











