Help! Eprom Programmer!

endrien

Member
Joined
Aug 19, 2009
Messages
932
Reaction score
1
Location
Canada
I'm trying to get my EP-1 eprom programmer to work, it shows up in the software and I can look at the hex code of the eprom, I can see the checksum, but I can't save it as a file or verify it. If I try to save it, it says too many errors detected. If I try to verify it, it says ep-1 has stopped responding. Please help.
I don't currently have any erased eproms to try to test programming.

Video:
http://www.youtube.com/watch?v=YDn9JMygWwo
 
My Ep-1140 just flat out rocks in Xp. I checked my BPWSoft-03 to see if it would work with the Ep-1 and it doesn't.

It was an idea... Have you tried a regular old modem cable? Ratshack has them for less than a ten spot. Maybe one wire on yours is not acting right.
 
My Ep-1140 just flat out rocks in Xp. I checked my BPWSoft-03 to see if it would work with the Ep-1 and it doesn't.

It was an idea... Have you tried a regular old modem cable? Ratshack has them for less than a ten spot. Maybe one wire on yours is not acting right.
'

The EP-1 Only accepts serial. It uses DOS only software which is specific to the EP-1(I have the correct software). I'm thinking maybe a transfer wire or something is messed up or the cable is not right as the programmer show's no signs of trouble with tests.
I've tried using a printer cable but like I said, it only works with serial(COM1) not LPT.
I need to try and get an older computer with a 25 pin serial connection maybe.
 
'

The EP-1 Only accepts serial. It uses DOS only software which is specific to the EP-1(I have the correct software). I'm thinking maybe a transfer wire or something is messed up or the cable is not right as the programmer show's no signs of trouble with tests.
I've tried using a printer cable but like I said, it only works with serial(COM1) not LPT.
I need to try and get an older computer with a 25 pin serial connection maybe.

Oh wait, you said modem cable. I haven't tried one of those yet, that's what I had went to the source(canadian version of radioshack) trying to get a modem cable but they didn't have it. I found that another local store should have one so I'll try that. One of the wires may be loose or shorted on that cable that I made, I was waiting to get my Hakko soldering station in the mail so I had to use my beat up radio shack iron that's tip was completely messed.
 
There's a post here in the past few days where someone posted the proper EP-1 software link. That might help...
 
You need a 25 pin straight through cable IIRC. A lot of standard modem and serial cables won't work because they don't use all of the lines. Someone who had one also said something about USB to Serial ports not working right either.

ken
 
There's a post here in the past few days where someone posted the proper EP-1 software link. That might help...

You need a 25 pin straight through cable IIRC. A lot of standard modem and serial cables won't work because they don't use all of the lines. Someone who had one also said something about USB to Serial ports not working right either.

ken

I've got the same software originally included on the floppy disks, thats not the problem.
I've been trying to get my hands on a computer with a 25 pin serial, they don't seem to be common. The manual says it accepts 9 and 25pin serial.

I emailed BP and they said:
If this is the same PC that you have always used with this programmer successfully, then my hunch is that the programmer has given up...unless the serial port or cable is bad. Otherwise, it is possible that you need to slow your communication rate(see the manual).

Which to me makes me think it is the cable/port and not the programmer as the programmer wouldn't pass tests if it was broken.
 
With a modem cable it doesn't even recognize the EP-1 so yeah, I guess it doesn't use the right pins. Looks like I'm going to need to try a 25 pin to 25 pin serial.

Apparently I need a different pinout, being
PC (DB-25) EP-1
TxD (2) ---> TxD (2)
RxD (3) <--- RxD (3)
RTS (4) ---> RTS (4)
CTS (5) ---> CTS (5)
DSR (6) <--- DSR (6)
GND (7) ---- GND (7)
DTR (20) --> DTR (20)

PC (DB-9) EP-1
TxD (3) ---> TxD (2)
RxD (2) <--- RxD (3)
RTS (7) ---> RTS (4)
CTS (8) ---> CTS (5)
DSR (6) <--- DSR (6)
GND (5) ---- GND (7)
DTR (4) ---> DTR (20)

I tried that pinout with DB9, it didn't seem to recognize the programmer.
 
Last edited:
I can't seem to find a computer with 25pin serial, any other suggestions?
 
I don't think it is the cable since your tests are all working correctly. My odds up front were on it being a problem with the COM port like a resource conflict. After watching your video I'm wondering if it is actually a problem with Windows 95.

Have you tried using straight DOS like 6.22 or something pre-Win95?

Have you tried making a PIF file for your EP software to run it under Win95?

If you haven't done either of those, I would start with the PIF file creation. Can't quite remember how to create one, but I think you make shortcut to the application and mess with the properties and it will allow you to do all sorts of limitations so that the DOS application doesn't know it is running under windows. Obviously booting directly to DOS would also negate the need for the PIF file. There is a PIF editor in the default windows install if I remember correctly.

