Xeltek SuperPro 280U/580U/3000U 64bit hack

A recent Ebay purchase of a Xeltek SuperPro 280U came with the following note that it was supported only in Windows XP and not under Windows 7. This post documents how to make this working on a modern operating system; like Windows 10 64bit. Luckily; all of this software was readily available via webcaches and polish electronic forums. I’ve pulled all the documents here in one place so you can easily replicate it. I believe the software is the same for the 580U/3000U but you’re mileage may vary.

Why do this? This programmer is still very functional as long as you have a USB port.

First you need to get the Xeltek software from their support site under legacy programmers. Go ahead and download the 32bit windows install package and the test software so you can prove your “hack” is functional. Direct links for the SuperPro 280U install software and the SP280u Test.

Next install the SuperPro software to a known directory. The follow the instructions in the SP280u test archive. See the readme.txt file which tells you to put the TSETUSB2.USB file in \algo5 of the installed program.

Now you need to install the hacked EzUSB drivers from Cypress. This was explained in www.macros-arcade.com’s webcache. That website seems to be down – maybe forever which is why I’m copying the relevant bits here for prosperity:

The older Xeltec range of USB Eprom programmers do now work on 64 bit versions of windows, since, according to their own website “working on 64bit platform requires tremendous effort from our side
So to save their programmers from all of this tremendous effect, here is how to make it happen
N.B. This has only been tested on my PC using my Superpro 280u with Windows 7,8 and 10 – it should work for you, but everything is done at your own risk!


In the download file, Here,  are the signed driver and support files.

If you need XVI32 you will need to download it from their website.


Xeltek use a standard USB interface chip, an Ez-USB FX2, originally made by Anchor chips, who were taken over by Cypress.

Fortunately, they only seem to have made a single change to the reference driver that was issued by Anchor / Cypress, so as long as a 64 bit version of that driver exists then it should be possible to use the eprom programmer on a 64 bit OS.

A clever guy (Here) has already created a 64 bit version of the driver to use with some other hardware that utilises the same chip, and also sorted out the necessary inf files to allow you to install it on various newer versions of windows. A small change to that inf file, so it recognises the identity of the chip within the Superpro, and that will install the driver. 

Another helpful guy, Doug, has now signed the driver file so that you no longer need to do any trickery to let Windows allow you to use the driver – many thanks to him.
finally, you need to make one change to the SP3000.EXE to allow it to work with EZUSB.SYS (rather than their version XEUSB.SYS), and for this you will need a hex editor. I use XVI32, a free download from Here. using this search for the text “Xeltekusb-0” (on the latest version it is at offset 0x9B344). This is the name of the driver that it is going to use, and so we need to change this to “Ezusb-0” and then pad the extra characters out with 00’s (Hex 00, not characters!). Save this change and coupled with the driver you should now be able to use your Superpro on the 64 bit version of windows.


I heard from a user about a problem with the signed Xeltec drivers. So in case you are having the same problem :-
“My new PC has windows 10 installed as UEFI. Installing it that way enables secure boot by default and saves the default keys to your motherboard. Secure boot adds another layer of driver authentication, which causes the Xeltec patched driver to fail.
In order to fix this, you need to disable secure boot (which is motherboard specific).
Once disabled, the driver plays nice. Only caveat – your system is now (technically) susceptible to rootkits and other forms of malware that attack your drivers. Not a huge concern if you’re not using fishy software.”
Thanks Bill

Obviously; those links are likely dead. So I did a google search and came to a polish site which had all the original files: https://www.elektroda.pl/rtvforum/topic3353985.html#16553970

I registered with the site so I could download it. I’ve put the unaltered files on my Google Drive for public consumption:

UnRar (or use 7zip) and uncompress the Xeltek 3000U Win7x64.rar to a subfolder in your installation location. You are going to want to further unzip: sp3000u_x64_driver_signed.zip to your installation folder. This contains a How To.txt file and several ezusb.* driver files. That howto file has most of the text from the Bill quote above. All I did was right click on the ezusb.inf file and click install. This installs the signed 64bit driver for use under Windows 10 64bit. 😀

Now uncompress SP3000.exe from the Xeltek 3000U Win7x64.rar archive. This is the hex edited executable discussed in the How To.txt and the Bill quote above. I renamed my original SP3000.exe to SP3000.exe.orgDriver in the bin directory and copied the new SP to that folder.

With that; the “hack” is complete. Now let’s test to make sure your programmer will function with it’s new Win10 64bit host. To do this; double click the new SP3000.exe and it should automatically detect the programmer (assuming it’s plugged in and turned on) with the new ezUsb driver. With no chips in the ZIF socket; follow the Xeltek instructions contained in the readme.txt file… regurgitated here:

Type “Xeltek” under search when choosing a device on your software. Under device name choose “####..222…“. Run all the test functions except “test_type“.

Each function should return OK! indicating the test passed. Here’s a screenshot of my completed test runs:

Hope this helps someone in the future.