> intel | hex | :10010000 <
// Intel HEX - Standard format for microcontroller firmware and EEPROM data
Microcontroller Ready
Standard format for programming microcontrollers and EEPROMs.
Error Detection
Each line includes a checksum for data integrity verification.
Memory Mapping
Includes address information for precise memory placement.
>> technical info
How Intel HEX Works:
Intel HEX format represents binary data as ASCII text records. Each line starts with ':', followed by byte count, address, record type, data, and checksum. This allows binary firmware to be transmitted as text.
Record Structure:
:LLAAAATTDD...CC : Start code LL Byte count AAAA Address TT Record type DD Data bytes CC Checksum
Why Use Intel HEX:
- >Microcontroller programming
- >EEPROM data transfer
- >Firmware distribution
- >Bootloader protocols
- >Debug and verification
>> frequently asked questions
What is Intel HEX format?
Intel HEX is a file format that conveys binary information as ASCII text records. It's widely used for programming microcontrollers, as it includes addressing information and error-checking.
What are the different record types?
Common types include: 00 (Data), 01 (End of File), 02 (Extended Segment Address), 04 (Extended Linear Address), and 05 (Start Linear Address). Type 00 is most common for data.
How does the checksum work?
The checksum is the two's complement of the sum of all bytes in the record (except the checksum itself). It ensures data integrity during transmission and storage.
Why use Intel HEX over raw binary?
Intel HEX is ASCII text, making it easier to transmit through various channels. It includes addressing information and checksums, and can represent sparse memory layouts efficiently.
Other Languages
References
How we make sure
We check this tool with the automated test suites linked below. Example checks are shown in their original language.
- Verification method
- Independently inspect record lengths, addresses and payload bytes, check checksums, then verify complete UTF-8 decoding.
- Comparison reference
- Intel HEX zero-sum and S-record ones-complement checksum rules, with explicit byte assertions.
- Verification scope
- The listed records and boundaries do not cover every firmware address layout.
Test source and cases (select a file to read it)
-
text-reliability.test.js
- Intel HEX: UTF-8 records preserve bytes, addresses, counts and zero-sum checksums
These checks cover the listed examples and boundaries, not every possible input. Round trips and checks using the same library are not independent verification.