<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Swupdate on Marcus Folkesson</title>
    <link>https://www.marcusfolkesson.se/tags/swupdate/</link>
    <description>Recent content in Swupdate on Marcus Folkesson</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 May 2024 10:00:34 +0100</lastBuildDate>
    <atom:link href="https://www.marcusfolkesson.se/tags/swupdate/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Versioning with SWUpdate</title>
      <link>https://www.marcusfolkesson.se/blog/versioning-with-swupdate/</link>
      <pubDate>Wed, 15 May 2024 10:00:34 +0100</pubDate>
      <guid>https://www.marcusfolkesson.se/blog/versioning-with-swupdate/</guid>
      <description>Versioning with SWUpdate TLDR; It is now possible to let SWUpdate manage the sw-versions file entirely thanks to the --gen--swversions feature I&#39;ve been working on.&#xA;SWUpdate SWUpdate [1] is a project I&#39;ve been using for a very long time for updating firmware on embedded systems.&#xA;The update service is a critical part of any embedded system, so having a well-tested, flexible, competent and ready-to-use solution is so much worth. Too many times I&#39;ve seen custom made update services that contain bugs, is not flexible enough or using slots for whatever software that could be updated.</description>
    </item>
  </channel>
</rss>
