Intel HEX & S-record Image Audit

Paste a .hex or .s19 firmware image.

Intel HEX & S-record Image Audit
Example of the result this page gives you

Try it freeFull version · $149 once →

How it works
  1. Enter your details in the free version below.
  2. See your result right away on this page.
  3. Need more? The full version adds what is listed under "What you get".

Updated 2026-10-29 · ReadyStack

Try it freeFull version →

Paste a firmware image (.hex, .ihex, .s19, .s28, .s37, .srec, .mot). Every record checksum is recomputed byte by byte and every absolute address is mapped, so a bad checksum, an overlap, a gap, a record past the EOF or a stray merge line is named at its line before the image reaches the programmer. The sample below is a 14-line image with a hand patch, a generator comment and a record appended after the EOF. It runs in this tab and sends nothing.

Install free

Free for the file open in your editor - no key, no limit. The workspace sweep and the report ask for a key.

VS Code MarketplaceOpen VSX (Cursor, VSCodium)npmMCP server (npx)
ext install ReadyStack.hex-image-audit
npx @readystack/hex-image-audit <file>
npx @readystack/hex-image-audit --mcp

Team? One key for every ReadyStack linter, 5 seats, $149 once

Get the full rule table as a PDF
All 17 rules Intel HEX & S-record Image Audit checks, each with its source and date, on printable pages you can hand to your team or auditor. We email it now, and once more only if a rule changes. No newsletter.

Get the full version $29

Sweeps every .hex/.s19/.srec/.mot image in the workspace in one pass and writes a dated Markdown audit report you keep (scope + ownership axis) — $29 once per person or CI seat.

One payment, one licence key for this tool. The key is shown right after payment.

Freelance embedded software engineers average about $103 an hour (contractrates.fyi, crowdsourced, read 2026-10-29); a manual record-by-record review of one image takes longer than that hour.

Buy the full version — $29

Need more than this one? ReadyStack Pass opens all 679 files and 561 full versions — $29/month or $199/year. See the Pass →

Embed this tool on your site (free)

Paste this code into your page. It runs in your visitor’s browser and stays up to date. Nothing your visitors type is stored.

 All embeddable tools

For businesses: your name and logo instead of ours, and each visitor’s result + e-mail in your inbox (only when they tick consent) — Pro from $19/month. See Pro →

· ReadyStack

Worked example

Real numbers from this tool, line by line.

7 errors in a 14-line firmware image: what one hand-patched .hex file hides

7 errors and 11 warnings is what a 14-line Intel HEX image returned for an embedded firmware engineer merging a bootloader patch before the flashing station, checked against 17 rules.

linewhat the record doesfinding
3ends in checksum 0x2Arecomputed checksum is 0xE8
4byte count says 16the record carries 15 data bytes
5# regenerated by patch_tool.pynot a record at all
9writes 0x08000108line 7 already wrote that address
10starts at 0xFFF8runs 16 bytes past 0xFFFF with no type 04 record
11record type 0x07only types 00-05 exist
14a data recordsits after the end-of-file record on line 13

The 11 warnings are the map around those errors: five blocks that do not fill whole 256-byte flash pages, four unwritten gaps (one of them 65,000 bytes), an entry point at 0x00000200 that no record writes, and a switch from upper- to lower-case hex on line 6 that says two different tools wrote this file.

Why each of those breaks a board

An Intel HEX checksum is the two's complement of every byte before it. A hand edit that changes one data byte and leaves the old checksum is the most common reason a strict programmer aborts — and a lax one flashes the record anyway. A byte count that no longer matches the data makes a loader read past the record or cut it short. The comment line on line 5 is exactly what a generator script leaves behind; many programmers stop at it.

The overlap on line 9 is the quiet one. Two records write the same absolute byte, so the value that ends up in flash depends on the load order of the tool. The record on line 14 is the classic appended fix: it sits after :00000001FF, so conforming loaders never read it and the patch never reaches the device.

Three images, three different answers

The same 17 checks give different answers to different files. A clean 19-line image — one type 04 record, 16 data records filling one 256-byte page, a start record and the EOF — returns 0 findings. A 6-line Motorola S19 image with one edited byte returns 3: the S-record checksum on line 3 (0x00 where 0x64 is correct), a block that stops 192 bytes short of a page, and no S0 header. An audit that reports nothing on a good image is the half nobody tests.

Why the archive copy matters now

Since 11 September 2026 the EU Cyber Resilience Act's reporting obligations apply to products with digital elements, and the technical documentation is kept for 10 years after the product is placed on the market or for the support period, whichever is longer. A firmware image kept as evidence is only useful if it is the image that shipped and still says which release it is. An S-record image without an S0 header names no module or version; an Intel HEX image has no header record at all.

What is free and what is not

Opening one image is free and whole: every check, every finding, every line, in VS Code or in the browser, no key. The licence covers a different job — sweeping every .hex, .s19, .srec and .mot file in a build output folder in one pass and writing a dated Markdown audit report you keep with the release. A freelance embedded software engineer averages about $103 an hour on crowdsourced rates; re-reading one merged image byte by byte takes longer than that hour.

Paste the image you are about to flash and read its lines first.

15 seconds — what it actually does

Questions people ask

What does Intel HEX & S-record Image Audit actually do?

It reads one firmware image in Intel HEX or Motorola S-record format and recomputes every record checksum byte by byte, checks each byte-count field, maps every absolute address and names bad records, overlaps, gaps, data past 0xFFFF without an extended-address record, records after the EOF, a missing terminator and an entry point outside the image. Each finding carries its line number.

Who is Intel HEX & S-record Image Audit for?

It is for embedded and firmware engineers who merge a bootloader with an application image, hand-patch a .hex before release, regenerate images with scripts or coding agents, or send .hex and .s19 files to a contract manufacturer's flashing station. It also fits release engineers who keep firmware images as evidence in a product's technical documentation file.

Why not use a chatbot or a free converter?

A chatbot reads a pasted image as text and is not built to recompute every two's-complement checksum or carry type 04 extended addresses across the whole file. Command-line converters such as objcopy and srec_cat are built to convert an image, not to audit it, so they do not hand you one list of every bad record, overlap, gap, page split and entry-point problem by line.

What is free and what does the licence add?

Free: the image you have open, in VS Code or in the browser, is checked against all 17 rules with every finding and line shown, no key and no limit on records. The licence, $29 once per person or CI seat, sweeps every .hex, .s19, .srec and .mot file in the workspace in one pass and writes a dated Markdown audit report you keep.

How does the cost compare with paying an engineer?

Freelance embedded software engineers average about $103 an hour according to crowdsourced rates on contractrates.fyi, read on 29 October 2026. Re-reading one merged image record by record, recomputing checksums and mapping addresses takes longer than an hour by hand, so a single review already costs more than the one-time $29 licence for the folder sweep and report.

Why not just ask ChatGPT or another AI chat?

A general AI chat answers from training data with a cutoff date, cannot read your repository and names no rule version. Intel HEX & S-record Image Audit checks the file you open against 17 rules from a rule set dated 2026-09-21, and points at the exact line. For a filing, an audit or a client you need that dated result on your own files.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Privacy: your e-mail is used only to send you the answer. A question appears on this page only after it is answered, without your e-mail.

For a team or company: for an invoice with your company details, a quote or several licences, write to [email protected].

New this week

More in Developer tools See all →