• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. need help in $dumpvar function :

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 14057
  • 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

need help in $dumpvar function :

archive
archive over 17 years ago

Hello Guys, i'm like to record bus data[31:0] into VCD file. therefore i use the following code: initial begin $dumpvar(0,top.dut.data); end end however , in the VCD file it prints the bus in seperate bits. like this : (verilog.dump file) $var a 1 data[31] $end $var b 1 data[30] $end $var c 1 data[29] $end ... instead of what i expect: $var 32 a data[31:0] $end can anybody tell me how do i refer to data[31:0] as a merged bus and not seperate bits ? thanks ,


Originally posted in cdnusers.org by zcabeli11
  • Cancel
  • archive
    archive over 17 years ago

    Using the vector notation is the default for the VCD file output. Ordinarily you have to work to get the output in individual bits. You can get the individual bits by declaring the wire as "scalared" or by using the "-expand" option with ncelab. Do either of these apply to your situation?


    Originally posted in cdnusers.org by TAM
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    i really want to get the output as vector. however, for some reason i get it seperated ... is there any way to force output as vector ?


    Originally posted in cdnusers.org by zcabeli11
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information