<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Firmware on Binary Ruins</title>
    <link>/tags/firmware/</link>
    <description>Recent content in Firmware on Binary Ruins</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright 2026, Ishmael42</copyright>
    <lastBuildDate>Fri, 03 Oct 2025 19:26:37 +0530</lastBuildDate>
    <atom:link href="/tags/firmware/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reversing ARM Firmware</title>
      <link>/posts/reversing-arm-firmware/</link>
      <pubDate>Fri, 03 Oct 2025 19:26:37 +0530</pubDate>
      <guid>/posts/reversing-arm-firmware/</guid>
      <description>&lt;p&gt;Reversing a raw firmware dump is very different from reversing an ELF executable or a PE image. There are no sections, no symbols, and often no clear format - just raw bytes.&lt;/p&gt;&#xA;&lt;p&gt;In this post, I’ll walk through the process of reversing a simple ARM Cortex-M3 (ARMv7-M) firmware image using Ghidra, mapping memory regions, identifying initialization routines, and making sense of global variables.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
