FilabBack
BLOG.0035 MIN READ

28% Area Reduction on an Encryption Module — Without Touching Timing

LOGIC AREA28%AREA REDUCTION
DELIVERY TIME99%+CYCLE TIME COMPRESSED
EQUIVALENCE100%FUNCTIONAL EQUIVALENCE
01Customer

Our customer is a semiconductor company building security-sensitive products across industrial, automotive, and consumer electronics markets. Their SoC designs embed encryption modules at multiple points in the chip — protecting data pipelines and securing communication interfaces that their end customers depend on.

They came to FiLabs with a mature, proven design — not a prototype. The encryption module had already taped out and was in active production. What they wanted was straightforward to state but hard to deliver: reduce the area footprint meaningfully, without touching timing, and without a weeks-long re-spin cycle.

With a growing queue of derivative SKUs and customer-specific variants, every week spent re-iterating a single module was a week their roadmap  move. Speed and accuracy weren't nice-to-haves. They were the constraint.

02The Challenge

Same Spec. Tighter Silicon.

CONSTRAINT

Functional spec unchanged — timing constraints fully preserved

TARGET

Area reduction target: as aggressive as possible within those bounds

TIMELINE

Delivery timeline: a fraction of the traditional flow

“The traditional path — rewrite RTL, tune synthesis, run ECO iterations — takes 4 to 5 weeks. And there's no guarantee you've found the global optimum.”

Manual RTL optimization is inherently constrained by how many variants an engineer can reasonably explore in a given time window. Synthesis iteration averages 3–5 rounds, each taking 1–2 weeks. Most of that time is spent waiting — not deciding.

03How FiLabs Approached It

A Coordinated Agent Pipeline — Not a Tool

FiLabs deployed its Spec-to-RTL Agent system, running the full flow from specification parsing to verified, synthesis-ready RTL delivery. Each agent owns a distinct stage and shares a persistent representation of intent, constrign state.

AGENT PIPELINE — SPEC-TO-RTL
Stage 01

Spec & Architecture Agent

Micro-architecture + interface definition

Stage 02

RTL Generation Agent

Synthesizable SystemVerilog

Stage 03

Verification Agent

Formal equivalence verification report

Stage 04

Design-Space Exploration Agent

Area, timing & performance multi-objective optimization

04Technical Highlights

Intent-Level Parsing. Thousands of Variants. Zero Regression.

01

The Spec Agent parsed the original specification at intent level — identifying redundant logic paths and conservative area margins baked into the hand-written RTL

02

The DSE Agent explored thousands of design variants in parallel under synthesis constraints, targeting minimum area while treating timing correctness as a hard boundary

03

Every generated RTL candidate was subjected to formal equivalence checking against the original design — ensuring zero functional regression

05Results

The Numbers

MetricFiLabs OutputOriginal DesignOutcome
Logic Area (std. cells)↓ 28%Baseline✓ Achieved
Timing (Fmax)edBaseline✓ Achieved
Functional Equivalence100% verified✓ No Regression
Delivery Time0.1 Days4–5 Weeks↓ 99%+
Engineer InvolvementReview & sign-offFull manual flow✓ Efficiency Leap
scroll

28% area reduction. Zero timing compromise. Delivery in 0.1 days — down from 4–5 weeks. Functional equivalence formally verified.

06Why It Matters

28% area is not a small number.

At 22nm and 28nm — the dominant nodes for industrial, automotive, and consumer electronics — area maps directly to per-die cost. This module is typically instantiated multiple times across an SoC, meaning the area savings compound across the full chip. At production volumes, this translates into millions of dollars in cumulative cost reduction.

Smaller area also means lower dynamic power, which is particularly valuable in power-constrained product categories.

Why is traditional design so slow here?

RTL optimization is a high-dimensional search problem. Engineers navigate it with experience and heuristics — not exhaustive experation is slow, and most of a project's calendar time is consumed by waiting cycles between tool runs, not actual decision-making.

FiLabs runs thousands of design variants in a single pass, compressing what used to be weeks of back-and-forth into a fraction of a working day. The bottleneck shifts from iteration speed to engineer review — which is exactly where expert judgment belongs.

See What's Possible on Your Design.

From spec to verified, synthesis-ready RTL — in a fraction of the traditional timeline.