×
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
post
page
×
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
post
page
×
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
post
page
Home / Blog / Accelerating System Architecture Exploration and Implementation

Accelerating System Architecture Exploration and Implementation

by Nandan Nayampally
Toward the integration of Baya FabricStudio™ with Synopsys Platform Architect™

In modern AI systems, performance is increasingly determined not only by how fast processors compute—but by  how efficiently data moves through the system. 

Across the semiconductor industry, this shift is driving renewed focus on system architecture and interconnect design. As workloads scale and heterogeneous compute becomes the norm, architects must evaluate how CPUs, accelerators, memory subsystems, and chiplets interact long before RTL development begins. Understanding system-level data movement early has become essential to delivering predictable performance and hitting product timelines. 

As AI, HPC, and heterogeneous SoC designs grow in complexity, data movement architecture has become as critical as compute. Modern systems rely on a diverse mix of CPUs, accelerators, memory subsystems, and chiplets that generate complex traffic patterns across the system interconnect. Understanding how these components interact—and how traffic flows through the system—has become a key part of early architecture exploration. 

Yet accurately modeling these systems early in the design cycle remains difficult. 

Traditional approaches often force architects to choose between accuracy and productivity. Full-system RTL simulation offers high fidelity but is expensive in engineering effort, simulation time, and compute resources. At the other extreme, architects often rely on simplified models or hand-coded protocol transactors. While faster, these approaches can miss important real-world behaviors and still require significant engineering effort to build and maintain. 

What many systems teams need is a  more effective modeling approach: one that runs fast enough for architecture exploration while accurately capturing the high-level behavior of the interconnect, providing clear guidance for making architectural decisions. Baya Systems and Synopsys are collaborating on the integration of Baya’s rapid NoC simulation capabilities with Synopsys Platform Architect product family. Synopsys Platform Architect for Multi-Die is a SystemC standards based power and performance analysis tool for architecture exploration helping optimize hardware-software partitioning, memory configuration, interconnect and IP selection-configuration. Baya’s FabricStudio platform  enables architects early on to define and automatically generate NoC models that are accurate to the microarchitecture of systems. The integration between these two tools unlocks a powerful capability to evaluate realistic NOC behavior earlier in the system exploration stage.

The Modeling Gap in Modern SoC Architecture

System architects evaluating new designs typically face two imperfect choices. 

Full RTL simulation can provide accurate system behavior but comes with significant tradeoffs: 

  • Long simulation runtimes 
  • High compute and memory requirements 
  • Substantial engineering effort to build models 

Alternatively, teams sometimes construct system models using hand-coded AXI or CHI TLM transactors. While faster, these models often fail to capture realistic IP behavior and key network dynamics such as congestion, buffering, or backpressure. 

As a result, answering fundamental architecture questions early becomes difficult: 

  • Can the interconnect sustain peak AI workload traffic? 
  • Where will congestion emerge in the system? 
  • How do coherency features affect latency and throughput? 
  • Which topology or buffering strategy best supports expected workloads?
The stakes are high. Late discovery of system-level performance issues can have significant technical and financial consequences. The cost of discovering system performance issues late in the design cycle can be significant. Industry surveys show that only about 14% of ASIC and SoC projects achieve first-pass silicon success, meaning most programs require additional design iterations. At the same time, missing a product window can be extremely costly. Analysts estimate that a  six-month delay in silicon can translate into more than $100 million in lost opportunity, particularly when companies miss key design cycles in data-center, networking, or AI infrastructure markets. These realities are driving increased focus on system-level modeling and architecture exploration earlier in the development process. These realities are driving demand for tools that allow architects to analyze data movement and system performance much earlier in the design process. 
Introducing FabricStudio Cycle-Level NoC Simulation into Platform Architect

Baya’s approach introduces cycle-level NoC simulation directly into the system modeling workflow. 

At the core of this capability is Baya’s flit-level NoC simulation engine, which models how packets move through routers, links, and buffers across the network. This allows the model to capture important network behaviors such as: 

  • Congestion hotspots 
  • Traffic interactions across the system
Because the simulator models real protocol features, architects can explore configuration options reflecting realistic system behavior. For example, the model can represent CHI Home Node capabilities such as DMT, DWT, and DCT, along with the ability to system-level cache functionality model various System-Level Cache (SLC) configurations including the number of SLCs, address hashing, cache capacity and associativity..  This enables architects to evaluate how architectural choices influence system performance before implementation begins.  As Onur Mutlu, Professor of Computer Science at ETH Zurich and visiting researcher at Google observed in a recent paper on modern system architecture, moving data efficiently is now one of the fundamental challenges in high-performance computing. The architecture of how data flows through the system is just as important as the compute itself. This was echoed by Mark Papermaster, CTO of AMD in his discussion with  Inside HPC.  In practice, many system performance problems ultimately trace back to the interconnect. 
System Architecture Modeling Workflow

In the integrated workflow, FabricStudio acts as the entry point for defining the NoC architecture, while Platform Architect provides the broader system simulation environment. 

Architects describe the NoC topology using FabricStudio’s Python-based architecture flow. From this configuration, FabricStudio automatically generates the SystemC-based NoC model. 

The generated SystemC model can then be imported into Synopsys Platform Architect for Multi-Die, where it interacts with other system models such as CPUs, generic or IP-specific and highly accurate memory subsystems (like HBM, LPDDR, DDR), Die-2-Die or Chip-2-Chip IP (like UCIe, CXL, PCIe), and accelerators. Architects can simulate workloads and analyze how traffic flows through the network. 

Because the simulator models flit-level behavior, architects can study real NoC characteristics such as bandwidth utilization, latency, and congestion under realistic traffic patterns. 

Seamless Integration Using Industry Standards

Reducing integration overhead is critical for system architects. 

The Baya NoC simulator’s external-facing API supports both C++-based and standard SystemC-based,  and ARM AMBA TLM 2.0 Library interface, supporting both AXI and CHI protocols. Synopsys Platform Architect provides conversion modules between Synopsys SCML2 Fast Timed (FT) and ARM AMBA TLM 2.0 interfaces, enabling the NoC model to integrate with existing system models without custom glue logic. 

This standards-based approach helps ensure flexibility across different system architectures and modeling environments. 

Observability Across the Network

The simulator also provides detailed visibility into NoC behavior. 

Architects can analyze metrics such as: 

  • End-to-end transaction latency
  • Per-router bandwidth utilization
  • Buffer occupancy 
  • Congestion propagation  
These insights help architects identify bottlenecks and evaluate architecture alternatives across the entire network.
NoC Traffic and Congestion Visibility

Fig 1. NoC and traffic visibility 

Such visibility helps architects understand where bandwidth constraints emerge, which routers experience congestion, and how workload patterns influence overall system performance.

Automation Through FabricStudio

FabricStudio simplifies the process of generating and integrating the NoC model. 

Starting from a Python-based configuration, a single command will be able to generate: 

  • SystemC headers
  • Integration scripts
  • Compiled simulation libraries
  • Import files for Platform Architect
This automation removes much of the manual effort required for system modeling and allows architects to focus on architectural exploration.
Looking Ahead

As system complexity grows, the industry is increasingly shifting toward architecture-first design methodologies, where data movement, topology, and traffic behavior are explored before RTL implementation begins. Integrations such as the emerging FabricStudio–Platform Architect workflow aim to give architects a practical way to evaluate interconnect behavior early in the design cycle—reducing risk and helping teams move from architectural concept to silicon with greater confidence. 

by Nandan Nayampally