An Intel HEX EPROM programmer workflow is less mysterious once you separate three things: the chip you are programming, the file format you were given, and the software that will load it. That matters for this site because both the ART EPP-4 documents and the MQP PROMDRIVER manual mention support for common archival formats including Intel HEX, Motorola HEX, and binary images.

What Intel HEX Actually Is

Intel HEX is a text-based file format that stores address and data records in a structured way. Unlike a flat binary dump, it can carry address information directly in the file. That makes it useful when firmware is exchanged between toolchains, service engineers, and archival collections that want something easier to inspect or transmit than a raw image.

For many restorers, the question is not “what is Intel HEX?” but “can my programmer software load it cleanly?” In the case of the EPP-4 and MQP material documented here, the answer is yes for the published toolchains.

What the ART and MQP Documents Say

The ART EPP-4 brochure lists automatic file format detection and conversion for formats such as binary, Motorola HEX, Intel HEX, and Tektronix HEX. The MQP Series II manual lists a broader file-format section that includes binary image, Intel Hexadecimal, Motorola Hexadecimal, and several object-file variants.

That means both software families were designed with real-world firmware exchange in mind rather than assuming everything would arrive as a raw binary file.

When to Use Intel HEX Instead of Binary

  • Use Intel HEX when the source file already includes address-aware records and you want to preserve that structure.
  • Use binary when you know you need a flat image with a fixed start point and no format translation overhead.
  • Use Motorola HEX when that is the published source format and your toolchain supports it directly.

The key is not to convert formats casually unless you understand what address data or padding behaviour might change in the process.

A Safer Legacy Workflow

  1. Confirm the exact chip family and capacity first.
  2. Load the source file in the programmer software and verify the detected format.
  3. Check address expectations before programming.
  4. Read, program, and verify rather than assuming the write succeeded.

If your actual target is an ART EPP-4 setup, the manual guide and download archive are the best next steps. If you are working on older MQP workflows, start from the MQP200 manual page.

Primary Sources

The details in this article are based on the following source material.

Need the Archive Files?

If your next job is loading firmware into the ART or MQP archive tools rather than just understanding the format, start from the archive pages below.

Browse the archive and setup guides

Related Legacy Programmer Downloads

For preserved software and setup notes, use the main download page, the ART EPP-4 download guide, the MQP 200 download guide, the ART EPP-4 driver guide, and the PROMDRIVER archive guide. These pages keep the strongest ART EPP-4 download and MQP200 download terms clustered together for archive visitors.