<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hardware-Verification on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hardware-verification/</link>
    <description>Recent content in Hardware-Verification on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 07 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hardware-verification/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>cocotb vs VUnit vs UVM in 2026: Picking a Hardware Verification Framework</title>
      <link>https://www.pistack.xyz/posts/2026-11-07-cocotb-vs-vunit-vs-uvm-hardware-verification-frameworks/</link>
      <pubDate>Sat, 07 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-07-cocotb-vs-vunit-vs-uvm-hardware-verification-frameworks/</guid>
      <description>&lt;p&gt;Half the engineering effort on a modern chip goes into proving it works. Verification outnumbers design three to one at most fabs, and the framework you pick decides whether that effort is spent writing tests or fighting testbench infrastructure.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
