<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Openocd on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/openocd/</link>
    <description>Recent content in Openocd on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/openocd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted JTAG/SWD Remote Debug Servers: OpenOCD vs pyOCD vs probe-rs</title>
      <link>https://www.pistack.xyz/posts/2026-06-07-self-hosted-jtag-swd-remote-debug-servers-openocd-pyocd-probe-rs/</link>
      <pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-07-self-hosted-jtag-swd-remote-debug-servers-openocd-pyocd-probe-rs/</guid>
      <description>&lt;p&gt;Debugging embedded systems has traditionally meant connecting a hardware debug probe directly to your development machine via USB. But as embedded development teams grow and CI/CD pipelines extend to hardware-in-the-loop testing, the need for remote, network-accessible debug servers becomes critical. Three major open-source projects — &lt;strong&gt;OpenOCD&lt;/strong&gt;, &lt;strong&gt;pyOCD&lt;/strong&gt;, and &lt;strong&gt;probe-rs&lt;/strong&gt; — each provide GDB server functionality over TCP, enabling remote debugging workflows where the debug probe is physically connected to one machine while developers connect from anywhere on the network.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
