<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pranav Senthilkumar</title>
    <description>The latest articles on DEV Community by Pranav Senthilkumar (@pranav-s79).</description>
    <link>https://dev.to/pranav-s79</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4026440%2F6430b21f-c666-4a29-9f9b-9f51a7e8b282.png</url>
      <title>DEV Community: Pranav Senthilkumar</title>
      <link>https://dev.to/pranav-s79</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pranav-s79"/>
    <language>en</language>
    <item>
      <title>I built Regdrift, a CLI and GitHub Action for detecting breaking CMSIS-SVD changes</title>
      <dc:creator>Pranav Senthilkumar</dc:creator>
      <pubDate>Sun, 12 Jul 2026 21:21:02 +0000</pubDate>
      <link>https://dev.to/pranav-s79/i-built-regdrift-a-cli-and-github-action-for-detecting-breaking-cmsis-svd-changes-51j3</link>
      <guid>https://dev.to/pranav-s79/i-built-regdrift-a-cli-and-github-action-for-detecting-breaking-cmsis-svd-changes-51j3</guid>
      <description>&lt;p&gt;Hi guys, I've been working on Regdrift, my first open-source project. It's a CLI and GitHub Action that compares two CMSIS-SVD files to check whether there are any register-map changes that could affect firmware functionality.&lt;/p&gt;

&lt;p&gt;It catches changes such as moved registers, interrupt renumbering, access changes, and altered read/write behavior. It then classifies those changes as &lt;code&gt;BREAKING&lt;/code&gt;, &lt;code&gt;WARNING&lt;/code&gt;, or &lt;code&gt;SAFE&lt;/code&gt; so the tool can act as a CI gate.&lt;/p&gt;

&lt;p&gt;I'm looking for feedback from people who maintain SVDs, HALs, PACs, SDKs, or firmware repositories. If possible, I'd like to test it against real old/new SVD pairs and learn where the classifications produce false positives, miss important changes, or are unclear.&lt;/p&gt;

&lt;p&gt;For people who work frequently with CMSIS-SVD files: which types of register-map changes are most detrimental to firmware or cause the most difficult code-related problems?&lt;/p&gt;

&lt;h2&gt;
  
  
  Resources
&lt;/h2&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Pranav-s79/regdrift" rel="noopener noreferrer"&gt;https://github.com/Pranav-s79/regdrift&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Install
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install &lt;/span&gt;regdrift
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Usage
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;regdrift check old.svd new.svd
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



</description>
      <category>showdev</category>
      <category>python</category>
      <category>devtool</category>
      <category>github</category>
    </item>
  </channel>
</rss>