Anyway, try those out... You have enough disk space where you are trying to save the HEX file? Just want to make sure you are not trying to save the file to a locked floppy or something like that. I agree with your sentiment that it looks like it should be working since you can dump the image and checksum the ROM. That's why I am suspecting a file problem. You might add some file handles in your config.sys if you have not done so already. Here is a link to Microsoft's site... This is for ME, but it talks about adding file handles to Config.sys for pre-windows apps and windows VM's once windows is running.

http://support.microsoft.com/kb/269030
 
I don't think it is the cable since your tests are all working correctly. My odds up front were on it being a problem with the COM port like a resource conflict. After watching your video I'm wondering if it is actually a problem with Windows 95.

Have you tried using straight DOS like 6.22 or something pre-Win95?

Have you tried making a PIF file for your EP software to run it under Win95?

If you haven't done either of those, I would start with the PIF file creation. Can't quite remember how to create one, but I think you make shortcut to the application and mess with the properties and it will allow you to do all sorts of limitations so that the DOS application doesn't know it is running under windows. Obviously booting directly to DOS would also negate the need for the PIF file. There is a PIF editor in the default windows install if I remember correctly.

Anyway, try those out... You have enough disk space where you are trying to save the HEX file? Just want to make sure you are not trying to save the file to a locked floppy or something like that. I agree with your sentiment that it looks like it should be working since you can dump the image and checksum the ROM. That's why I am suspecting a file problem. You might add some file handles in your config.sys if you have not done so already. Here is a link to Microsoft's site... This is for ME, but it talks about adding file handles to Config.sys for pre-windows apps and windows VM's once windows is running.

http://support.microsoft.com/kb/269030

I'm a bit confused with how to make a PIF file, I haven't tried anything pre win95 because I don't have any floppy disks and would need to use a CD drive in DOS.
And yes I have enough space. The programmer also locks up when I try to verify an eprom, which could be explained with file permissions being wrong.

MrSalvage my computer has PCI ports not ISA XD. But I'll look at ebay for some 25pin PCI cards to see the price.
 
I'm a bit confused with how to make a PIF file, I haven't tried anything pre win95 because I don't have any floppy disks and would need to use a CD drive in DOS.
And yes I have enough space. The programmer also locks up when I try to verify an eprom, which could be explained with file permissions being wrong.

MrSalvage my computer has PCI ports not ISA XD. But I'll look at ebay for some 25pin PCI cards to see the price.

Microsoft has the steps on their site.

http://support.microsoft.com/kb/131877

I would try this out before spending cash on a new io card. This example shows you how to do the pif file for command.com. That is what will give you a dos shell. You could do a pif for that or make one for the exe or com file you use with the programmer. If there is more than one executable file, just do one for command.com.

Enable/disable the features that protect e dos app from knowing it is running under windows. Pre-windows apps can be pretty picky about running under windows. So do things like force full screen mode, etc.

Once you have a PIF file, that is what you will launch to access your programmer.
 
Microsoft has the steps on their site.

http://support.microsoft.com/kb/131877

I would try this out before spending cash on a new io card. This example shows you how to do the pif file for command.com. That is what will give you a dos shell. You could do a pif for that or make one for the exe or com file you use with the programmer. If there is more than one executable file, just do one for command.com.

Enable/disable the features that protect e dos app from knowing it is running under windows. Pre-windows apps can be pretty picky about running under windows. So do things like force full screen mode, etc.

Once you have a PIF file, that is what you will launch to access your programmer.

I tried using the software in just plain old dos that I installed on my computer, it gives the same thing. It is not the cable. It probably has to do with the settings. I also tried using it in a terminal emulator, the manual says to start file capture(not sure what this is) as when I type RH it lists the data on the eprom.
 
I tried using the software in just plain old dos that I installed on my computer, it gives the same thing. It is not the cable. It probably has to do with the settings. I also tried using it in a terminal emulator, the manual says to start file capture(not sure what this is) as when I type RH it lists the data on the eprom.

I believe it supports XModem download. Back in the day you had to hit a command key sequence depending on terminal program and tell it to receive a file via XModem. The terminal program would capture all of the bytes to a file for you. The XModem is the protocol used to transfer the binary data over the serial link. So just look in the help for the program you are using.
 
Ensure your firewall is disabled. Honestly I'm not sure how XP's firewall reacts to serial communication but better to be safe than sorry.

Disable ANY and all anti malware or virus scanning software.

If this fails then slow down the com port. Go into Device manager, find your com port and go into advanced settings. IIRC you'll have an option to change the speed. Typically the settings are 9600baud, 8, none and 1.
 
Ensure your firewall is disabled. Honestly I'm not sure how XP's firewall reacts to serial communication but better to be safe than sorry.

Disable ANY and all anti malware or virus scanning software.

If this fails then slow down the com port. Go into Device manager, find your com port and go into advanced settings. IIRC you'll have an option to change the speed. Typically the settings are 9600baud, 8, none and 1.

There is no anti virus and firewall is disabled. The programmer automatically sets the baud rate, but the terminal emulator sets it to 9600.

I'll try that update that was posted.
 
Back
Top Bottom