Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 13969
  • 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

Loading and streaming custom Pcell issue.

Petya

Hi,

I'm developing a skill pcell, but have a problem with loading it. I use two files one that has all my procedures and another that has the pcDefinePcell. I load the procedures file in the libInit.il file, and then load the pcell which compiles without problems. The next time I open a new session though it gives an Pcell eval fail error:

*WARNING* (DB-270002): ("funcall" 0 t nil ("*Error* funcall: argument #1 should be a function object or name (type template = \"ug\")" nil))

Also if I load it locally streaming out works. But when I use the library I created to be common and used by other users as well it doesn't :(

I tried using Pcell IDE, but somehow its doesn't work for me. Any help will be appreciated.

Thanks,

Petya

Parents
  • skillUser

    Hi Petya,

    You should only need to load the code with the pcDefinePCell statement if the parameters or their defaults change, otherwise you can just load the 'drawing code', provided that your code is structured something like the following:

    
::::::::::::::::::::::::::::::
:: file to define the PCell ::
::::::::::::::::::::::::::::::
let( (library cell pcellId)
  library="myLibName"
  cell="myCellName"
  unless(ddGetObj(library)
    error("Couldn't open library %L\n" library)
  )

  pcellId = pcDefinePCell(
    list(ddGetObj(library) cell "layout" "maskLayout")

    (
      (length   "10.0")
      (width    "10.0")
    )
    ;; call PCell drawing code
    MYdrawPCell(pcCellView length width)
  ); pcDefinePCell

  dbSave(pcellId)
  dbClose(pcellId)
)

::::::::::::::::::::::::::::::
::  file to draw the PCell  ::
::::::::::::::::::::::::::::::
procedure(MYdrawPCell(cv l w "dtt")
  ;; drawing code goes here
)

    Then each time you change the drawing code you only need to load that (in each new session, for example).  Within a session you might need to purge the PCell from virtual memory to be able to test new drawing code.  With the above separation of PCell definition and drawing code, you should only need to load the latter from a libInit.il file.

    I hope this helps you.

    Regards,

    Lawrence.

Reply
  • skillUser

    Hi Petya,

    You should only need to load the code with the pcDefinePCell statement if the parameters or their defaults change, otherwise you can just load the 'drawing code', provided that your code is structured something like the following:

    
::::::::::::::::::::::::::::::
:: file to define the PCell ::
::::::::::::::::::::::::::::::
let( (library cell pcellId)
  library="myLibName"
  cell="myCellName"
  unless(ddGetObj(library)
    error("Couldn't open library %L\n" library)
  )

  pcellId = pcDefinePCell(
    list(ddGetObj(library) cell "layout" "maskLayout")

    (
      (length   "10.0")
      (width    "10.0")
    )
    ;; call PCell drawing code
    MYdrawPCell(pcCellView length width)
  ); pcDefinePCell

  dbSave(pcellId)
  dbClose(pcellId)
)

::::::::::::::::::::::::::::::
::  file to draw the PCell  ::
::::::::::::::::::::::::::::::
procedure(MYdrawPCell(cv l w "dtt")
  ;; drawing code goes here
)

    Then each time you change the drawing code you only need to load that (in each new session, for example).  Within a session you might need to purge the PCell from virtual memory to be able to test new drawing code.  With the above separation of PCell definition and drawing code, you should only need to load the latter from a libInit.il file.

    I hope this helps you.

    Regards,

    Lawrence.

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.