Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 2522
  • 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

unbound variable - device property issue

sjwprcker

Hi,

I set a variable "L350" to NMOS transistor length and sweep the variable. It works well. 

However, after I try parameterization on its length, accidently cds shows the unbound variable issue of "L350", CIW report: CDF parameter function has problem. And when I open property of NMOS transistor by "Q", all CDF info disappear. 

I can forcely open property assistant view, and find many yellow exclamation mark as below. Btw, the netlisting and simulation still work with this issue. 

Is there anyway to recover the CDF settings as before? Thanks!

Parents
  • Andrew Beckett

    The error message is pretty clear - report this to the supplier of the PRIMLIB library, which is presumably AMS (given by the callback name)? What it means is that the CDF callback for this field doesn't support variables being used in the length field - most likely they are trying to evaluate the value using evalstring() which won't work and is not safe. Not sure why all the properties would go missing on the edit properties form, but either way you need to take this up with the provider of the PDK. It's their code that is breaking.

    Andrew.

Reply
  • Andrew Beckett

    The error message is pretty clear - report this to the supplier of the PRIMLIB library, which is presumably AMS (given by the callback name)? What it means is that the CDF callback for this field doesn't support variables being used in the length field - most likely they are trying to evaluate the value using evalstring() which won't work and is not safe. Not sure why all the properties would go missing on the edit properties form, but either way you need to take this up with the provider of the PDK. It's their code that is breaking.

    Andrew.

Children
  • sjwprcker
    in reply to Andrew Beckett

    Hi Andrew, thanks for your feedback. I will contact with them. 

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.