DenseChip

SoC Integration · All levels

AXI/ACE Contracts: Design Space

Design Space for AXI/ACE Contracts.

Design space exploration

For AXI/ACE Contracts, integration options trade schedule velocity, silicon risk, and closure confidence.

Option A — conservative

  • Conservative contracts: helps predictability

  • Risk: slower early iteration

  • Validate with: first-pass integration

Option B — balanced

  • Balanced governance: helps reasonable velocity

  • Risk: needs discipline

  • Validate with: mature program

Option C — aggressive

  • Aggressive shortcuts: helps short-term speed

  • Risk: late escapes

  • Validate with: last-resort crunch

Option D — architectural

  • Architectural rework: helps structural fix

  • Risk: schedule impact

  • Validate with: systemic issues

diagram
DESIGN SPACE — AXI/ACE Contracts
risk <-> velocity <-> closure confidence

Design pitfalls

  • Unowned risks

  • Fixes without manifest-locked regression

Tradeoff curve

diagram
BEFORE / AFTER FIX — AXI/ACE Contracts

risk index
 0 |                    --- target
40 |    ● regression
65 |         ● before fix
20 |              ● after fix
    +-------------------------------> iteration
Always verify collateral, regression suite, and owner signoff.

SoC deep dive

Fabric correctness and contention behavior must be proven together.

Concept diagram

diagram
FABRIC FLOW
masters -> routers/VCs -> slaves + memory

Metric graph

diagram
LATENCY TAIL
p50 ███
p95 ██████
p99 ██████████

Reports and artifacts

  • NoC contention heatmap

  • ordering violation report

  • QoS fairness summary

  • protocol trace

Mini case study

Bandwidth looked fine at average load, but p99 tail violated SLA due to arbitration starvation.

Debug branches

  • Isolate traffic class

  • Check ordering assumptions

  • Audit arbitration policy

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

  • State baseline manifest and owner with every closure metric.

  • Run cross-domain regression after every top-level fix.

Common pitfalls

  • Comparing results across different manifests.

  • Unowned issues slipping through review cycles.

  • Waiving risks without expiry and validation plan.

Principal SoC review addendum

AXI/ACE integration depends on preserving ID, ordering, coherency attributes, and sideband semantics through bridges and fabric adapters.

Metric: ordering violations, protocol error rate, outstanding depth stability

Practice this lesson