Skip to content
iharhlPublic

About

Parser library and viewer app for IntelHex and binary files written in Rust

Topics

Resources

Stars

9 stars

Watchers

0 watching

Forks

Repository files navigation

Hexalyzer

Hexalyzer is an app for inspecting and modifying firmware files and binary data. It opens Intel HEX files and shows any other file as raw binary, which makes it well suited to embedded firmware analysis.

The project consists of:

  • Hexalyzer, a desktop GUI app for viewing and editing HEX and binary files.
  • intelhexlib, a standalone Rust library for reading, editing and writing Intel HEX and binary data.
  • hexcli, a command-line tool built on the library for inspecting, relocating, converting and merging files.

Hexalyzer app preview

Installation

Prebuilt installers and the hexcli tool are attached to each release:

Platform App CLI
macOS (Apple Silicon) Hexalyzer_<version>_aarch64.dmg hexcli_<version>_macos-arm64.tar.gz
Windows (x64) hexalyzer_<version>_x64-setup.exe hexcli_<version>_windows-x86_64.zip
Linux (x64) hexalyzer_<version>_amd64.deb or hexalyzer_<version>_x86_64.AppImage hexcli_<version>_linux-x86_64.tar.gz

Binaries for Intel Macs are not prebuilt so you have to build them from source (see below).

Security warnings

Your browser or operating system may warn that Hexalyzer is unrecognized or could not be verified. This is expected: the warnings are about the files not being code-signed and not about anything found in them. Signing needs a paid Apple Developer ID on macOS and a code-signing certificate on Windows, which the project does not have yet.

Hexalyzer is open source, and every release file is built by GitHub Actions straight from the tagged source in this repository (see the release workflow). The build logs of each release are public on the Actions page.

