• 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. Use of a specify block within a SystemVerilog interface

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 17265
  • 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

Use of a specify block within a SystemVerilog interface

SCollins
SCollins over 12 years ago

Hi All, 

I'm currently converting a legacy testbench to use SystemVerilog interfaces between the DUT and some behavioural models. The testbench code includes a specify block that uses the $width system task to check for glitches on a signal between the DUT and one of the models.

I've tried to update the code so that the $width task now checks the equivalent signal within the interface instance, which connects the DUT and the model. For example:

specify

$width(posedge interface_inst.my_signal, 100, 0, my_notifier);

endspecify

Unfortunately Incisive reported a ncvlog error (ILLHIN) for the line containing the $width task call:

"A hierarchical name was used as an identifier where a hierarchical name is not allowed. Use a simple identifier."

I then moved the specify block to the interface itself, as on reflection, this seems a more suitable place anyway. The specify block is defined within the scope of the interface declaration. For example:

interface my_interface ();

logic my_signal, ...etc

modport ( ...);

specify

$width(posedge my_signal, 100, 0, my_notifier);

endspecify

endinterface

This time, Incisive reported a different ncvlog error (DECINM) for the line containing the specify keyword:

"The declaration is only valid within a module, interface, and program and not supported within task, function and package."

The message clearly states that a specify block within an interface is supported so why is Incisive reporting an error?

Thanks in advance for any help.

  • Cancel
Parents
  • SCollins
    SCollins over 12 years ago

    I have since found out that IEEE Std 1800 (SystemVerilog LRM) does not allow specify blocks to be defined in interfaces.

    Also, Incisive does not currently support the use of hierarchical references in specify blocks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • SCollins
    SCollins over 12 years ago

    I have since found out that IEEE Std 1800 (SystemVerilog LRM) does not allow specify blocks to be defined in interfaces.

    Also, Incisive does not currently support the use of hierarchical references in specify blocks.

    • 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