• 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. Error in verilogA

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 15667
  • 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

Error in verilogA

sreeni
sreeni over 12 years ago

Hi to all

Am designing one model in verilog-A. 

In that i have defined one function (Charge_low) and while using it in the main design it showing some error.

Am not able to understand the error.

 hsp-vacomp: Error: syntax error

 hsp-vacomp:     ['SBCNTFET.va',399]

 hsp-vacomp:     Qs_low1 = Charge_low(  2.32  ,H1,b1_1,b0_1)-Charge_low(`alpha_1,L1,b1_1,b0_1);
 hsp-vacomp:                                                         ^

 Error was showing @ the "," after H1.

All variables in the function are declared as real and defined.

Please let me know what may be the error.

 

Thanks

SRINI

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Srini,

    Again, you didn't really give enough to be sure, but I corrected two mistakes in what you sent me:

    1. The function charge_low had an input called "bo" but in the expression, it's called "b0".
    2. The function is defined as "charge_low" but called as "Charge_low". Verilog-A is case sensitive.

    I then assembled a simple example module using both these, with some definitions for `alpha_1 and the other arguments:

     `include "disciplines.vams"

    module forum (x);
    input x;
    electrical x;

    analog function real hspsqrt;
      input a;
      real a;
      hspsqrt=sqrt(a);
    endfunction

    analog function real hsppow;
      input a,b;
      real a,b;
      hsppow=pow(a,b);
    endfunction

    analog function real hspln;
      input a;
      real a;
      hspln=ln(a);
    endfunction

    analog function real eeta;
            input x,y;
            real x,y;
            begin
                eeta  = hspsqrt(x*y*y+y);
            end
        endfunction

    analog function charge_low;
    //input x,y,b1,bo;
    //real x,y,b1,bo;
    input x,y,b1,b0;
    real x,y,b1,b0;
      begin
         charge_low = eeta(x,y)*((b1*(y-(1/2*x)))+(2*b0))+((b1)/(4*hsppow(x,1.5)))* hspln(((0.5+(x*y))/(hspsqrt(x)))+(eeta(x,y)));
       end
    endfunction

    `define alpha_1 2.32


    real H1,b1_1,b0_1,L1,Qs_low1;

    analog begin
        @(initial_step) begin
            H1=1.0;
            b1_1=1.0;
            b0_1=1.0;
            L1=1.0;
            //Qs_low1 = Charge_low(`alpha_1,H1,b1_1,b0_1)-Charge_low(`alpha_1,L1,b1_1,b0_1);
            Qs_low1 = charge_low(`alpha_1,H1,b1_1,b0_1)-charge_low(`alpha_1,L1,b1_1,b0_1);
        end

        V(x) <+ 1.0;
    end

    endmodule

    With spectre, I created this netlist:

    //

    thing (n1) forum
    r1 (n1 0) resistor r=1k

    ahdl_include "forum.va"

    dc dc

    And spectre was quite happy when I ran this. So you need to take this up with Synopsys - assuming that you've corrected the typos I mentioned earlier and that doesn't fix it. Note I had to define all those hspsqrt, hspln, hsppow functions because they don't exist in the standard language. So probably Synopsys customer support is your best bet.

    Kind Regards,

    Andrew.

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

    Srini,

    Again, you didn't really give enough to be sure, but I corrected two mistakes in what you sent me:

    1. The function charge_low had an input called "bo" but in the expression, it's called "b0".
    2. The function is defined as "charge_low" but called as "Charge_low". Verilog-A is case sensitive.

    I then assembled a simple example module using both these, with some definitions for `alpha_1 and the other arguments:

     `include "disciplines.vams"

    module forum (x);
    input x;
    electrical x;

    analog function real hspsqrt;
      input a;
      real a;
      hspsqrt=sqrt(a);
    endfunction

    analog function real hsppow;
      input a,b;
      real a,b;
      hsppow=pow(a,b);
    endfunction

    analog function real hspln;
      input a;
      real a;
      hspln=ln(a);
    endfunction

    analog function real eeta;
            input x,y;
            real x,y;
            begin
                eeta  = hspsqrt(x*y*y+y);
            end
        endfunction

    analog function charge_low;
    //input x,y,b1,bo;
    //real x,y,b1,bo;
    input x,y,b1,b0;
    real x,y,b1,b0;
      begin
         charge_low = eeta(x,y)*((b1*(y-(1/2*x)))+(2*b0))+((b1)/(4*hsppow(x,1.5)))* hspln(((0.5+(x*y))/(hspsqrt(x)))+(eeta(x,y)));
       end
    endfunction

    `define alpha_1 2.32


    real H1,b1_1,b0_1,L1,Qs_low1;

    analog begin
        @(initial_step) begin
            H1=1.0;
            b1_1=1.0;
            b0_1=1.0;
            L1=1.0;
            //Qs_low1 = Charge_low(`alpha_1,H1,b1_1,b0_1)-Charge_low(`alpha_1,L1,b1_1,b0_1);
            Qs_low1 = charge_low(`alpha_1,H1,b1_1,b0_1)-charge_low(`alpha_1,L1,b1_1,b0_1);
        end

        V(x) <+ 1.0;
    end

    endmodule

    With spectre, I created this netlist:

    //

    thing (n1) forum
    r1 (n1 0) resistor r=1k

    ahdl_include "forum.va"

    dc dc

    And spectre was quite happy when I ran this. So you need to take this up with Synopsys - assuming that you've corrected the typos I mentioned earlier and that doesn't fix it. Note I had to define all those hspsqrt, hspln, hsppow functions because they don't exist in the standard language. So probably Synopsys customer support is your best bet.

    Kind Regards,

    Andrew.

    • 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