sas73 Posted July 31, 2019 Report Share Posted July 31, 2019 When a testbench hangs such that the UVM timeout is triggered I get a message like this reporter [PH_TIMEOUT] Explicit timeout of 10 hit, indicating a probable testbench issue Are there ways in which UVM can help me identify the cause of this timeout? For example, special wait statements that would notify me if they are blocking when the timeout hits. Quote Link to comment Share on other sites More sharing options...
Taichi Ishitani Posted August 1, 2019 Report Share Posted August 1, 2019 How about printing objection information? For example, list of components locking objection. Regards, Taichi Ishitani Quote Link to comment Share on other sites More sharing options...
hbhbts Posted August 1, 2019 Report Share Posted August 1, 2019 you can enable UVM_PHASE_TRACE, this debug message can print phases and objections information. Quote Link to comment Share on other sites More sharing options...
sas73 Posted August 1, 2019 Author Report Share Posted August 1, 2019 @Taichi Ishitani That would certainly narrow the scope a bit but I would hoping for something that would pinpoint the wait statement. Is there a instrumentation mechanism in place? That would require me to add code manually but it would also be useful for other scenarios, for example to locate a loop that is stuck. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.