Cadence Cerebrus AI Studio can perform hierarchical design closure more efficiently by employing agentic AI features that autonomously handle top-block co-optimization, providing game-changing engineering productivity and turnaround time.
This allows the simultaneous exploration of top and blocks with various actions and policies. Multiple data handoffs are handled with tagging, and all the design changes can be embraced with live updates. AI agents assist the design closure at every stage of hierarchical design, and the Cadence Certus Closure Solution can be used for chip-level timing closure.
Cadence Cerebrus AI Studio can be used for hierarchical design at every stage of the design flow. For the prototype stage, this feature provides a usable top floorplan with reasonable channel estimation and module placements, which can be used for I/O bump/pad planning, packaging simulations, PG bump distribution and supply planning, and PCB planning. Once more mature RTLs are delivered after design flow flush, explorations begin, and winning recipes from the Partition Optimization agent will be taken forward for clock planning and budgeting, and then handed off for block exploration.
Top exploration can also start in parallel with early-ILMs. When prects block results are available after going through Cadence Cerebrus-based optimization, the top can migrate to using prects databases for exploration. The purpose of this exploration is to arrive at predictable PPA convergence for blocks and top, and to determine what should be frozen for subsequent iterations and what can be kept open for further exploration.
Also note that, for convergence-critical blocks that are unable to close in congestion or timing, use bottom-up partitioning with the critical block shape frozen, so that other blocks can adjust to accommodate it. Once the design reaches the pre-final stage, ML model reuse should be applied to transfer the learnings of previous partition optimization exploration regarding block shapes, location, pin placement, etc., to the incoming mature Innovus database. All subsequent stages will run in an “Incremental” mode, and all block/top stage apps will run in “Warm-start’ mode.
The final design netlist goes through a high degree of reuse of all past experiments, frozen partitions, top clock planning, and budgeting, only accommodating minor changes that are incrementally handled. All stage-wise apps run in “Replay” mode, where the smart/mega replay techniques can be used as appropriate.