• 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
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    I had some trouble running it - I had to change KT to be a smaller number (see the comment in the code below). The key seemed to be moving the definition of phase to above the cross. I think the issue is that it was using the previous iteration's value of phase.

    I also changed it to use phase again rather than V(phase_out) (spectre advised me that it had changed it back to a real number for performance reasons anyway).

    This was the netlist I used to test it with:

     //

    OSC1 (in op1 op2) DCO

    v1 (in 0) vsource type=dc dc=1
    r1 (op1 0) resistor r=100k
    r2 (op2 0) resistor r=100k

    ahdl_include "DCO.va"

    tran tran stop=1m


     // VerilogA for VERILOG_A_MODEL, DCO, veriloga
    
    `include "constants.vams"
    `include "disciplines.vams"
    
    module DCO (in, out,out1);
    
    input in;
    output out,out1;
    electrical in, out,out1;
    parameter real Vlo=0, Vhi=1.25;
    
    parameter real Vth=0;
    
    parameter real ttol=1p;
    parameter real vtol=1p;
    parameter real tt = 1p;
    
    
    // changed KT value because it seemed enormous to me otherwise!
    parameter real KT=200e-6;
    parameter real Tv_0= 0.5n;
    real n,delay;
    parameter real start_delay=1n;
    
    real T_period;
    real Time_Span;
    real phase,reset;
    
    
    
    analog begin
    
    @(initial_step) begin
          V(out) <+ 0;    
          
          delay= start_delay;
          reset =0;
     end
     
     T_period = Tv_0 + KT * V(in) ;
    
    // $strobe("T_period is ",T_period);
     
     
    
     phase= idt(1,0,reset) - delay; // Phase Integration
     reset =0;
    
    // V(phase_out) <+ phase;
        
     @(cross(phase-T_period,+1,ttol,vtol)) begin
           reset=1;
           delay =0;
           $strobe("T_period is ",T_period);
           $strobe("cross val is ",phase-T_period);
           $strobe("EDGE_TIME = %rs \n", $abstime);
          
         end
         
    // $strobe("phase is ",phase);
    
    
      n= (phase >=0) && (phase < (T_period/2));
         
         V(out) <+ transition(n ? Vhi:Vlo,0,tt);
         V(out1) <+ phase ;
         
         //$bound_step(0.01n);     
         
    end
     endmodule

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    I had some trouble running it - I had to change KT to be a smaller number (see the comment in the code below). The key seemed to be moving the definition of phase to above the cross. I think the issue is that it was using the previous iteration's value of phase.

    I also changed it to use phase again rather than V(phase_out) (spectre advised me that it had changed it back to a real number for performance reasons anyway).

    This was the netlist I used to test it with:

     //

    OSC1 (in op1 op2) DCO

    v1 (in 0) vsource type=dc dc=1
    r1 (op1 0) resistor r=100k
    r2 (op2 0) resistor r=100k

    ahdl_include "DCO.va"

    tran tran stop=1m


     // VerilogA for VERILOG_A_MODEL, DCO, veriloga
    
    `include "constants.vams"
    `include "disciplines.vams"
    
    module DCO (in, out,out1);
    
    input in;
    output out,out1;
    electrical in, out,out1;
    parameter real Vlo=0, Vhi=1.25;
    
    parameter real Vth=0;
    
    parameter real ttol=1p;
    parameter real vtol=1p;
    parameter real tt = 1p;
    
    
    // changed KT value because it seemed enormous to me otherwise!
    parameter real KT=200e-6;
    parameter real Tv_0= 0.5n;
    real n,delay;
    parameter real start_delay=1n;
    
    real T_period;
    real Time_Span;
    real phase,reset;
    
    
    
    analog begin
    
    @(initial_step) begin
          V(out) <+ 0;    
          
          delay= start_delay;
          reset =0;
     end
     
     T_period = Tv_0 + KT * V(in) ;
    
    // $strobe("T_period is ",T_period);
     
     
    
     phase= idt(1,0,reset) - delay; // Phase Integration
     reset =0;
    
    // V(phase_out) <+ phase;
        
     @(cross(phase-T_period,+1,ttol,vtol)) begin
           reset=1;
           delay =0;
           $strobe("T_period is ",T_period);
           $strobe("cross val is ",phase-T_period);
           $strobe("EDGE_TIME = %rs \n", $abstime);
          
         end
         
    // $strobe("phase is ",phase);
    
    
      n= (phase >=0) && (phase < (T_period/2));
         
         V(out) <+ transition(n ? Vhi:Vlo,0,tt);
         V(out1) <+ phase ;
         
         //$bound_step(0.01n);     
         
    end
     endmodule

     

    • 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