<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Edge Systems Lab on Prashant Divate | Edge Systems Lab</title><link>https://prashantdivate.github.io/</link><description>Recent content in Edge Systems Lab on Prashant Divate | Edge Systems Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 19 Sep 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://prashantdivate.github.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing Soul Room: An Open-Source Edge Fleet Platform for Linux Devices</title><link>https://prashantdivate.github.io/posts/soul-room-edge-platform/</link><pubDate>Sat, 19 Sep 2026 10:00:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/soul-room-edge-platform/</guid><description>&lt;p&gt;Project repository: &lt;a href="https://github.com/prashantdivate/soul-room-edge-platform"&gt;Soul Room Edge Platform&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="a-calm-room-for-every-connected-device"&gt;A Calm Room for Every Connected Device&lt;/h2&gt;&#10;&lt;p&gt;Today I am opening &lt;strong&gt;Soul Room&lt;/strong&gt; to the community: an open-source edge fleet platform for teams that build and operate Linux devices outside the data center.&lt;/p&gt;</description></item><item><title>OP-TEE from Zero: Part 1</title><link>https://prashantdivate.github.io/posts/op-tee-from-zero-part-1/</link><pubDate>Sat, 12 Sep 2026 00:03:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/op-tee-from-zero-part-1/</guid><description>&lt;p&gt;Originally published on Medium: &lt;a href="https://medium.com/@prashant-divate/op-tee-from-zero-part-1-1e7d5fe7b3be"&gt;OP-TEE from Zero: Part 1&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Understanding the Basic Architecture&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Summary&lt;/strong&gt; OP-TEE is a protected mini operating system. Your normal Linux application stays in Linux and asks a small Trusted Application (TA) in OP-TEE to perform security-sensitive work.&lt;/p&gt;</description></item><item><title>Remotely Accessing Wayland-based Applications using RDP client in Yocto Image</title><link>https://prashantdivate.github.io/posts/remotely-accessing-wayland-rdp-yocto/</link><pubDate>Sat, 12 Sep 2026 00:02:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/remotely-accessing-wayland-rdp-yocto/</guid><description>&lt;p&gt;Originally published on Medium: &lt;a href="https://medium.com/@prashant-divate/remotely-accessing-wayland-based-applications-using-rdp-client-in-yocto-image-55f38b67e0aa"&gt;Remotely Accessing Wayland-based Applications using RDP client in Yocto Image&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;Get more detailed information of this topic on the &lt;a href="https://thepenguintech.com/"&gt;official website&lt;/a&gt; with working demo.&lt;/p&gt;&#10;&lt;p&gt;Remote access to graphical applications running on embedded systems can be a valuable tool for developers and administrators. In this article, we&amp;rsquo;ll explore how to remotely access Wayland applications in a Yocto image using RDP (Remote Desktop Protocol). This method leverages the Wayland display server, specifically Weston, and the FreeRDP library to achieve remote access.&lt;/p&gt;</description></item><item><title>Scaling IoT fleets: Secure Reverse SSH into Yocto for Automated Field Deployment</title><link>https://prashantdivate.github.io/posts/scaling-iot-fleets-secure-reverse-ssh-yocto/</link><pubDate>Sat, 12 Sep 2026 00:01:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/scaling-iot-fleets-secure-reverse-ssh-yocto/</guid><description>&lt;p&gt;Originally published on Medium: &lt;a href="https://medium.com/@prashant-divate/scaling-iot-fleets-secure-reverse-ssh-into-yocto-for-automated-field-deployment-df27d54be7f3"&gt;Scaling IoT fleets: Secure Reverse SSH into Yocto for Automated Field Deployment&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;&#10;&lt;p&gt;Managing and remotely accessing large-scale IoT deployments is one of the biggest operational challenges in embedded Linux systems. Devices are often deployed behind NATs, firewalls, or cellular networks, making direct SSH access difficult and insecure.&lt;/p&gt;</description></item><item><title>Designing an update that knows when to stop</title><link>https://prashantdivate.github.io/posts/update-state-machine/</link><pubDate>Fri, 11 Sep 2026 09:00:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/update-state-machine/</guid><description>&lt;p&gt;An update is more than a download followed by a reboot. It changes a running system while depending on storage, power, network access, and the assumptions made by the previous release.&lt;/p&gt;</description></item><item><title>Debugging containers without losing the evidence</title><link>https://prashantdivate.github.io/posts/container-debugging/</link><pubDate>Wed, 09 Sep 2026 09:00:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/container-debugging/</guid><description>&lt;p&gt;The temptation is familiar: a container stops responding, so restart the stack and see whether the problem disappears. That may restore service, but it can also make the original failure harder to understand.&lt;/p&gt;</description></item><item><title>A small map of the embedded Linux stack</title><link>https://prashantdivate.github.io/posts/embedded-linux-map/</link><pubDate>Tue, 08 Sep 2026 09:00:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/embedded-linux-map/</guid><description>&lt;p&gt;An embedded Linux product can look like a single device from the outside. Inside, it is a series of interfaces between layers that have different responsibilities.&lt;/p&gt;&#10;&lt;p&gt;The exact boot sequence is platform-specific. The following picture is a mental model, not a board-specific boot guide.&lt;/p&gt;</description></item><item><title>Make the build explain itself</title><link>https://prashantdivate.github.io/posts/build-context/</link><pubDate>Sun, 06 Sep 2026 09:00:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/build-context/</guid><description>&lt;p&gt;When a build behaves differently from the previous one, the most useful question is often not &amp;ldquo;what command did you run?&amp;rdquo; It is &amp;ldquo;what exact inputs did that command see?&amp;rdquo;&lt;/p&gt;</description></item><item><title>Security starts before the application</title><link>https://prashantdivate.github.io/posts/security-boundaries/</link><pubDate>Sat, 05 Sep 2026 09:00:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/security-boundaries/</guid><description>&lt;p&gt;Security features are easier to reason about when the question comes before the mechanism.&lt;/p&gt;&#10;&lt;p&gt;&amp;ldquo;Can I trust the software that booted?&amp;rdquo; is different from &amp;ldquo;which component may read a credential?&amp;rdquo; Both matter, but answering one does not automatically answer the other.&lt;/p&gt;</description></item><item><title>Hello, Edge Systems Lab. A place for useful ideas.</title><link>https://prashantdivate.github.io/posts/hello-edge-systems-lab/</link><pubDate>Tue, 01 Sep 2026 09:00:00 +0530</pubDate><guid>https://prashantdivate.github.io/posts/hello-edge-systems-lab/</guid><description>&lt;p&gt;This blog is a place for ideas that deserve more than a chat message and less than a textbook. The website is intentionally simple to maintain: content lives in Markdown files, layout lives in Hugo templates, and visual styling lives in one stylesheet.&lt;/p&gt;</description></item><item><title>An engineer. Always building.</title><link>https://prashantdivate.github.io/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://prashantdivate.github.io/about/</guid><description>&lt;h2 id="the-work-behind-the-interface"&gt;The work behind the interface&lt;/h2&gt;&#10;&lt;p&gt;I am Prashant Divate, an embedded Linux engineer with 7+ years of experience across Yocto distro engineering, BSP integration, platform bring-up, secure updates, and production release workflows. My day-to-day thinking usually sits around Yocto, Linux services, OTA, secure boot, containers, board integration, and the automation that makes field work less painful.&lt;/p&gt;</description></item><item><title>Embedded Linux services</title><link>https://prashantdivate.github.io/services/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://prashantdivate.github.io/services/</guid><description/></item><item><title>Find a blog.</title><link>https://prashantdivate.github.io/search/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://prashantdivate.github.io/search/</guid><description/></item><item><title>The archive</title><link>https://prashantdivate.github.io/archive/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://prashantdivate.github.io/archive/</guid><description/></item></channel></rss>