IMSProg - software for CH341A-based programmers to work with I2C, SPI and MicroWire EEPROM/Flash chips
Home Page: https://antenna-dvb-t2.ru/IMSProg.php
License: GNU General Public License v3.0
Михаил, приветствую. Немного душноты :) Если установить IMSprog, то в апликейшен попадает 3 файлика.
I think is useful to add a translation part in readme, small example below taking from older commit and adding a small note for contributing to add new language (to be improved):
Hungarian translation by blackPantherOS,
Italian translation by Marino Pasquale and Giovanni Scafora,
Brasil translation by Alexandre C. Leite,
Ukrainian translation by Sergey Golovko
Anyone can add or improve a translation by making a pull request.
Translations files are located in: IMSProg_programmer/language/ and IMSProg_editor/language/
Can you add to README.md the instructions to create .deb / .rpm after compilation?
IMSProg can be compiled on macOS natively and works. The only one problem is udev rules for device detection. MacOS doesn't have udev rules, so it is necessary to do it darwin-way (maybe using diskutil). Unfortunately, as we discussed, @bigbigmdm couldn't do it himself because he doesn't know anything about macOS. It is really difficult to support multiple operating systems and it is normal.
I opened this issue to encourage people to help with porting IMSProg to macOS.
Hi,
From this discussion I have this problem:
When I try to flash coreboot.rom file but I get this error when I do the "Erase-Program-Verify":
Error comparing data!
Address: 00000000
Buffer: 5F
Chip: 00
My bios chip is MX25L12835EZNI-10G. Is that supported?
Hi @bigbigmdm! First of all thank you for the software. I read content of 93C56 and bits are misplaced.
I got:
4a31 4634 3446 5338 5958 324c 3036 3333 3135....
instead of:
314a 3446 4634 3853 5859 4c32 3630 3333 3531....
Any ideas what could cause incorrect reading?
Here is data spec for the eeprom.
Image of the chip:
Chip connection:
| CH341A | 93C56 pin name | 93C56 pin |
|---|---|---|
| CLK | sk | 2 |
| CS | cs | 1 |
| MOSI | di | 3 |
| MIOS | do | 4 |
| GND | gnd | 5 |
| 3.3V | pe | 6 |
| 5V | pre, Vcc | 7,8 |
Do IMSProg need to support 45DB series chips (e.g. AT45DB161D)?
Who uses chips of this series for work, please participate.
Ubuntu 23.10
amd64
Linux version 6.5.0-28-generic
V 1.3.7
Chinese locale is zh_CN, not zn_CH.
No response
No response
No response
Does IMSProg use the same database format as EZP2019, EZP2020, EZP2023, Minpro I, XP866+ programmers or similar? "Основан на формате" means "similar", but "is clone" sounds like "database format is the same"...
"Формат базы данных микросхем основан на формате программаторов EZP2019, EZP2020, EZP2023, Minpro I, XP866+."
https://antenna-dvb-t2.ru/IMSProg.php
"The chip database format is clone with EZP2019, EZP2020, EZP2023, Minpro I, XP866+ programmers."
https://github.com/bigbigmdm/IMSProg/blob/main/README.md
Ubuntu 22.04
amd64
6.5.0-35
commit 0573530
cmake ask sudo passwrd
~/build/IMSProg/IMSProg/IMSProg_programmer/build$ cmake ..
-- The C compiler identification is GNU 11.4.0
-- The CXX compiler identification is GNU 11.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for module 'libusb-1.0>=1.0.20'
-- Found libusb-1.0, version 1.0.25
-- Checking for module 'udev'
-- Found udev, version 249
[sudo] пароль для johndoe:
No response
why it ask?
No response
Actually, IMSProg_programmer/other/index.html seems manually generated from old version of README.md.
This don't seem very good, so is better remove it, and include README.md in package docs or keep it updated.
For keeping it updated, the best way is to generate on build (and keep it optionally if software required is installed).
I did some very fast tests and the best software tested seems pandoc, done with:
pandoc -s --metadata pagetitle="IMSProg" README.md -o index.html
As hinted here, udev uaccess is granted by /usr/lib/udev/rules.d/73-seat-late.rules. So having a rule add the uaccess tag after 73-seat-late.rules ran has not effect. The rules are ran in lexical order, so to be compatible with the uacccess system, the rule must be renamed, i.e. to 70-CH341.rules.
After compiling the source code and installing on Ubuntu 22.04, IMSProg cannot find the chip database file IMSProg.Dat.
I downloaded a new version using the IMSProg_database_update.sh script and put it in the /opt/IMSProg folder as described in the README.md file. The error persists.
I then used strace to look at what is being initialised and found that IMSProg is expecting the chip database file in the location /etc/imsprog/IMSProg.Dat.
After copying the file there, the chip database is loaded correctly on startup.
fix:
sudo mkdir /etc/imsprog
sudo cp /opt/IMSProg/IMSProg.Dat /etc/imsprog
IMSProg fails when trying to read 32Mb spi flash.
This happens because of null pointer in spi_nor_flash.c
static int snor_4byte_mode(int enable)
{
int retval;
if (snor_wait_ready(1))
return -1;
if (spi_chip_info->id == 0x1) /* Spansion */
{
The spi_chip_info does not exist.
If you have a desire to help the project, please compare the two pdf documents. I have done this more than ten times. I can't see any difference, but the M95M128 works correctly with my programmer and the 25F512 does not write or erase.
First document - https://www.st.com/resource/en/datasheet/m95128-r.pdf
Second document - https://pdf1.alldatasheet.com/datasheet-pdf/download/175067/ATMEL/AT25F512.html
The fact that these chips are of different volumes is understandable. It's just that I have both of them in stock.
README.md
"On Debian >=13 and Ubuntu >=23.10:
sudo apt-get install systemd-dev
"
Are you shure? I have Ubuntu 23.10 (but it was updated from previous Ubuntu 23.idon'tremember may be 04). systemd-dev already has installed... How we can check does systemd-dev already has installed by default on Ubuntu 23.10 and Ubuntu 24?
Looks like you use CMake and qmake both build systems. But looks like you prefer CMake. I think it is good choice!
Do you really need qmake? It will take a great power to keep up to date both. I suggest drop qmake (remove IMSProg_editor.pro and IMSProg.pro).
It is not 100% clear where 99-CH341.rules should be placed in:
/lib/udev/rules.d according this: Line 273 in 5f5b625
/etc/udev/rules.d according this:
Anyway .deb actually install it in /usr/lib/x86_64-linux-gnu/udev/rules.d/ which is surely wrong:
$ dpkg -c imsprog_1.1.2-12_amd64.deb
drwxr-xr-x root/root 0 2023-12-01 00:08 ./
drwxr-xr-x root/root 0 2023-12-01 00:08 ./etc/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./etc/imsprog/
-rw-r--r-- root/root 36448 2023-12-01 00:08 ./etc/imsprog/IMSProg.Dat
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/bin/
-rwxr-xr-x root/root 580152 2023-12-01 00:08 ./usr/bin/IMSProg
-rwxr-xr-x root/root 549 2023-12-01 00:08 ./usr/bin/IMSProg_database_update
-rwxr-xr-x root/root 129568 2023-12-01 00:08 ./usr/bin/IMSProg_editor
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/lib/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/lib/x86_64-linux-gnu/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/lib/x86_64-linux-gnu/udev/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/lib/x86_64-linux-gnu/udev/rules.d/
-rw-r--r-- root/root 248 2023-11-17 18:17 ./usr/lib/x86_64-linux-gnu/udev/rules.d/99-CH341.rules
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/applications/
-rw-r--r-- root/root 2094 2023-12-01 00:08 ./usr/share/applications/IMSProg.desktop
-rw-r--r-- root/root 2106 2023-12-01 00:08 ./usr/share/applications/IMSProg_database_update.desktop
-rw-r--r-- root/root 1873 2023-12-01 00:08 ./usr/share/applications/IMSProg_editor.desktop
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/doc/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/doc/imsprog/
-rw-r--r-- root/root 1342 2023-12-01 00:08 ./usr/share/doc/imsprog/changelog.Debian.gz
-rw-r--r-- root/root 11863 2023-12-01 00:08 ./usr/share/doc/imsprog/copyright
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/doc/imsprog/html/
-rw-r--r-- root/root 675023 2023-12-01 00:08 ./usr/share/doc/imsprog/html/index.html
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/doc-base/
-rw-r--r-- root/root 268 2023-12-01 00:08 ./usr/share/doc-base/imsprog
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/imsprog/
-rw-r--r-- root/root 3823 2023-11-17 18:17 ./usr/share/imsprog/chipEditor_de_DE.qm
-rw-r--r-- root/root 3771 2023-11-17 18:17 ./usr/share/imsprog/chipEditor_es_ES.qm
-rw-r--r-- root/root 3778 2023-11-17 18:17 ./usr/share/imsprog/chipEditor_hu_HU.qm
-rw-r--r-- root/root 3732 2023-12-01 00:08 ./usr/share/imsprog/chipEditor_it_IT.qm
-rw-r--r-- root/root 3791 2023-12-01 00:08 ./usr/share/imsprog/chipEditor_pt_BR.qm
-rw-r--r-- root/root 3782 2023-11-17 18:17 ./usr/share/imsprog/chipEditor_ru_RU.qm
-rw-r--r-- root/root 3782 2023-11-17 18:17 ./usr/share/imsprog/chipEditor_uk_UA.qm
-rw-r--r-- root/root 2938 2023-11-17 18:17 ./usr/share/imsprog/chipEditor_zn_CH.qm
-rw-r--r-- root/root 18193 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_de_DE.qm
-rw-r--r-- root/root 18500 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_es_ES.qm
-rw-r--r-- root/root 18628 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_hu_HU.qm
-rw-r--r-- root/root 17847 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_it_IT.qm
-rw-r--r-- root/root 18567 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_pt_BR.qm
-rw-r--r-- root/root 17894 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_ru_RU.qm
-rw-r--r-- root/root 18436 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_uk_UA.qm
-rw-r--r-- root/root 14767 2023-12-01 00:08 ./usr/share/imsprog/chipProgrammer_zn_CH.qm
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/man/
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/man/man1/
-rw-r--r-- root/root 755 2023-12-01 00:08 ./usr/share/man/man1/IMSProg.1.gz
-rw-r--r-- root/root 885 2023-12-01 00:08 ./usr/share/man/man1/IMSProg_database_update.1.gz
-rw-r--r-- root/root 793 2023-12-01 00:08 ./usr/share/man/man1/IMSProg_editor.1.gz
drwxr-xr-x root/root 0 2023-12-01 00:08 ./usr/share/pixmaps/
-rw-r--r-- root/root 6976 2023-11-17 18:17 ./usr/share/pixmaps/IMSProg64.png
-rw-r--r-- root/root 3013 2023-11-17 18:17 ./usr/share/pixmaps/IMSProg_database_update.png
-rw-r--r-- root/root 2790 2023-11-17 18:17 ./usr/share/pixmaps/chipEdit64.pngREDOS 7.3.4
amd64
No response
Version 1.3.9
In one of the RedHat based distributions I saw incorrect display of national text characters in the programme:
No response
No response
The following edits had to be made for correction:
IMSProg_programmer/main.cpp
- 21 QFont font("Monospace");
+ 21 QFont font("OpenSans");
- 23 font.setPointSize(12);
+ 23 font.setPointSize(11);MSProg_programmer/mainwindow.cpp
- 109 heFont = QFont("Monospace", 10);
+ 109 heFont = QFont("DejaVu Sans Mono", 10);No such problems are observed with the same IMSProg distribution on Fedora 38.
What is the situation with fonts in different distributions?
mainwindow.cpp (starting at line 617 ):
chipData = hexEdit->data();
//uint8_t buf[currentBlockSize];
uint8_t *buf;
buf = (uint8_t *)malloc(currentBlockSize);
for (k = 0; k < currentNumBlocks; k++)
{
for (j = 0; j < currentBlockSize; j++)
{
buf[addr + j - k * currentBlockSize] = static_cast<uint8_t>(chipData[addr + j]) ;
}
QByteArray ChipData initialized with the hexEdit->data(). But the user can load file of any size. If the file size is smaller than chip size, chipData will also have size < memory chip size.
Since writing algorithm alawys writes the full chip, and the chipData.size < currentNumBlocks*currentBlockSize, at some moment chipData[addr + j] will try to read bytes which are not persent in chipData. QT runtime warns about that with the message like "QByteRef beyond QByteArray size". Actually it is reading beyond array limits and this is undefined behaviour.
Good day,
after installing deb package (v1.0.29-3/Ubuntu 22.04) can't open "Edit chip database" (ctrl+q) with "Not found file IMSProg_editor error" and same error on program start
Separately IMSProg_editor can be opened
Hi again,
I would like to recommend a source for updating the IMSprog database, a good source the mtd drivers (kernel/drivers/mtd/devices/) from kernel tree, example:
https://www.infradead.org/pipermail/linux-mtd/2013-April/046407.html
Hey there, IMSProg is great; thank you for creating it. I thought it might help others access IMSProg if I packaged it for the AUR, which I've now done: https://aur.archlinux.org/packages/imsprog. You can read the PKGBUILD there, but essentially it just pulls the release tarball from this repo and automates the build/install process. Users get the added benefits of the transactional install & uninstall capabilities.
Perhaps it might help others if a note was added to the README to say Arch users can install with paru imsprog or yay imsprog, or whichever AUR helper they like! If you have any feedback or suggestions for the PKGBUILD please let me know. The only deviation from the build process in the README is that I've used
make -j`nproc`
instead of make -j4, which should give a quicker performance boost on systems with more cores. I haven't timed this, though.
Lastly, it's not mentioned in the README, but the database update script depends on wget and zenity (I've added these to the PKGBUILD depends array), and the .desktop file for the script has the same Name and GenericName (the latter, just the English text) properties as the main IMSProg entry, which leads to ambiguous listings in, e.g., rofi:
If it was something you'd be open to, I'd be happy to submit a couple of PRs for these minor fixes. In any case, thanks!
Hello, newbie here.
How should I uninstall the program? I didn't find any script so I tried with sudo make uninstall but I received the error message make: *** No rule to make target 'uninstall'. Stop..
To install the program I unpacked the tar.gz and run build_all.sh.
IMSProg_editor.desktop
Comment[uk]=Редактор бази мікросхем для IMSProg
GenericName[uk]=Редактор бази мікросхем для IMSProg
IMSProg.desktop
Comment[uk]=Программатор i2c,SPI,MW мікросхема для CH341a
GenericName[uk]=Программатор i2c,SPI,MW мікросхема для CH341a
IMSProg_database_update.desktop
Comment[uk]=Оновлення бази даних мікросхеми для IMSProg
GenericName[uk]=Оновлення бази даних мікросхеми для IMSProg
Arch Linux
64 bit
6.8.7 from Arch Linux
1.3.6
Open dialogSFDP.
The translation is perfect.
If you click on Read or on Write registers, part of the translation reverts to English (see Legend area).
I am sending the two pictures to give you a better idea.
No response
No response
No response
Raspbian GNU/Linux 11 (bullseye)
armhf
6.1.21-v7+ #1642
1.3.7
Can't read block 0 or write block 0
No response
No response
No response
What is different between EZP2019-EZP2025_chip_data_editor and IMSProg editor?
I want to fix README.md text
"IMSProg - Linux IMSProg - I2C, MicroWire and SPI EEPROM/Flash chip programmer for CH341A devices. The IMSProg is a free programmer tool based on QhexEdit2 and modified SNANDer programmer.
This is a GUI program used widget QhexEditor. For setting the SPI chip parameters you can use the Detect button for reading chip parameters (JEDEC information reading) or manually setting it. The I2C and MicroWire EEPROM only manually selected."
Looks like this repo contains two different programs: programmer and editor. If so then you should describe the programmer and describe the editor...
P.S. Please use English or Russian.
Нашел старую мат. плату, с AWARD биос чипом (32 ношки). Судя по всему это (atmega3208):
На форумах нашел схему перепрошивки:
Возможно, стоит добавить эту информацию в программу \ документацию. Работоспособность, не проверял, нужен кварц.
Please add to the "System software requirements" section of README.md, one more item: sudo apt-get install pkg-config
This package is absent by default in the Ubuntu
The .deb package installs the 99-CH314.rules file at path /usr/lib/x86_64-linux-gnu/udev/rules.d/, which folder doesn't exists and it's created at install time, instead of the default /etc/udev/rules.d/ directory, causing the device to not be read on USB by IMSProg.
This behavior happens on both apt install imsprog and direct dpkg -i *.deb commands.
Verify function on I2C EEPROMs fails when verifying files shorter than full EEPROM size because it searches for the dummy 0x00 used to pad the content by the Program function
Maybe adding some 0x00 padding also in the Verify function may solve the issue with hopefully low effort (in the virtual file content bytestring used to do the comparison you could pad accordingly to what happens during Program)
Issue find on Ubuntu 22.04 LTS, writing on the following IC:
can you add the support for GD5FGQ4UB91G ? these family nand is supported in SNANDER
Михаил, ещё раз приветствую. Заметил забавную особенность в плане разной скорости записи одной и той же флешки разным софтом. Шью флешку SPANSION S25FL064A на линуксе при помощи вашего IMSProg и на винде AsProgrammer https://github.com/nofeletru/UsbAsp-flash
Разница в скорости записи в 10 раз т.е. запись 5 мегабайтной прошивки в IMSProg проходит за ~20минут, а в AsProgrammer за ~2минуты. Нельзя ли как-то ускорить запись и в IMSProg?)
hello dear friend, I have an tl866cs epron programmer and I want to use his database in your IMSprog, but I don't know how,
I saw in your repository that I can use the database of ezp2019-2025 too, can you give me a shortcut of how to add all the chip datbase from tl866cs in IMSprog, the one I have doesn't have .dat files to be added.
Coild you add MX25L3233F Flash support?
Thank.
Михаил, приветствую. А есть в интерфейсе возможность записи со смещением т.е. писать фал не с нуля, а скажем с 700000 адреса? Есть необходимость шить в одну микросхему 2 файла. Первый шьется с нуля, а второй со смещением.
ALT Linux
any
any
1.3.2
Error due to incorrect formatting of comments.
$ /sbin/udevadm -V
254
$ /sbin/udevadm verify 99-CH341.rules
/home/data/gear/IMSProg/IMSProg_programmer/other/99-CH341.rules:1 Invalid key/value pair, ignoring.
/home/data/gear/IMSProg/IMSProg_programmer/other/99-CH341.rules:2 Invalid key/value pair, ignoring.
/home/data/gear/IMSProg/IMSProg_programmer/other/99-CH341.rules: udev rules check failed.
1 udev rules files have been checked.
Success: 0
Fail: 1
$ /sbin/udevadm verify 99-CH341.rules
1 udev rules files have been checked.
Success: 1
Fail: 0
Must use # at the beginning of the line.
Need mentors to add IMSProg to Fedora, Centos, RedHat.
I'm trying to read a chip marked S93C56 BDDVAX 8913. Any idea what settings I should use? Thanks!
Debian 12
amd64
6.1.0-21-amd64
1.3.8
первый раз сработало. но потом обращается на адрес такой
Couldn't open device 1a86:5512
хотя на самом деле программатор тут
Bus 002 Device 011: ID 1a86:5523 QinHeng Electronics CH341 in serial mode, usb to serial port converter
без понятия
нормальную работу программы
нету доп информации
Thank you for a good software but the feature is realy missing is recently open files.
Also it does not remember last opened directory. All the path should be passed again and again from the start to open a firmware.
I suggest new About text from here
I make tags using Wikipedia...
To run the editor program from the main window of the programmer: It seems that you didn't apply the my patch to the editor's relative path in mainwindow.cpp, so the program can't be launched from the programmer's toolbar, only from the command line or a separated icon. The reason for this is that when the user launches itt, it is not in /usr/bin, but in its home directory, therefore the relative path will be invalid.
I am attaching two pictures to help you understand the problems...
First showing the binary compiled from the current source code:
And this binary working fine after applying the my patch :
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.