Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13995
  • 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

Changin strobeperiod

Bernd das Brot

Hello,

I'm running a transient long time simulation (spectreVerilog) and have to store several signals. Up to now I don't need the exact timing in the resulting data and therefore I set a strobeperiod which is about a quarter of the master clock periodto reduce the data.

 But now I need the "exact" timing for some special phases of the simulation (about 10% of the whole simulation time).

 I found the information, how to change the timestep during the simulation by using $bound_step in ahdl/verilog-a, but i don't want to influence the simulation steps but the stored values. Is there a way to tempoary change or disable the strobeperiod setting? 

thanks!

 

Parents

  • Thank You for your response. I had a terrible feeling you were going to write that.

    There were some points, which made me ignoring this option:

    1. There are 3 periods in my simulation, where I would like to habe the "high resolution". 

    2. It's difficult to determine in advance the times, when these periods appears.

    I guess, I can only define one period by using skipstart/skipstop and I have to set them before simulation starts.

    Therefore I was hoping, there would be a way to modify this setting event driven. I found the $bound_step statement in solution 11167712 and I planned to do something like 

    always @(posedge any_usefull_startsignal ) $strobeperiod( small_steps)

    always @(negedge any_usefull_startsignal ) $strobeperiod( large_steps)

    ( I guess, I mixed up some languages. Up to now, I used verilog and ahdl and just going to start with verilog-a) 

    I guess, I have to try skipstop. I hope, I can cope with it.

    Regards

Reply

  • Thank You for your response. I had a terrible feeling you were going to write that.

    There were some points, which made me ignoring this option:

    1. There are 3 periods in my simulation, where I would like to habe the "high resolution". 

    2. It's difficult to determine in advance the times, when these periods appears.

    I guess, I can only define one period by using skipstart/skipstop and I have to set them before simulation starts.

    Therefore I was hoping, there would be a way to modify this setting event driven. I found the $bound_step statement in solution 11167712 and I planned to do something like 

    always @(posedge any_usefull_startsignal ) $strobeperiod( small_steps)

    always @(negedge any_usefull_startsignal ) $strobeperiod( large_steps)

    ( I guess, I mixed up some languages. Up to now, I used verilog and ahdl and just going to start with verilog-a) 

    I guess, I have to try skipstop. I hope, I can cope with it.

    Regards

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.