<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Reverse engineering &#8211; Purism</title>
	<atom:link href="https://puri.sm/posts/tag/reverse-engineering/feed/" rel="self" type="application/rss+xml" />
	<link>https://puri.sm/</link>
	<description>High-quality computers that protect your freedom and privacy</description>
	<lastBuildDate>Wed, 01 Oct 2025 18:29:47 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.9.28</generator>

<image>
	<url>https://puri.sm/wp-content/uploads/2020/04/cropped-purism-logo-rectangle-1-32x32.png</url>
	<title>Reverse engineering &#8211; Purism</title>
	<link>https://puri.sm/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Wrangling the EC: Adventures in Power Sequencing</title>
		<link>https://puri.sm/posts/wrangling-the-ec-adventures-in-power-sequencing/</link>
		<pubDate>Fri, 28 May 2021 20:55:10 +0000</pubDate>
		<dc:creator><![CDATA[Purism]]></dc:creator>
				<category><![CDATA[Firmware and BIOS]]></category>
		<category><![CDATA[Librem 14]]></category>
		<category><![CDATA[Advanced readers]]></category>
		<category><![CDATA[Chipsets and components]]></category>
		<category><![CDATA[Laptops]]></category>
		<category><![CDATA[Reverse engineering]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=71989</guid>
		<description><![CDATA[<p>As we outlined in a previous post, the Librem 14 is the first Purism laptop to ship with our new, free software Librem-EC firmware for the laptop&#8217;s embedded controller (EC). This was a big undertaking, and as with any effort of this magnitude, issues arise in corner cases that often don&#8217;t show themselves during developmental [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/wrangling-the-ec-adventures-in-power-sequencing/">Wrangling the EC: Adventures in Power Sequencing</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
		</item>
		<item>
		<title>GPS Tuning the Librem 5 Hardware</title>
		<link>https://puri.sm/posts/gps-tuning-the-librem-5-hardware/</link>
		<pubDate>Tue, 15 Sep 2020 08:25:54 +0000</pubDate>
		<dc:creator><![CDATA[Angus Ainslie]]></dc:creator>
				<category><![CDATA[Firmware and BIOS]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Advanced readers]]></category>
		<category><![CDATA[Chipsets and components]]></category>
		<category><![CDATA[Reverse engineering]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=69294</guid>
		<description><![CDATA[<p>Phone Hardware debugging in a duopoly Society is getting pretty used to the idea that the data and applications on phones are completely controlled by large corporations. Purism is working hard to change that with the Librem 5. Because of the market capitalization and duopoly control of the phone OS vendors, the hardware tool vendors [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/gps-tuning-the-librem-5-hardware/">GPS Tuning the Librem 5 Hardware</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
		</item>
		<item>
		<title>Intel FSP reverse engineering: finding the real entry point!</title>
		<link>https://puri.sm/posts/intel-fsp-reverse-engineering-finding-the-real-entry-point/</link>
		<pubDate>Mon, 02 Apr 2018 13:37:27 +0000</pubDate>
		<dc:creator><![CDATA[Purism]]></dc:creator>
				<category><![CDATA[Firmware and BIOS]]></category>
		<category><![CDATA[Advanced readers]]></category>
		<category><![CDATA[Boot and BIOS]]></category>
		<category><![CDATA[Laptops]]></category>
		<category><![CDATA[Newsletter and status updates]]></category>
		<category><![CDATA[Reverse engineering]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=48306</guid>
		<description><![CDATA[<p>2018-05-10 UPDATE: Intel politely asked Purism to remove this document which Intel believes may conflict with a licensing term. Since this post was informational only and has no impact on the future goals of Purism, we have complied. If you would like the repository link of the Intel FSP provided from Intel, please visit their [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/intel-fsp-reverse-engineering-finding-the-real-entry-point/">Intel FSP reverse engineering: finding the real entry point!</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
		</item>
		<item>
		<title>A Primer Guide to Reverse Engineering</title>
		<link>https://puri.sm/posts/primer-to-reverse-engineering/</link>
		<pubDate>Fri, 17 Nov 2017 20:00:15 +0000</pubDate>
		<dc:creator><![CDATA[Purism]]></dc:creator>
				<category><![CDATA[Firmware and BIOS]]></category>
		<category><![CDATA[Advanced readers]]></category>
		<category><![CDATA[Laptops]]></category>
		<category><![CDATA[Newsletter and status updates]]></category>
		<category><![CDATA[Reverse engineering]]></category>
		<category><![CDATA[Software freedom]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=43843</guid>
		<description><![CDATA[<p>Over the years, many people asked me to teach them what I do, or to explain to them how to reverse engineer assembly code in general. Sometimes I hear the infamous &#8220;How hard can it be?&#8221; catchphrase. Last week someone I was discussing with thought that the assembly language is just like a regular programming [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/primer-to-reverse-engineering/">A Primer Guide to Reverse Engineering</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
		</item>
		<item>
		<title>Reverse-engineering the Intel Management Engine&#8217;s ROMP module</title>
		<link>https://puri.sm/posts/reverse-engineering-the-intel-management-engine-romp-module/</link>
		<pubDate>Wed, 10 May 2017 16:12:30 +0000</pubDate>
		<dc:creator><![CDATA[Purism]]></dc:creator>
				<category><![CDATA[Additional Press Information]]></category>
		<category><![CDATA[Firmware and BIOS]]></category>
		<category><![CDATA[Advanced readers]]></category>
		<category><![CDATA[Newsletter and status updates]]></category>
		<category><![CDATA[Reverse engineering]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Software freedom]]></category>

		<guid isPermaLink="false">https://puri.sm/?p=18666</guid>
		<description><![CDATA[<p>Last month, while I was waiting for hardware to arrive and undergo troubleshooting, I had some spare time to begin some Intel ME reverse engineering work. First, I need to give some shout out to Igor Skochinsky, a Hex-Rays developer, who had been working on reverse engineering the Intel ME for a while, and who [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://puri.sm/posts/reverse-engineering-the-intel-management-engine-romp-module/">Reverse-engineering the Intel Management Engine&#8217;s ROMP module</a> appeared first on <a rel="nofollow" href="https://puri.sm/">Purism</a>.</p>
]]></description>
		</item>
	</channel>
</rss>
