• 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. Differences b/w logic , reg & wire

Stats

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

Differences b/w logic , reg & wire

archive
archive over 18 years ago

hi,

1.      i  know the differences between reg & wire...but i what to know the differences between logic , reg & wire clearly.

2.     When iam writing code in systemverilog using URM ..... i got a simple bug.. which iam pasting below & please let me know where to use reg , wire & logic in systemverilog coding.....


  
      

ncelab: *W,ENUMERR (./sv_module/sips_apb_env.sv,53|66): This
assignment is a violation of SystemVerilog strong typing rules for
enumeration datatypes.
            .PWRITE(dut_if.PWRITE),
                  |
ncelab: *E,ICDPAV (./sv_module/sips_apb_dut_wrap.sv,25|19): Illegal combination
of driver and procedural assignment to variable dut_if.PWRITE detected.
            .PADDR(dut_if.PADDR),
                 |
ncelab: *E,ICDPAV (./sv_module/sips_apb_dut_wrap.sv,26|18): Illegal combination
of driver and procedural assignment to variable dut_if.PADDR detected.
            .PWDATA(dut_if.PWDATA),      


... Raghavendra


Originally posted in cdnusers.org by raghavendrap
  • Cancel
Parents
  • archive
    archive over 18 years ago

    ncelab: *W,ENUMERR (./sv_module/sips_apb_env.sv,53|66): This
    assignment is a violation of SystemVerilog strong typing rules for
    enumeration datatypes.
    .PWRITE(dut_if.PWRITE),



    You need to show us the declaration of:

    PWRITE inside the DUT and
    dut_if.PWRITE



    ncelab: *E,ICDPAV (./sv_module/sips_apb_dut_wrap.sv,25|19): Illegal combination
    of driver and procedural assignment to variable dut_if.PWRITE detected.



    Again we need full declaration that shows:

    1. Data type
    2. Direction (I/O/IO)

    to comment properly. From the clear error message it is clear that you have a "procedural assignment" - say inside task/function/initial PWRITE and perhaps a "net" connection from a block beneath.

    Show us full code to help better. If it is too many lines, consider posting a tar ball or send via email ajeetha <> gmail.com

    Interestingly I was doing some revamp of our (CVC, www.noveldv.com) SystemVerilog training material this week and found similar examples that we show during our classes.

    Regards
    Ajeetha, CVC
    www.noveldv.com


    Originally posted in cdnusers.org by ajeetha
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    ncelab: *W,ENUMERR (./sv_module/sips_apb_env.sv,53|66): This
    assignment is a violation of SystemVerilog strong typing rules for
    enumeration datatypes.
    .PWRITE(dut_if.PWRITE),



    You need to show us the declaration of:

    PWRITE inside the DUT and
    dut_if.PWRITE



    ncelab: *E,ICDPAV (./sv_module/sips_apb_dut_wrap.sv,25|19): Illegal combination
    of driver and procedural assignment to variable dut_if.PWRITE detected.



    Again we need full declaration that shows:

    1. Data type
    2. Direction (I/O/IO)

    to comment properly. From the clear error message it is clear that you have a "procedural assignment" - say inside task/function/initial PWRITE and perhaps a "net" connection from a block beneath.

    Show us full code to help better. If it is too many lines, consider posting a tar ball or send via email ajeetha <> gmail.com

    Interestingly I was doing some revamp of our (CVC, www.noveldv.com) SystemVerilog training material this week and found similar examples that we show during our classes.

    Regards
    Ajeetha, CVC
    www.noveldv.com


    Originally posted in cdnusers.org by ajeetha
    • 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