<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Embedded on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/embedded/</link>
		<description>Recent content in Embedded on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/embedded/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Rust in Orbit: Memory Safety for Microcontrollers and Satellites</title>
				<link>https://dplabs.tech/blog/rust-memory-safety-microcontrollers-satellites/</link>
				<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/rust-memory-safety-microcontrollers-satellites/</guid>
				<description>&lt;p&gt;Once a satellite is launched, nobody can open it up and fix it. Whatever firmware is on board when it leaves the launch pad is what it will run until an uplink patch arrives, and an uplink patch is itself a piece of attacker-reachable input arriving over a radio link. If the code that receives that input has a memory bug, the spacecraft can be crashed, bricked, or taken over by whoever finds the bug first.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
