• 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. nccovdut option : Can it have more than 1 option?

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 65
  • Views 14183
  • 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

nccovdut option : Can it have more than 1 option?

Pooja
Pooja over 16 years ago

Hi,

      I use ncverilog and the DUT for which am working on currently has a seperate Tx top and a seperate Rx top,

and it  does not have a common top level or rather the design team wants to keep the Tx and Rx seperate.Now I

want code coverage for Tx as well as Rx,is it possible to have 2 arguments to the nccovdut switch? Meaning

can we have +nccovdut+xyz_tx_top+xyz_rx_top in the makefile? Please let me know your thoughts as to how can  i

get code coverage of Rx and Tx wherein I have them as seperate modules and also don have the luxury to put

them together in a top level design file?

  • Cancel
Parents
  • Pooja
    Pooja over 16 years ago

    Hi Mickey ,

           Thanks a lot for the valuable inputs that you give me time and again,I must confess it helps me a lot!!!!!!!

                My aim is to get the coverage for TX and Rx modules and if I used a * option to generate the report it gives me the coverage of nested modules which makes it difficult to discern the actual coverage of TX and RX so I agree with you and hence now I generate the coverage report using report_html tx rx > output.html ,It certainly gives a better idea.Also could you give me a pointer to a document which would help me analyze my code coverage? I want to understand the coverage report so that I can fill up the holes.

    Thanks,

    Pooja

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Pooja
    Pooja over 16 years ago

    Hi Mickey ,

           Thanks a lot for the valuable inputs that you give me time and again,I must confess it helps me a lot!!!!!!!

                My aim is to get the coverage for TX and Rx modules and if I used a * option to generate the report it gives me the coverage of nested modules which makes it difficult to discern the actual coverage of TX and RX so I agree with you and hence now I generate the coverage report using report_html tx rx > output.html ,It certainly gives a better idea.Also could you give me a pointer to a document which would help me analyze my code coverage? I want to understand the coverage report so that I can fill up the holes.

    Thanks,

    Pooja

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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