Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 1918
  • 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

Can't retain the create->probe option across sch designs in tabs

ssram

I wrote the following code to open the selected instances in layout/schematic in a new tab.

But somehow this doesn't workout well since the create->probe doesn't work well in schematic across the tabs, also it gives the following ERROR. Could someone help me here to fix this?

*Error* _schIsUserEditable: argument #1 should be a string (type template = "t") - nil

;+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

procedure(srOpenLayoutInTab()

techLibName = techGetTechFile(geGetEditCellView())~>libName
myCells = geGetSelSet()

if( myCells then

foreach( cells myCells
cellViewType = cells~>master~>cellViewType
when(
cellViewType == "maskLayout"
if( cells~>isAnyInst then
myLibName = cells~>libName
myCellName = cells~>cellName
myViewName = cells~>viewName
printf("\nOpening the design %A from lib %A in a new tab\n\n" myCellName myLibName)
window = hiOpenWindow(?session hiGetSessionWindow(hiGetCurrentWindow()) ?type "graphics" ?appType hiGetAppType(hiGetCurrentWindow()))
window->sessionWindow=hiGetSessionWindow(hiGetCurrentWindow())
geOpen(
?window window
?lib myLibName
?cell myCellName
?view myViewName
?viewType cellViewType
?mode "r"
)
);if
);when
);foreach

foreach( cells myCells
cellViewType = cells~>cellView~>cellViewType
when(
cellViewType == "schematic"
if( cells~>isAnyInst then
myLibName = cells~>libName
myCellName = cells~>cellName
;myViewName = cells~>viewName
printf("\nOpening the design %A from lib %A in a new tab\n\n" myCellName myLibName)
window = hiOpenWindow(?session hiGetSessionWindow(hiGetCurrentWindow()) ?type "graphics" ?appType hiGetAppType(hiGetCurrentWindow()))
window->sessionWindow=hiGetSessionWindow(hiGetCurrentWindow())
geOpen(
?window window
?lib myLibName
?cell myCellName
?view "schematic"
?viewType cellViewType
?mode "r"
)
);if
);when
);foreach

else
printf("\nNo instances are selected to open \n\n")
);if

);procedure

;+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Thanks

SSR

Parents
  • RiadKaced

    As said, you are opening your design hierarchy in new tabs instead of descending the hierarchy, which will retain the net highlighting among other things. The "CCSschDescendWithUserControls" shared below solves a good problem but has some limitations as far as your issue is concerned, especially when iterating through multiple instances. I have written the following code for you, it's on my git repo, I have tested it on a schematic design however I don't have any layouts to test at the moment. The script is well documented,

    FTTdescend.il

    Cheers,

    Riad.

  • ssram
    in reply to RiadKaced

    Thanks a lot Riad, appreciate your help.

    The schematic descend works fine for me, but the layout portion doesn't seem to work well. I'm not sure if the envSetVal for layout is working well.

    The layout opens in the same tab of the window, it doesn't look like it honors the envSetVal.

    I tried the following in the CIW and i get some warnings.

    +++++++++++++

    envSetVal("layout" "descendCanvasType" 'string "new tab")
    *WARNING* envSetVal: type mismatch for variable 'descendCanvasType'
    in tool[.partition] 'layout'.
    nil

    +++++++++++++

    Thanks

    SSR

  • ssram
    in reply to ssram

    Found the issue... it was the way i was doing the envSetVal for layout. Instead of string, i should be using cyclic as below

    envSetVal("layout" "descendCanvasType" 'cyclic "new tab")

    Now the code works like a charm :-)

    Thanks Riad once again.

Reply
  • ssram
    in reply to ssram

    Found the issue... it was the way i was doing the envSetVal for layout. Instead of string, i should be using cyclic as below

    envSetVal("layout" "descendCanvasType" 'cyclic "new tab")

    Now the code works like a charm :-)

    Thanks Riad once again.

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.