Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • RTL Foundations36
  • Combinational Design25
  • Sequential Design27
  • FSM & Control27
  • Timing & Clocking39
  • Reset & CDC34
  • Memory & Buses57
  • Advanced RTL28
  • Senior & Interview76
    • Low-Power RTL Hub
    • DFT and Scan Hub
    • Physical Awareness Hub
    • Waveform Debug Hub
    • STA and ECO Hub
    • RTL-to-Implementation Closure
    • DFT-Ready RTL
      • Scan-Ready Coding
      • Test Clocks, Resets, and Modes
      • Memory, JTAG, Compression, and Handoff
    • Capstone: Resilient Streaming Peripheral
    • Principal Design Review
    • Senior RTL Interview Questions & Model Answers
  • Glossary and Notation
Loading lesson

‹DFT-Ready RTL
  1. Topics
  2. RTL Design
  3. Senior & Interview
  4. DFT-Ready RTL
  5. Memory, JTAG, Compression, and Handoff

Part 9 · Senior · Senior

Memory, JTAG, Compression, and Handoff

Connect memory-test wrappers, TAP access, X-control and compression requirements to the RTL integration package.

Why this matters

A single unknown can spread through the response compactor and mask many observable bits. An incomplete handoff leaves memories unmapped and X sources uncontained.

After this lesson you can: write the DFT handoff for memories, JTAG and compression, and list what must be true before it is accepted.

Area

RTL owner supplies

Detailed owner/course

MBIST

Memory inventory, wrapper ports, clocks/resets, repair/status path

DFT MBIST & LBIST

JTAG/boundary scan

Pin mux ownership, TAP/reset connectivity, lifecycle policy

DFT Boundary Scan & JTAG

Compression

X-source inventory, mask/control hooks, domain partition

DFT Compression & Diagnosis

ATPG

Legal test modes, constants, black-box models

DFT ATPG & Patterns

Physical

Clock/domain/hierarchy intent and test ports

DFT Physical Integration

The final handoff maps both sensor SRAMs to memory built-in self-test (MBIST), assigns the external pins to the boundary-scan policy, and documents the analog-status clamp so automatic test pattern generation (ATPG) and compression do not inherit an uncontrolled unknown source.

Diagram: u_tap drives u_sample_mbist, which tests u_sample_sram 256x16, and u_cfg_mbist, which tests u_cfg_sram 64x32. Done/fail return to the TAP on status bits 0 to 1 and 2 to 3. analog_status, clamped to 0, feeds the scan chains, which feed the response compactor.
The handoff in one picture: the TAP reaches each memory through its own MBIST controller and reads done/fail back on its status bits; the analog input is clamped before the scan chains so no unknown reaches the compactor.

Read the left side as memory test and the right side as logic test. Dashed arrows are status coming back.

Memory instance

Test mapping / resource-specific contract

Release artifact

u_sensor/u_sample_sram

u_sample_mbist -> sample wrapper, 256x16; exclusive port ownership, documented read latency and write/read collision rules

Macro model revision, algorithm/clock limits, done/fail mapping to TAP status[0:1]; repair unsupported in this illustrative macro

u_sensor/u_cfg_sram

u_cfg_mbist -> config wrapper, 64x32; separate bus test clock and port ownership; destructive test requires config reload

Own macro model/latency limits, done/fail mapping to TAP status[2:3]; repair unsupported here

Handoff acceptance requires both named instances mapped exactly once, no unresolved memory wrappers, reviewed per-mode clocks/reset assumptions, chain-domain inventory, pin parking expectations and clamp/mask coverage exclusions. Analog clamp=0 intentionally removes that source from scan fault observation; it needs a separate analog test plan. MBIST completion does not authorize functional traffic until reset/configuration initialization and domain readiness finish. Macro fault coverage, insertion, ATPG patterns and physical test timing remain DFT-owned evidence, not inferred from this inventory.

  • Version the memory instance list and map every instance to MBIST/repair policy.

  • Review JTAG access against security lifecycle and production lock requirements.

  • Identify X sources before compression insertion; uncontrolled X values destroy observability.

  • Provide test-mode SDC assumptions and confirm they do not leak into functional modes.

  • Close DFT DRCs or attach owned, expiring waivers.

Interview

Frame DFT readiness as an integration package: scan-friendly state, controllable test clocks and resets, MBIST wrappers, JTAG pin ownership, unknown-value containment, and signed-off handoff artifacts.

Check yourself Why does compression make X-control more important?

A single unknown can spread through the response compactor and mask many observable bits, reducing useful fault coverage.

Remember

  • Map every memory instance exactly once to MBIST and repair policy, and version the instance list.

  • Find X sources before compression insertion; analog clamp = 0 needs a separate analog test plan.

  • MBIST completion does not allow functional traffic until reset, configuration and domain readiness finish.

Keep going

  • Code lab: JTAG tap model

  • Interview: run a mock interview on this topic

Related topics

  • MBIST and LBIST course

  • Boundary Scan and JTAG

  • Compression and diagnosis

Previous

302 / 350

Next: Capstone: Resilient Streaming Peripheral

Up next

Up nextCapstone: Resilient Streaming Peripheral

Sign in to save progress

Practice this lessonReport an error

See also

  • Scan-Ready Coding