Probe Debugging

Read the shared embedded contract and keep source/build, device and physical evidence separate.

Read probe session boundaries. Confirm MCU/core, board/probe revision, target reference voltage, SWD/JTAG wiring, probe serial, server/runner version and the exact ELF/build. Begin with offline ELF inspection.

Inspect the existing launch config or runner instead of guessing an OpenOCD board file. Binding a debug server to loopback and selecting a probe explicitly avoids attaching to the wrong board. target remote/attach, reset, breakpoint and register writes can halt or change the target; stop/disable actuators with the target owner before that session. A debugger connection is not read-only.

Use named hypothesis checks: PC/backtrace and threads; disassembly at the fault; registers and stack bounds; watchpoint for a suspected overwrite. Optimized code can inline or eliminate variables; retain the failing binary before trying a separate debug build. Do not assume stepping reproduces race timing.