• 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. Annotation does not work however, Print DC operating point...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 124
  • Views 7794
  • 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

Annotation does not work however, Print DC operating point works fine - ISSUE

FormerMember
FormerMember over 5 years ago

Hi,

So when I'm using an instance N_12_LLHVTRF (mosfet) from the umc65ll library, the annotation of the DC operating point does not work on the component. However, when I use the print dc operating points, then all the parameters are displayed. I am not sure on why this discrepancy is occuring. Due to this I am unable to sweep any dc op parameters, and I have to manually do the print dc operating point for every simulation, and this is becoming time consuming. (attached screenshots).

Also, when I go to the view-> annotations-> setup, I see that the expressions are greyed out and disabled. I did the annotate from the ADEL window too, however these fields remain disabled (attached screenshot)

Cadence version - IC6.1.7-64b.78

Please do help, if anyone has had this issue previously. (Andrew Beckett)

Thank you so much.

Avinash

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

    Tagging me on posts isn't necessary (by the way, I'm glad you finally posted a new post, rather than not following the forum guidelines and posting on the end of 10-year old threads). Other people are allowed to respond on these threads and I get notified on the posts anyway. I ignored the other two because you'd posted on the end of 10-year old threads with very little information, so I didn't see much benefit on responding to those other than to tell you to post a new thread, which you've now done, with sufficient detail.

    In this case, understanding what is not working is going to be a challenge without being able to see the PDK - it's a fault with the PDK, to be honest. My guess is that the models have subckt models and are maybe not "inline" subckts, and so it can't see the operating point parameters. This is not insurmountable as it can be fixed in the CDF too. However, advising what to do here is going to be challenging (especially as I don't have easy access to the PDK you're talking about).

    I would suggest first contacting UMC to find out if there's a fix for this, and then following up with customer support if that doesn't resolve it.

    Regards,

    Andrew.

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

    Tagging me on posts isn't necessary (by the way, I'm glad you finally posted a new post, rather than not following the forum guidelines and posting on the end of 10-year old threads). Other people are allowed to respond on these threads and I get notified on the posts anyway. I ignored the other two because you'd posted on the end of 10-year old threads with very little information, so I didn't see much benefit on responding to those other than to tell you to post a new thread, which you've now done, with sufficient detail.

    In this case, understanding what is not working is going to be a challenge without being able to see the PDK - it's a fault with the PDK, to be honest. My guess is that the models have subckt models and are maybe not "inline" subckts, and so it can't see the operating point parameters. This is not insurmountable as it can be fixed in the CDF too. However, advising what to do here is going to be challenging (especially as I don't have easy access to the PDK you're talking about).

    I would suggest first contacting UMC to find out if there's a fix for this, and then following up with customer support if that doesn't resolve it.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Avinash Murugesan
    Avinash Murugesan over 5 years ago in reply to Andrew Beckett

    Thank you Andrew for your reply. Apologies for tagging you in the post. I read the guidelines only after I replied on the 10 year old posts, and then created the new post.

    I went to see the model files under the spectre section and noticed that the .scs file for the model does not have the "inline" keyword. So I went ahead and edited and added the inline keyword (please see below), and referenced the model library in the ADEL window. However, it still didn't seem to work. I have created a ticket with customer support and sent an email to UMC too.

    I tried playing with the CDF too, however it prevents me from editing, and says its read-only. 

    MODEL FILE - 

    inline subckt n_12_llhvtrf ( d g s b )
    parameters nf=5 lf=0.06u wf=8u con=1 sc=2.5u rshgo=12.47 rshgwf=1.833e-006 rshgnf=1.056 rde=1M hfn_flag=hfnoise
    + rshg=rshgo * (1+rshgwf / wf) * (1+rshgnf / nf) lffc=5.3e+007 wffc=8e-007 cfo=4.856e-011 .........

    Regards

    Avinash M

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Avinash Murugesan

    Hi Avinash,

    Just adding the inline keyword won't be enough. You also need to make sure that the instance name of the main transistor in the subckt has the same name as the subckt - i.e.

    inline subckt n_12_llhvtrf ( d g s b )
    parameters nf=5 lf=0.06u wf=8u con=1 sc=2.5u rshgo=12.47 rshgwf=1.833e-006 rshgnf=1.056 rde=1M hfn_flag=hfnoise
    + rshg=rshgo * (1+rshgwf / wf) * (1+rshgnf / nf) lffc=5.3e+007 wffc=8e-007 cfo=4.856e-011 .........

    n_12_llhvtrf (d g s b) modelname param=value param2=value2 ...

    This is how it would know that the  annotation data should come from that transistor.

    You may of course want to be a little cautious about changing the model files!

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Avinash Murugesan
    Avinash Murugesan over 5 years ago in reply to Andrew Beckett

    Dear Andrew,

    I figured that out too after reading the spectre documentation, that you should have the same name. I see that the instantiation (n_12_llhvtrf) is missing, and another mosmodel (mos_n_12) is being called. However, I am still trying to figure out which file this model is present in.

    mos_n_12 ( d g s b ) n_12_llhvtrf_main l=lf w=w nf=nf ad=p_area_d as=p_area_s pd=p_pj_d
    ++p_pj_dg ps=p_pj_s+p_pj_sg sa=sp_edge_nw+lf+sp_edge sb=sp_edge_nw+lf
    ++sp_edge sd=sp_poly sc=sc

    Thank you for your swift reply Andrew. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Avinash Murugesan

    The model is not mos_n_12, but n_12_llhvtrf_main. mos_n_12 is the instance name, and that's what needs to change to n_12_llhvtrf for the inline subckt to be useful. Caveat emptor...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Avinash Murugesan
    Avinash Murugesan over 5 years ago in reply to Andrew Beckett

    Dear Andrew, It worked right now, after replacing this. Thank you so much for your help. Appreciate it a lot.

    Regards

    Avinash M

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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