• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. select block view in ocean script

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 14916
  • 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

select block view in ocean script

DavidLou
DavidLou over 7 years ago

hello exports,

think I have behavior models developed for my design. then I want to swap one block/cell at a time by real transistor level block/cell with all rest behavioral models. How can I pick such transistor/behavioral view in ocean script so that I can run these tests in a batch?

I know I can use Hierarchy Editor to create many config to use different views, but that could be very messy once I have so many configs. 

thanks a lot,

David

  • Cancel
  • DavidLou
    DavidLou over 7 years ago

    just to clarify what I'm looking for. I'd like to have the equivalent SKILL/OCEAN script to define what Hierarchy Editor gui does.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to DavidLou

    This could be done with the hdb APIs if you really want to do it with an OCEAN script. It could also be done with CONFIG view variables in ADE XL (and probably simpler in Assembler if you then want to create a simple script to batch run the simulations).

    The hdb APIs would involve you using:

    hdbOpen - to open the config
    hdbSetObjBindRule - to change the binding rule for a cell
    hdbSave
    hdbClose

    This could also be done by having a config and then using CONFIG view variables (use right mouse button menu over the global variables in ADE XL or Assembler to add the variable) - then you could have one variable for each cell you wish to switch, and potentially arrange all the combinations via corners (say).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 7 years ago in reply to Andrew Beckett

    thanks Andrew, 

    I assume hdb APIs would physically require a config existing ahead and the API would physically change the file after each run, right? anyway, I'll try that out.

    thanks,

    David

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to DavidLou
    DavidLou said:
    I assume hdb APIs would physically require a config existing ahead and the API would physically change the file after each run, right?

    Hi David,

    Not necessarily. You can create a config from scratch using hdbOpen but you'd also need to tell it the top level cellView and the global switch and stop lists (via the appropriate APIs). It's not that difficult though.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    hi Andrew, 

    a following up question regarding this (sorry to resume an old thread here), I can see the expand.cfg config file is pure text based configuration, so can we just put those config text or something similar into Ocean script so that the Ocean script is self-sustaining w/o creating a physical config view? 

    thanks,

    David

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to DavidLou

    Hi David,

    There's no support for creating the config view from a textual representation of the expand.cfg contents. Yes, it's text and yes, it's fairly intuitive, but it's not documented and so may change without any notice. Therefore you should only ever create the config view with the SKILL API or using the hierarchy editor.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information