• 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. RF Design
  3. How to avoid Hidden State in VerilogA model for Spectre...

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 66
  • Views 25185
  • 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

How to avoid Hidden State in VerilogA model for SpectreRF

RFStuff
RFStuff over 12 years ago

 Dear All,

I am a beginner in verilogA .

I wrote a code but when I ran PSS it showed hidden state in the code and didn't run.

My behavioural model is as below:-

 

 

// VerilogA for VERILOG_A_MODEL, HARD_LIMIT_GM, veriloga

`include "constants.vams"
`include "disciplines.vams"

module HARD_LIMIT_GM(in,out);
  inout in,out;
  parameter real vtrans = 0;
  parameter real tdelay = 0 from [0:inf);
  parameter real trise = 1p from (0:inf);
  parameter real tfall = 1p from (0:inf);
  parameter real Gm=-5m;
  electrical in,out;
  real vout_val;
  analog begin
 
         @ (cross(V(in) - vtrans, 1))  vout_val = 1;
         @ (cross(V(in) - vtrans, -1)) vout_val = 0;
 
         I(out) <+ Gm * transition( vout_val, tdelay, trise, tfall); 
  end   
endmodule

 

Could anybody please tell how I can avoid the hidden state  (vout_val ) ?

 

Kind Regards,

  • Cancel
Parents
  • kapiljainwal
    kapiljainwal over 9 years ago

    Dear Andrew,

    I am using AMS kit.

    I have made circuit using schematic editor but while I am running PSS analysis, it is getting terminated with showing following error:

     ERROR (SPCRTRF-15177): PSS analysis doesn't support behavioral module components with hidden states found in component 'modn_ahdl'.  Skipped.

    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vgs_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vds_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vgb_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vdb_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vsb_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vbpsub_ot

    The same message is appearing for PSS analysis for all circuits.

    Thanks and Regards,

    Kapil J.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • kapiljainwal
    kapiljainwal over 9 years ago

    Dear Andrew,

    I am using AMS kit.

    I have made circuit using schematic editor but while I am running PSS analysis, it is getting terminated with showing following error:

     ERROR (SPCRTRF-15177): PSS analysis doesn't support behavioral module components with hidden states found in component 'modn_ahdl'.  Skipped.

    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vgs_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vds_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vgb_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vdb_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vsb_ot
    /root/cadence/ams/AMS_410_CDS/spectre/c35/soac/soac.va, declared in line 23: Hidden state variable: vbpsub_ot

    The same message is appearing for PSS analysis for all circuits.

    Thanks and Regards,

    Kapil J.

    • 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