IMSProg icon indicating copy to clipboard operation
IMSProg copied to clipboard

IMSProg cannot connect to EZP2023+ on Linux

Open sergiojoker11 opened this issue 1 month ago • 1 comments

Distribution

Ubuntu 24.04

Architecture

amd64

Kernel version

6.14.0-35 generic

IMSProg version

v1.7.1

Bug description

Hi, I'm trying to use IMSProg on Ubuntu 24.04 with an EZP2023+ programmer. IMSProg displays “Not Connected”, and when running it from the terminal I get:

Couldn't open device 1a86:5512.

What I see on my system

The device does not enumerate as 1a86:5512. Instead, when plugging the EZP2023+, the kernel reports:

idVendor=1fc8, idProduct=310b Product: WinUSBComm Manufacturer: www.zhifengsoft.com

lsusb shows:

Bus 001 Device XXX: ID 1fc8:310b www.zhifengsoft.com WinUSBComm

So IMSProg expects a CH341A-compatible device (1a86:5512), but my EZP2023+ identifies itself as a completely different USB device (1fc8:310b), which causes IMSProg to fail when opening it.

What I expected

Since the project documentation states that EZP2023 is supported, I expected IMSProg to detect this device or at least handle this VID/PID variant.

What I've tried

Different USB ports (USB2 / USB3)

Direct connection (no hub)

Different cables

Creating a udev rule (no effect, since the expected VID/PID is different)

Running with sudo

Running the software from terminal to get the exact error

Suggestion

It looks like the EZP2023+ model I'm using uses a different USB bridge (Zhifengsoft WinUSBComm instead of CH341A). If IMSProg intends to support the whole EZP2023 family, this VID/PID might need to be added together with the corresponding USB protocol.

I'd be happy to test any build or provide additional logs if needed.

Thanks!

Steps to reproduce

No response

Expected behavior

No response

Additional information

No response

sergiojoker11 avatar Nov 20 '25 22:11 sergiojoker11

Hello, @sergiojoker11! IMSProg only supports the CH341A programmer. I will consider supporting CH347 and FT232H devices in the future. Nowhere in the documentation is there any mention of support for EZP series programmers, except that the chip database structure was borrowed from software for these programmers.

bigbigmdm avatar Nov 21 '25 04:11 bigbigmdm