Stats

  • Locked Locked
  • Replies 5
  • Subscribers 144
  • Views 14343
  • 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

about the function of dbCreateParamInst

b0719r

Hi Everyone,

I am using the function of  dbCreateParamInst to draw a rf nmos with w, l, #f can be changed, however, when I use this function as below:

 paramList=list(list("wf" "float" fw) list("lf" "float" fl) list("nf" "int" nf))
    a=-(0.98*nf/4-0.2)
    b=-fw/2
   inst= dbCreateParamInst(newCV master nil a:b "R180" 1 paramList)

the mos size can not be changed, which seems as default size. I think the problem is the propName I use, it may be wrong. but I use this names before in the 90nm, it works ok, when I use them into 65nm, it doesn't work anymore. 

Is anyone have the idea that how to find the propName? or how to solve this problem?

Parents

  •  Hi Quek,

     

    Thank you for answerming my question. I have checked the type thing, it is "string" in cdf, however, when I use umc90nm, the setting is the same, but it works for my code to use "float". So I think this is not problem. 

    Now my situation is that, when I check the nmos I drawed by this skill code,   I can see the parameters has been changed, but total width is not, which will be changed when I change parameters mannually. 

     Do you have any idea about this problem? 

     Best regards,

    Aleck
Reply

  •  Hi Quek,

     

    Thank you for answerming my question. I have checked the type thing, it is "string" in cdf, however, when I use umc90nm, the setting is the same, but it works for my code to use "float". So I think this is not problem. 

    Now my situation is that, when I check the nmos I drawed by this skill code,   I can see the parameters has been changed, but total width is not, which will be changed when I change parameters mannually. 

     Do you have any idea about this problem? 

     Best regards,

    Aleck
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.