Silicon Bring-up · All levels

ARM SWD and Debug Access Port: Debug Playbook

Debug Playbook for ARM SWD and Debug Access Port.

Debug playbook

Debug Playbook for ARM SWD and Debug Access Port is anchored on DAP attach success rate, AP transaction error rate, and turnaround time for first memory/register visibility after reset.. Convert observed behavior into mechanism-backed and owner-bound actions.

Freeze setup metadata and preserve first-failure state.
Locate first persistent boundary where behavior diverges.
Classify mechanism: dependency, margin, protocol, software, or silicon.
Apply one focused reproducer and one bounded fix.
Re-run replay, corner, and soak confidence matrix.

Review memo template

diagram

BRING-UP REVIEW MEMO - Debug Interfaces & Observability / ARM SWD and Debug Access Port

1. Symptom
   - Failing metric: DAP attach success rate, AP transaction error rate, and turnaround time for first memory/register visibility after reset.
   - Trigger context: <board/firmware/corner/test window>
   - First failing boundary: <power/reset/clock/interface/firmware>

2. Mechanism hypothesis
   - Candidate mechanism: Serial Wire Debug (SWD) compresses debug control into SWCLK/SWDIO while retaining access to the ARM Debug Access Port hierarchy, where a Debug Port fronts one or more Access Ports for memory and core register operations. Bring-up depends on sequencing: power domains, debug authentication state, and reset topology must allow the debugger to enumerate the target, select the right AP, and execute reliable reads/writes without sticky faults. Engineers commonly triage WAIT/FAULT responses, stale CSW/TAR settings, and security lock states that silently block debug even when electrical connectivity is healthy. A disciplined SWD workflow captures attach transcripts, reset-mode variations, and register snapshots at each milestone so failures can be classified quickly as tooling, access-policy, clocking, or target-state issues.
   - Competing hypotheses: setup, dependency, margin, software path, silicon defect
   - Missing evidence: <trace/scope/register/report>

3. Proposed action
   - Smallest reversible change: <setup/script/config/firmware>
   - Expected movement: <repro rate/latency/pass trend>
   - Regression risk: stability, safety, release timeline, ownership handoff

4. Signoff
   - Required artifact: SWD/DAP access playbook with attach sequence traces, AP map validation, sticky-fault recovery steps, and secure-debug state checklist.
   - Required owners: silicon bring-up owner, firmware boot owner, security architecture owner, debug tools owner
   - Final decision: ship, bounded rollout, rollback, respin escalation

Silicon bring-up deep dive

Debug interfaces are useful only when access paths are trusted, minimally intrusive, and synchronized to failure context.

Concept diagram

diagram

DEBUG ACCESS STACK

physical probes -> debug transport -> trace/scan capture -> correlated analysis

Metric graph

diagram

OBSERVABILITY MATURITY

access failures          ████
partial captures         █████
actionable captures      ███████

Metrics and artifacts to collect

JTAG/SWD access success rate
trace trigger hit coverage
scan dump decode turnaround time
observability gap backlog

Mini case study

A misdiagnosed silicon issue was cleared after TAP chain validation revealed a board-level debug domain assumption error.

Debug branches

Validate access-layer prerequisites before deep protocol decode.
Correlate trace timestamps with software checkpoints.
Treat missing evidence as an observability gap, not closure.

Senior review question

Ask: what is the first failing boundary, which artifact proves it, and who owns bounded closure?

Key takeaways

Tie every bring-up claim to one reproducible setup state and one proving artifact.
Prefer bounded fixes with clear owner and rollback trigger over broad multi-variable edits.

Common pitfalls

Running parallel uncontrolled experiments and losing causality.
Declaring closure without replaying across representative corners.
Escalating severity before bench/setup hypotheses are disproven.

Debug ladder

Sequence: reproduce -> classify -> isolate -> instrument -> bounded fix -> replay.

Avoid parallel broad edits before first root-cause class is proven.

Practice this lesson