<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>From Library Portability to Para-rehosting: Natively Executing Microcontroller Software on Commodity Hardware · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2107.12867/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2107.12867/feed.xml" rel="self" type="application/rss+xml" /><item><title>From Library Portability to Para-rehosting: Natively Executing Microcontroller Software on Commodity Hardware — mentioned by AlotOfReading</title><link>https://news.ycombinator.com/item?id=32523558</link><guid isPermaLink="false">urn:hackerpapers:mention:2107.12867:32523558</guid><pubDate>Fri, 19 Aug 2022 17:04:41 GMT</pubDate><description>&lt;p&gt;The direction people are moving towards is re-hosting and directed emulation, where you run the code in an environment where the analysis tools are better and emulate just enough of the platform that the code thinks it&amp;#x27;s executing natively. Some of the published work even looks at the expectations encoded in the source to emulate what it&amp;#x27;s expecting from the &amp;quot;hardware&amp;quot;. Since the HW is fake, testing new configurations is just a config change away. Take a look at [1], [2], [3] for published work. I also have a tool that&amp;#x27;s used in a couple companies able to rehost simpler linux device drivers…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2107.12867/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.PL</category></item></channel></rss>
