Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 4488
  • 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* eval: undefined function -xxxxx_mosDisplay while using abConvertComponentParams.il to change device between different PDK

George Qin

Dear Andrew,

I want to change umc80nm device to umc55nm device in all schematics of my Library, but get *Error* eval: undefined function -xxxxx_mosDisplay while using abConvertComponentParams.il to change device between different PDK.

I load "abConvertComponentParams.il" and "abInvokeCdfCallbacks.il" and use the following function in CIW:

abConvertComponentParamsForLib("xxxx(my Library name) "schematic" "../../conv.config")

My conv.config file(for change NMOS as example):

Although the device seems correctly changed, I can not modify any parameter in the property of instance (as the pic below, some boxes are grey) 

CIW also shown these Error:

How can I solve this problem?

Thanks

  • This suggests something is wrong with the PDK installation, because that function is the display call-back for each of the parameters. It's nothing to do with the conversion code - it's simply that when trying to call the callback for each parameter to determine whether that parameter should be displayed or not (when editing properties or doing create instance) the function cannot be found.

    I don't believe that error would appear during the conversion code, because it doesn't use the display callback at all. It's just when you do edit properties or create instance after the conversion? I expect the same thing would happen if you  place an new instance of a component from the PDK.

    So you need to contact the foundry.

    Andrew.

  • in reply to Andrew Beckett

    Thanks, the problem is due to PDK, as you said.

    By the way, can I use the configure file formate below to converter all umc80nm instance to 55nm (Including mos, res ,cap,diode etc.)? It seems work well.

    What I mean is to omit the code :"params("w" width "l" length), addProps("isnoisy" t)" etc.

    (since I do not know what does these code do)

  • in reply to George Qin

    There's no requirement to have params or addProps in the config (note, the comments at the top of the code explain what they do). The params form is needed if you need to map a parameter name from one device to another or do some scaling - so for example if the parameter is called "l" in one PDK and "length" in the other. The addProps is needed if you want to add additional properties on the instance which weren't there before. If you don't need either of these things, then they can be safely omitted, as you've found.

    Regards,

    Andrew.

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.