• 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 Design
  3. Simulation files and bus syntax

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 127
  • Views 18258
  • 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

Simulation files and bus syntax

simbamford
simbamford over 15 years ago

 Hi,

 

I have a design with some nodes using bus syntax, for example some nodes labelled BL<1:2>.

I create a stimulation file (.scs) containing:

 _BL1 (BL<1> 0) vsource type=dc dc=0
_BL2 (BL<2> 0) vsource type=dc dc=3.3

but when it parses it it gives the following error:

ERROR (SFE-874): "/home/sim/Cadence/Sim/SynMem_Test/spectre/schematic/netlist/stimuli/2010_04_14SynMem_Test.scs" 1: Unexpected operator "<". Expected end of file or end of line.
ERROR (SFE-874): "/home/sim/Cadence/Sim/SynMem_Test/spectre/schematic/netlist/stimuli/2010_04_14SynMem_Test.scs" 2: Unexpected operator "<". Expected end of file or end of line.

I assume I have to write something special for it to accept the bus syntax. Looking in the netlist it normally produces without the stimulation file, I see, for example:

InvBL\<1\> (nBL\<1\> BL\<1\> 0 vdd!) INV1
InvBL\<2\> (nBL\<2\> BL\<2\> 0 vdd!) INV1

 However when I try using the backslash in my stimulation file, like this:

 _BL1 (BL\<1\> 0) vsource type=dc dc=0
_BL2 (BL\<2\> 0) vsource type=dc dc=3.3

 I get the same error.

 Can anyone suggestion a solution?

 Thanks

Sim Bamford

 

  • Cancel
Parents
  • simbamford
    simbamford over 15 years ago

     Hi Andrew,

     

    Thanks very much for this. Mixed results though. It will now parse the file. However in the input.scs file that it generates for the design from the schematic, bus nodes that were previously listed as e.g. bus\<1\> are now listed as bus_1. Then, if I select one of those from the schematic for being saved and plotted, this appears in the save statement as  bus\<1\>, with the effect that they are not recognised as nodes and not saved or plotted. Any ideas? (I'm not stuck though because I can use "nmp" mapping and double backslashes for now). 

    One more related question: in my design I had a bus called BLin<1:36>. When I simulated this, node BLin<35> and only that one caused problems - it seemed to recognise that node as already existing, although it's nowhere else in my design. when I changed the name of the bus to e.g. BLInputs<1:36> the problem went away. Have I hit on a reserved word or something like that?

     Thanks

    Sim Bamford

     

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

     Hi Andrew,

     

    Thanks very much for this. Mixed results though. It will now parse the file. However in the input.scs file that it generates for the design from the schematic, bus nodes that were previously listed as e.g. bus\<1\> are now listed as bus_1. Then, if I select one of those from the schematic for being saved and plotted, this appears in the save statement as  bus\<1\>, with the effect that they are not recognised as nodes and not saved or plotted. Any ideas? (I'm not stuck though because I can use "nmp" mapping and double backslashes for now). 

    One more related question: in my design I had a bus called BLin<1:36>. When I simulated this, node BLin<35> and only that one caused problems - it seemed to recognise that node as already existing, although it's nowhere else in my design. when I changed the name of the bus to e.g. BLInputs<1:36> the problem went away. Have I hit on a reserved word or something like that?

     Thanks

    Sim Bamford

     

    • 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