SiliconScapesArchitecture · RTL · Prototype
Work / Custom IP

Three custom IP blocks for a low-power AR SoC: hardware logging, mailbox synchronization and event generation

Architectural specifications for three infrastructure IP blocks, RTL and verification for two of them, oversight of the third, and integration guidance to the chip team.

ClientAR/XR headset OEM
Stages
  • Architect
  • Implement
Tools
  • SystemVerilog
  • APB
  • ATB
  • Synopsys VCS
  • Verilog DPI
  • CDC

The challenge

A multi-core SoC with several DSP architectures needed infrastructure blocks that the application teams could not live without: a way to log and trace from every core without stealing DSP cycles, a way for cores to synchronize and signal each other, and a way to trigger events between subsystems. Each block spanned multiple clock domains.

What we owned

Hardware logging accelerator. A hardware path that lets every core log and trace without spending DSP cycles: cores hand messages to hardware, which stamps, packetizes, buffers and drains them to memory under per-channel policies, and takes a system-wide snapshot of trace history when any core flags a critical condition.

Mailbox and synchronization block. Hardware mailboxes with atomic operations and interrupt generation for synchronizing cores across several clock domains.

Event-generation block. A companion block for triggering between subsystems, verified alongside the mailbox in a hardware/software co-simulation framework.

Specification and integration. Architectural specifications for all three. RTL and verification for two, with CDC mitigation designed in; oversight of the third. Detailed documentation and guidance to the integration team on instancing and interconnecting the blocks in the full-chip design.

Outcome

Three infrastructure blocks in the chip, with a logging path that costs the DSPs almost nothing and a debug capability the software teams adopted.