HEXARBOR / IMAGE MERGE
Two images.
One checked union.
Review Intel HEX and Motorola S-record parts by byte address. Find disagreements before you share the merged files.
A handoff you can inspect.
| Import & validate | Choose up to four ASCII HEX or S-record files in Files. Review format, decoded bytes, entry address and original SHA256. Check record length, checksum, termination, count and address bounds. |
|---|---|
| Resolve overlaps | Inspect individual byte values and their source files. Equal overlaps are accepted; differing byte values or numeric entries block export. Disable an unwanted source to exclude its data. |
| Share complete output | Sparse HEX and SREC preserve the full enabled union. A binary window uses the exact range and fill you chose. The ZIP also contains original files, PDF, source and range CSV, a restorable source-bearing JSON plan and a SHA256 manifest. |
Support & supported formats
Email maga40@naver.com. Include app version and the exact error. Share proprietary source files only if you have permission and wish us to receive them.
Import boundaries
ASCII Intel HEX types 00–05 with EOF; single-width Motorola S1/S2/S3 data with an optional leading S0, optional S5/S6 count and matching S9/S8/S7 termination. No comments, vendor extensions, mixed S-record widths, wraparound or HEX data records crossing a 64KiB offset boundary. Four sources; each ≤2 MiB encoded, 20,000 records and 256 KiB decoded. Enabled union ≤512 KiB unique bytes. Twenty local plans and 96 MiB library. Binary window 1–2,097,152 bytes within 32-bit addresses.
Output entry and address semantics
Byte addresses only. Canonical HEX uses extended linear addresses and an agreed numeric entry when present. Segment CS:IP becomes CS*16+IP. Canonical SREC uses S3/S7; a missing entry becomes an explicit zero termination. Headers and record spelling are canonicalized; original bytes remain unchanged in the source files. Window.bin has no address or entry metadata; its range and fill are documented separately.
What the app does not do
No byte editing, rebase, ELF/disassembly, target word or phantom-byte conversion, hardware access, flashing, execution, signature validation, bootability or target compatibility guarantee. Use your own target tools to verify downstream use. File checksums detect record errors; they do not authenticate firmware.
Privacy policy
Effective October 4, 2026. Hexarbor is provided by Gobling Company.
We do not collect, receive, track, sell or upload your app data. Hexarbor has no account, developer network service, analytics or advertising SDK. Parsing and export run locally; the app makes no network requests.
Files you deliberately select are retained in local app storage to preserve original bytes and plans. Imported files are not modified. Files providers and device backups may retain copies under your own settings and their policies.
Shared ZIPs include original sources, proprietary image bytes and project notes. Only recipients and destinations you deliberately select through the system share sheet receive them. The app does not upload them to Gobling Company.
Delete sources or plans within the app. Removing the app deletes its local library. Keep important originals and exported JSON backups separately. iOS may clear export caches.
If you contact support, we receive the message and attachments you choose to send and use them to answer the request. Apple handles purchases under its own policies. Contact maga40@naver.com.
Use of the tool
Use and share only sources you have permission to handle. Hexarbor is a file review and conversion aid, not a programmer or certification service. A successful checksum or conflict check is not evidence of firmware safety, authenticity, target compatibility or bootability.