Stats

  • Locked Locked
  • Replies 4
  • Subscribers 142
  • Views 13591
  • 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

cdlinGuiDisplay inside procedure...

archive

I am trying to do a skill script for the automation of the import of CDL netlists to schematic views. For this, I open the CDLImport dialog with the skill function cdlinGuiDisplay( ) and fill it with some values processed by the script. This works fine as long as the script is just loaded and run.

In order to make the set of processed cells/netlists controlable by the user, I tried to define the whole flow as a  procedure so that the target library and source netlists can be specified as arguments.

In that case, the cdlinGuiDisplay( ) function opens the CDLImport dialog but then the procedure does not progress until the dialog is manually closed. In case it is closed by the "OK" button the CDL Import is even executed twice (once for the manual interaction and once for the script).

Can you tell me what I am doing wrong (and if there is a possibility to avoid this behaviour)?

The code looks in principal like this:

procedure( cdl2schematic( )

  ... code ...

  cdlinGuiDisplay( )
  hiiSetCurrentForm('cdlInGuiForm)
  cdlInGuiForm->paramFile->value = "/"
  _cdlInParamFileLoadCB( )
  hiFormDone( cdlInGuiForm )

  ... code ...

)

Thanks for any help in advance!
Sebastian


Originally posted in cdnusers.org by sroehrig

  • Just noticed that there is a copy/paste error in the quoted code. It should say

    cdlInGuiForm->paramFile->value = "[my path][my file]"

    in line 7.


    Originally posted in cdnusers.org by sroehrig

  • The problem is that many forms in DFII are blocking - this means that any code which displays the form will block until the form is OK'd or canceled. This can be changed, but only at the time the form is created - so it isn't possible in this case.

    So there are two approaches here.

    1. Create the template files for "nino" and invoke that using ipcBeginProcess to do the import.
    2. Write a function which will fill in the form field, and so on (i.e. everything after the cdlinGuiDisplay), and then
    call this using hiRegTimer("myFunction()" 0) just before calling cdlinGuiDisplay. This means that as soon
    as the toplevel returns, it will execute myFunction, which can then fill in the form and OK it.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett

  • Thanks for the quick reply! Approach #1 perfectly solves my problem. It is (of course ;-)) even better than my original approach as I did not really intend to open the GUI but did not see another solution for getting the CDL import feature to work from within the IC environment. Invoking the nino command via "system" or "csh" caused me some headaches but the ipc approach is perfect.

    Just for curiosity: with approach #2, would I (the end user) still have to close the form manually? To be honest I do not understand what "as soon as the toplevel returns" means here. Does it mean as soon as the procedure in which cdlinGuiDisplay is invoked returns? I assume not, because then it would not enhance the situation ;-)

    Anyway, thanks for the help! Cheers,
    Sebastian


    Originally posted in cdnusers.org by sroehrig

  • As you already have the solution Iam just proposing another approach which may be more easy.
    Instead of hiFormDone( cdlInGuiForm ) try using _cdlInCB()


    procedure( cdl2schematic( )

    ... code ...

    cdlinGuiDisplay( )
    hiiSetCurrentForm('cdlInGuiForm)
    cdlInGuiForm->paramFile->value = "/"
    _cdlInParamFileLoadCB( )
    [b] hiFormDone( cdlInGuiForm ) ------------> _cdlInCB() [/b]

    ... code ...

    )


    Originally posted in cdnusers.org by sagirameshraju

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.