To get past the warnings:

  • Browser: Chrome may block a new release file as "not commonly downloaded". Open the downloads list (chrome://downloads) and click "Download dangerous file".
  • macOS: if macOS says it could not verify that Hexalyzer is free of malware, click "Done", then go to System Settings → Privacy & Security and click "Open Anyway". This might happen twice: once when opening the .dmg, and once when first launching the installed app.
  • Windows: if SmartScreen shows "Windows protected your PC", click "More info" → "Run anyway".

I may add signing in a future release: an Apple Developer ID with notarization on macOS, and a signing service such as Azure Trusted Signing or SignPath (free for open-source projects) on Windows. That would remove most of these warnings.

Notes for Linux

The file dialogs go through the desktop portal (xdg-desktop-portal), which GNOME, KDE and most other desktops already run. The AppImage may need libfuse2 on newer distributions.

Notes for Windows

The installer is per user: it installs into %LOCALAPPDATA%\Hexalyzer and does not need admin rights. Releases up to v0.3.0 installed into C:\Program Files\Hexalyzer, so uninstall that version first (as admin) to avoid having two copies.

Building from source

Building needs Rust 1.95 or newer. The repository pins the exact compiler in rust-toolchain.toml, which rustup installs automatically on the first build.

Use cargo packager to build an installer for your platform. Go into hexalyzer directory cd hexalyzer and run cargo packager --release. It builds the app first and then packages it: a .dmg on macOS, a -setup.exe on Windows, and Linux packages such as .deb and AppImage (pick them with e.g. --formats deb,appimage).

To build the CLI tool, run cargo build -p intelhexlib --features cli --release

On Linux, building the GUI requires the X11 / Wayland development headers. On Debian / Ubuntu:

sudo apt-get install libxkbcommon-dev libwayland-dev \
  libxcb-render0-dev libxcb-shape0-dev libxcb-xfixes0-dev

On Windows, the executable icon is embedded at build time by the winresource build dependency, so no extra setup is needed.

Usage

Getting started

  1. Open a File: Use the File → Open file... menu or drag and drop a .hex or .bin file into the main window.

  2. Navigate: Use the scroll area to browse the data. The center panel displays the hex values and their ASCII equivalents side-by-side. Use side panel to jump to a specific hex address or search for a byte / ASCII value(s).

  3. Edit: Select a byte (or a range) and type two hex digits to set its value. Changes are tracked and can be reverted if needed. Closing a tab or quitting the app with unsaved changes asks for confirmation.

  4. Inspect: Use the side panel to see how the selected bytes are interpreted as different data types (integers, floats, etc.). Multibyte selection is possible!

Keyboard shortcuts

On Windows and Linux, use Ctrl instead of Cmd.

Shortcut Action
0–9, A–F Type a new value for the selected byte(s)
Arrow keys Move the selection
Shift + click Extend the selection
Esc Cancel the current edit, selection or search
Cmd+S Save the current file
Cmd+C Copy selected bytes as hex
Cmd+Shift+C Copy selected bytes as ASCII
Alt+C Copy the address of the selection

Menu options

The top menubar provides access to the core file management and data transformation tools:

File

  • Open file...: Browse your system to load a file into a new tab.
  • Save (Cmd+S / Ctrl+S): Overwrite the current file with your changes (in its original format).
  • Export...: Save a copy of your current session to a new file (format chosen by extension) and open it in a new tab.
  • Gap Fill: 0xFF: Submenu to set the byte used to fill address gaps when exporting to BIN.
  • Reload: Reload the current file from disk.
  • Close file: Close the current tab.

Edit

  • Relocate...: Relocate the current file to a new start address.
  • Merge...: Merge selected file into the current one. Before merging, new start addresses can be specified for both files.
  • Insert Range...: Insert range of bytes at provided address range.
  • Remove Range...: Remove range of bytes from provided address range.
  • Restore byte changes: Discard all changes made to the current file.
  • Copy as Hex / Copy as ASCII / Copy Address: Copy selected bytes to clipboard as hex, ASCII or their (start) address.

View

  • Show Sidebar: Toggle the side panel (can also be done by dragging or double-clicking the edge).
  • Select Bytes per Row: Switch between displaying 16 or 32 bytes per row.

Tools

  • Hex Converter: a helper tool that can convert between HEX / DEC / BIN / ASCII formats; accounts for the endianness and signedness of the data.

About

Displays version information and credits for the Hexalyzer project.

Intel HEX Library

The core of Hexalyzer is powered by a standalone Intel HEX library intelhexlib. It is designed to handle memory-sparse firmware files: data is stored as contiguous chunks in a BTreeMap<usize, Vec<u8>>, so large gaps between memory segments don't use extra RAM. It can read, edit (bytes, ranges, relocation, merging), search and write HEX and binary data.

See the library README for installation, a usage example and the full hexcli reference.

CLI

The hexcli tool is built on the library. It can:

  • Show info about a file.
  • Relocate a file to a new start address.
  • Convert a file between BIN and HEX formats.
  • Merge multiple files into one (mixing BIN and HEX files is allowed).

Prebuilt binaries are attached to each release (see Installation).

Development

The repository is a Cargo workspace with two crates: hexalyzer (GUI app) and intelhexlib (library and hexcli tool).

Common tasks are run through run.sh:

  • ./run.sh check: format the code and run clippy with strict lints.
  • ./run.sh test: run CLI, doc, unit and integration tests, with a coverage report (requires cargo-llvm-cov).
  • ./run.sh bench: run the intelhexlib benchmarks.

Every pull request is checked by GitHub Actions: formatting, clippy (warnings fail the build) and the full test suite on Linux, macOS and Windows.

To make a release, bump the version in the root Cargo.toml, run cargo check so Cargo.lock picks up the new version (CI builds with --locked), and push a matching tag. The release workflow runs the checks, builds the installers and CLI for macOS, Windows and Linux, and attaches them with a checksum file to a draft GitHub release, ready for release notes and publishing. To test the release build without making a release, run the Release workflow manually from the Actions tab; the files are attached to that run. To update Rust, bump channel in rust-toolchain.toml.

History

v0.1.0 (2026-01-14) - Initial Release.

v0.2.0 (2026-01-30) - Release with added usability features and improved performance.

v0.3.0 (2026-06-20) - Added lots of new features; improved UX.

v0.4.0 (2026-11-18) - Stability and robustness release: atomic file saves, stricter parsing, and many edge-case fixes. Hex converter has its own window, Linux package is added, as well as per-user Windows install.

Future app improvement ideas

  1. Support Undo / Redo.
  2. Support ELF format.
  3. Saving an entire app state.
  4. Introduce ViewModel layer. Right now, UI tightly couples rendering and model details. This will enable adding Comparison (Diff) tool which can reuse the same model.

About

Parser library and viewer app for IntelHex and binary files written in Rust

Topics

Resources

Stars

9 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages