IMSProg – I2C SPI EEPROM/Flash chip Programmer

IMSProg – I2C SPI EEPROM/Flash chip Programmer

Tool NameDescription
IMSProgMain chip programmer tool.
IMSProg_editorChip database editor.
IMSProg_database_updateScript for updating chip database via external web server.
QHexEdit2Hex editor tool.
SNANDerProgrammer tool for specific tasks.


Version 1.3.1 with support 25xxx SPI EEPROM chips

Added support 25xx SPI EEPROM chips:

AT25010, AT25020, AT25040, AT25080, AT25160, AT25320, AT25640, AT25128, AT25256, AT25F512, AT25F1024
25AA010, 25AA020, 25AA040, 25AA080, 25AA160, 25AA320, 25AA640, 25AA128, 25AA256, 25AAF512, 25AAF1024, 25LC010, 25LC020, 25LC040, 25LC080, 25LC160, 25LC320, 25LC640, 25LC128, 25LC256, 25LC512, 25LC1024
CAT25C01, CAT25C02, CAT25C04, CAT25C08, CAT25C16, CAT25C32, CAT25C64, CAT25C128, CAT25C256, CAT25C512


IMSProg is a versatile programmer tool designed for CH341a devices, specifically tailored for programming I2C, SPI, and MicroWire EEPROM/Flash chips. This software, built on QhexEdit2 and inspired by SNANDer programmer, offers a user-friendly interface and is available free of charge.

Utilizing the QhexEditor widget, IMSProg provides an intuitive GUI environment. When configuring SPI chip parameters, users can either employ the Detect button for automatic parameter retrieval (JEDEC information reading) or manually input the settings. For I2C and MicroWire EEPROM chips, manual selection is the norm.

IMSProg supports a chip database format akin to EZP2019, EZP2020, EZP2023, Minpro I, and XP866+ programmers. Users have the flexibility to modify the database using the EZP Chip Data Editor, ensuring compatibility and customization according to their needs.



 IMSProg Programmer  Version 1.3.1
 IMSProg Programmer  Version 1.2.1
 IMSProg Programmer  Version 1.1.11
 IMSProg Programmer  Version 1.1.8
 IMSProg Programmer  Version 1.1.4-1 & 1.1.4-2


To initiate the compilation process for the IMSProg_editor, follow these steps:

  1. Navigate to the IMSProg_editor directory:
cd IMSProg_editor
  1. Create a new directory named ‘build’ to store the build files:
mkdir build
  1. Move into the newly created ‘build’ directory:
cd build
  1. Generate build files using CMake:
cmake ..
  1. Begin the compilation process using the ‘make’ command. Utilize the -j flag followed by the number of available processors (nproc) for parallel compilation:
make -j`nproc`
  1. Once compilation is completed, install the editor using the ‘sudo make install’ command:
sudo make install

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *