Backdoor Access

Concept

In hardware and System-on-Chip (SoC) verification, backdoor access is a technique for directly reading from or writing to registers and memory locations in a Design Under Test (DUT) by traversing hierarchical HDL paths, rather than driving transactions over the physical bus. It enables zero-time register access, substantially reducing simulation time and resource consumption, and is used by techniques such as data comparison via backdoor read to expose bugs hidden by the front door access path.

First seen 7/1/2026

Last seen 7/1/2026

Evidence 1 chunks

Wiki v1

WIKI

Definition

In SoC and hardware verification, backdoor access refers to a mechanism by which a testbench reads or writes RTL registers and memory locations directly through their hierarchical HDL paths, bypassing the physical bus interface. The DUT is poked or peeked by name from the testbench environment instead of by issuing protocol-level transactions over the functional bus.

Front Door vs. Back Door Access

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

3 connections

Bug hunting SoC designs to achieve full functional coverage closure ← uses 100% 1e

The paper uses backdoor access for efficient register reading and data comparison.

Data Comparison via Backdoor Read ← uses 100% 1e

Data comparison via backdoor read uses backdoor access to read DUT registers.

RTL Simulation uses → 90% 1e

Backdoor access uses RTL simulation hierarchy to directly access registers.

LINKED ENTITIES

3 links

Bug hunting SoC designs to achieve full functional coverage closure USES Extracted graph relationship

Data Comparison via Backdoor Read USES Extracted graph relationship

RTL Simulation USES Extracted graph relationship

CITATIONS

5 sources

5 citations — click to expand

[1] Backdoor access accesses DUT registers directly in zero time using a hierarchical HDL path, bypassing the physical bus, in contrast to front door access which takes multiple clock cycles over the bus. Bug hunting SoC designs to achieve full functional coverage closure

[2] Writing thousands of registers via the front door is resource-consuming and time-consuming; backdoor access saves simulation time and physical-bus resource utilization. Bug hunting SoC designs to achieve full functional coverage closure

[3] To uncover bugs hidden by the front door access path (such as data bus reversal or mangled memory addresses), the recommended approach is to write via front door, read via back door, and compare the read data against an expected data array maintained by the testbench. Bug hunting SoC designs to achieve full functional coverage closure

[4] Reading back all memories (slaves) after transactions and performing data compares should be done via back door access rather than front door to save simulation time. Bug hunting SoC designs to achieve full functional coverage closure

[5] Outside the verification domain, 'backdoor access' is used in security research contexts (e.g., rowhammer attacks against federated learning servers, backdoored access via pre-installed Android software) with a meaning unrelated to HDL hierarchical register access. Remote Rowhammer Attack using Adversarial Observations on Federated Learning Clients