• 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. Accuracy of CROSS() function in Verilog-A

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 26639
  • 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

Accuracy of CROSS() function in Verilog-A

RFStuff
RFStuff over 11 years ago

Dear All,

I am using cross() in verilog-A as below:-

 

vtol=1e-12;

@(cross(phase-10u,+1,ttol,vtol)) begin
       $strobe("TIME = %rs \n", $abstime);
     end

But when I checked the abstime, it is NOT exactly at 10u of phase but at 10.541u of phase. This error is much larger than my vtol value.

But when I chnaged to strobeperiod of tran analysis to  1ns, abstime shows up at phase value of 10.002u.

I wonder why such descrpancy and why vtol  is NOT playing any role here.

Kind Regards,

 

 

  • Cancel
Parents
  • RFStuff
    RFStuff over 11 years ago

    Dear Andrew,

    Thanks a lot for your time and reply.

    I realised that it is NOT the cross() issue.

    The issue lies in idt(). 

    When the "phase" crosses "T_period" ( cross() is accurate no doubt ) , "reset" becomes one 1 at that instant.

    But idt() becomes zero in the next time point which is NOT controlled one ( it depends upon Spectre simulation).

    This leads to period error of the Oscillator.

    Same is the case for idtmod(). 

    Is there any way I can make idt() = 0 at the exact time instant when "reset" becomes 1 though it is completely abrupt and discontinuous.

     

    Kind Regards,

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • RFStuff
    RFStuff over 11 years ago

    Dear Andrew,

    Thanks a lot for your time and reply.

    I realised that it is NOT the cross() issue.

    The issue lies in idt(). 

    When the "phase" crosses "T_period" ( cross() is accurate no doubt ) , "reset" becomes one 1 at that instant.

    But idt() becomes zero in the next time point which is NOT controlled one ( it depends upon Spectre simulation).

    This leads to period error of the Oscillator.

    Same is the case for idtmod(). 

    Is there any way I can make idt() = 0 at the exact time instant when "reset" becomes 1 though it is completely abrupt and discontinuous.

     

    Kind Regards,

     

    • 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