• 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. Custom IC SKILL
  3. Correct syntax for input stimulus with bus notation

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 143
  • Views 13929
  • 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

Correct syntax for input stimulus with bus notation

ThomasThoe
ThomasThoe over 5 years ago

Hi,

I am having some troubles creating an input stimulus file for my simulations when there are bus signals involved.

I am including a .scs file in a maestro view with the stimulus field. So for example (hopefully no c&p errors):

stim.scs

simulator lang=spectre
_vlayer_0 ([#layer_0<0>] 0) vsource type=dc dc=0

When running the netlister, my input.scs then includes a .scs file that resides in the /stimulus/ subdirectory and was seemingly created by the netlister. So the netlisting itself seems to complete.

The created stimulus netlist now has:

simulator lang=spectre
_vlayer_0 (layer_0<0> 0) vsource type=dc dc=0

Which when simulating causes:

Cannot run the simulation because the syntax error `Unexpected operator "<". Expected block statement,...

Is this a bug with the name mapping feature ? I would expect the generated netlist to have a backslash character before the <, but I might be wrong here. If I add extra backslashes, like [#bus\<0\>], then these get deleted as well by the mapping feature.

Any pointers on how to do this correctly ? The documentation unfortunately only links to an example that doesn't use bus notation.

Thanks a lot,

Thomas

  • 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