Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 3151
  • 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

ADE simulation files -- error

Thodoros

 Hello,

I am trying to assign a simulation file to a ADE run (ADE ->setup -> simulation files) which contains the simple that follows:

simulator lang=spectre
_vAddr\<3\> (Addr\<3\> 0) vsource val0=0 val1=0 period=500p width=250p type=pulse

 I have ic6.1.4 and when I execute "Netlist and Run" I get the following error:

 Error found by spectre during circuit read-in.
     ERROR (SFE-874): "/home/simop/simulation/sram_PCCA/spectre/schematic/netlist/stimuli/stem" 2: Unexpected operator "<".

What really happens is that at the ~/ ... /simulation/<design>/schematic/netlist/stimuli/ directory the copied stimuli file has errased the "\" character.

I really have to add that character and perform ADE ->Simulation ->Run in order to continue with the simulation.

Can I ovefrcome this?

Thanks,

Thodoros

Parents
  • Thodoros

     OK I found a walk aroud.

     

    Instead of writing the stimuli

    simulator lang=spectre
    _vAddr\<3\> (Addr\<3\> 0) vsource val0=0 val1=0 period=500p width=250p type=pulse

     

    I add an extra "\" and the stimuli

    simulator lang=spectre
    _vAddr\\<3\\> (Addr\\<3\\> 0) vsource val0=0 val1=0 period=500p width=250p type=pulse

     is OK

    Is this the proper way of writing stimuli files?

    Thanks,

    Thodoros

Reply
  • Thodoros

     OK I found a walk aroud.

     

    Instead of writing the stimuli

    simulator lang=spectre
    _vAddr\<3\> (Addr\<3\> 0) vsource val0=0 val1=0 period=500p width=250p type=pulse

     

    I add an extra "\" and the stimuli

    simulator lang=spectre
    _vAddr\\<3\\> (Addr\\<3\\> 0) vsource val0=0 val1=0 period=500p width=250p type=pulse

     is OK

    Is this the proper way of writing stimuli files?

    Thanks,

    Thodoros

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.