Hexarbor Image Merge

Review your HEX and S-record image parts as one byte-addressed workspace.

Hexarbor helps embedded developers inspect original files, find overlap disagreements and prepare a reproducible local handoff. It is an image-file review tool, not a programmer or a claim that an image will boot on your target.

SEE THE BYTES Import up to four supported ASCII Intel HEX or Motorola S-record files through Files. Inspect a touchable byte table, jump to a 32-bit hexadecimal address and see every contributing source/value for the selected byte. iPad provides a wide 16-byte table with ASCII; iPhone keeps byte targets touchable.

RESOLVE THE UNION Record lengths, checksums, address boundaries, end records and optional S-record counts are validated before import. Equal-value overlaps are accepted. Different bytes at the same address, or disagreeing source start addresses, block image export. Inspect conflicts and disable unwanted sources without changing their originals. Navigate the complete occupied-range index.

A REAL HANDOFF Build a ZIP with the full active union in canonical Intel HEX and SREC32, a contiguous Window.bin with your explicit start/length/gap-fill byte, source and range CSVs, a PDF review, unchanged original files, SHA256 checksums, window settings and a restorable plan JSON. Disabled originals remain in the packet for traceability.

LOCAL PROJECTS Name, annotate, duplicate and delete plans. Restore exported JSON backups. Save up to 20 plans within a 96 MiB local library. Production starts empty; an optional original analytic study demonstrates two synthetic image parts and gaps. No vendor firmware is bundled.

ONE PURCHASE No subscriptions, advertisements, sign-in, analytics or app network requests. Your sources stay on your device until you deliberately export/share. Packets may contain proprietary source data and notes. Deleting the app removes its library; keep exported backups.

SUPPORTED LIMITS ASCII Intel HEX types 00–05 with EOF, or one data-address width per S-record block: S1/S2/S3, leading optional S0, optional S5/S6 count and matching S9/S8/S7 termination. Up to 2 MiB encoded and 20,000 records per source, 256 KiB decoded per source, 512 KiB unique bytes in the active union. The binary window is 1–2,097,152 bytes. No comments/vendor extensions, mixed S-record widths, wraparound or HEX data crossing 64 KiB record boundaries.

OUTPUT SEMANTICS All addresses are byte addresses exactly as encoded. Canonical HEX uses extended linear records; an agreed numeric start is retained, including CS:IP converted to CS × 16 + IP. SREC uses S3 and S7; an unspecified start is represented by an explicit zero terminator. Headers and record spelling are canonicalized; originals remain unchanged. Window.bin covers only its named range, fills absent bytes and carries no address/start metadata.

No byte editing, rebasing, disassembly, ELF import, target word/phantom-byte conversion, firmware signing, debugger, flashing, device access or execution. Target compatibility, bootability and hardware programming are not verified. Use your target tools to validate any downstream use.

Discovery signals