--- title: "Debug, visualize and test embedded C/C++ through instrumentation" url: https://daily.dev/posts/debug-visualize-and-test-embedded-c-c-through-instrumentation-gmnfdktnt source_url: https://www.embeddedrelated.com/showarticle/1781.php type: article source: "EmbeddedRelated" published: 2026-05-31T07:48:34.880Z updated: 2026-05-31T09:23:31.313Z tags: ["embedded"] reading_time: 10 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Debug, visualize and test embedded C/C++ through instrumentation **[EmbeddedRelated](https://daily.dev/sources/embeddedrelated)** · 10 min read · 0 upvotes · 0 comments ## Summary Instrumentation-based debugging offers an alternative to classical JTAG/SWD probes for embedded firmware. The Scrutiny Debugger framework — an open-source embedded library plus server and clients — lets you pipe data through existing peripherals (UART, CAN, USB CDC) to get real-time variable monitoring, trigger-based datalogs synchronized with firmware tasks, and Python-driven Hardware-In-the-Loop (HIL) testing. Key techniques covered include mocking IOs, exposing hardware registers via linker scripts, synchronizing firmware-triggered graphs with oscilloscopes via GPIO callbacks, and piggybacking custom commands over the Scrutiny protocol. The Python SDK enables scripted access to any firmware variable by its debug-symbol path, making automated testing feasible without a debug probe. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#embedded](https://daily.dev/tags/embedded) [View this post on daily.dev](https://daily.dev/posts/debug-visualize-and-test-embedded-c-c-through-instrumentation-gmnfdktnt)