Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 16629
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Stept through UVM code

Tudor Timi

Hi,

I'm trying to step through the SV UVM library code, but I just can't manage. I tried the built in library in IUS and also a version downloaded from Accelera. Both setups have -linedebug on the command line. When trying with the built in one, it says it was not instrumented for line debugging. The Accellera one lets me put breakpoints, the simulator stops there, but it doesn't show the execution point in the source browser (it just mentions in the console that it stopped at the specific line).

Is there something I'm missing?

Thanks and best regards,

Tudor 

  • Hi Tudor, try with the -uvmlinedebug option of irun: " -uvmlinedebug Enable single-stepping through UVM functions and tasks. By default, -uvm -linedebug does not apply the -linedebug option to the compilation of the UVM package. This means that when you are debugging your code, single-stepping through the UVM content is not enabled. Include the -uvmlinedebug option if you want to single-step through the UVM content to debug UVM code. This option forces the UVM package, and all other HDL files specified on the command line, to be compiled with line debug capabilities. " Regards, -hannes
  • Thanks a lot for the quick answer! It works to set breakpoints in the built in UVM code, but it's still not showing me the execution point.
  • The execution may be in a different scope. Are you using -linedebug as well? In general if everything is traced and you are stopped, you can click on the yellow arrow in the debugger to get to the current execution point. -hannes

  • Hi again, It seems like it was a scope issue. It works now. Thanks a lot for the help!

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.