• 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. Specman syntax errors

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 13706
  • 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

Specman syntax errors

Sarathi
Sarathi over 15 years ago
Hi Stephen Thanks for the previous help. I tried it and it worked with the latest versions of Specman as well. I have a new problem. I am trying to run DV using specman but I get a lot of syntax errors when I load the e-code in the specman environment. I used all the following Specman versions v4.3.1, v5.03, v5.1, v08.10.001, v08.20.002 and I tried running on both LINUX and SOLARIS as well. All of them gave the syntax errors The syntax errors are due to the following coding style: operate: ... ... end; All the action block statements have the similar syntax of ": ... end;" instead of "{...};" Can you identify the syntax used? Which version of Specman will it work with? Regards Bharath StephenH wrote: > > Hi Sarathi. > > It sounds like you've instantiated all your verification code directly > in sys, is that correct? > Cadence does not recommend this approach as it makes the code harder > to re-use between projects and from block to system level. > Instead you should encapsulate your testbench code in at least one > unit that you then instantiate inside sys. > > If all your code currently is written like this: > extend sys { > event clk is rise('clock') @sim; > ... > }; > > You could fairly easily change to swap "sys" to another unit name, > like this: > unit tb like any_unit { }; > extend tb { // instead of sys > event clk is rise('clock') @sim; > ... > }; > extend sys { // new block of code > tb : tb is instance; > keep tb.hdl_path() == "~/"; > }; > > This might still need some tweaking for your testbench coding style if > you used any full hierarchical paths from sys, but it's definitely the > right direction to be moving in. > > If you get really stuck, file a service request through SourceLink, > and one of hte support team would be able to help you without you > having to share any details of your code in this public forum... > > Good luck! :-) > > Steve. > > > > -- > View this message online at: > www.cadence.com:443/.../16151.aspx > -- > You received this email because you subscribed to notifications for > the Cadence Functional Verification Forum. To unsubscribe, log in, go > to forums, and change your forum subscriptions. > > www.cadence.com/.../ForumSubscriptions.aspx
  • Cancel
Parents
  • StephenH
    StephenH over 15 years ago

    The information about supported tool versions can be found on the SourceLink web site:

    http://sourcelink.cadence.com/en/infomgmt/DisplayStaticLink.jhtml?/docs/files/lifecycle/EORsupported.html

    This shows that Specman 6.0 is the oldest version still supported by Cadence.
    Version 2.0 pre-dates my career with Verisity, so I cannot comment on the syntax from that version!

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 15 years ago

    The information about supported tool versions can be found on the SourceLink web site:

    http://sourcelink.cadence.com/en/infomgmt/DisplayStaticLink.jhtml?/docs/files/lifecycle/EORsupported.html

    This shows that Specman 6.0 is the oldest version still supported by Cadence.
    Version 2.0 pre-dates my career with Verisity, so I cannot comment on the syntax from that version!

     

    • 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