USB Programmer for EPROM 27C, (27C256, 27C512, etc.)

Product Information

If it takes more than one erase-cycle for them to become blank, count the number of 10-minute cycles for them to become blank, then double that erase time. Super fast industrial gang programmer with four independent modules, ISP capabilities and USB 2.0 connectivity. The 448Pro2AP is built to meet the demands of high volume production programming with automated handlers and ATE machines... If you have a dedicated EEPROM programmer this is not a problem, the programmer will handle the data protection for you, but many hobbyists prefer to save a few pennies and using Ben’s own breadboard EEPROM programmer. My original ‘BenPrommmer’ with 28C16 EEPROM

Choosing a programmer ( Note: this is what I used in 2012, when this article was written. I'm sure there are better solutions out there nowadays!) You might want to use your EPROM programmer to read a mask ROM to see if it's damaged. As mentioned above, unless the mask ROM is pin compatible with an EPROM that the programmer supports you'll need to make an adapter first to switch the mask ROMs pins to those matching the supported EPROM. Otherwise there is great risk of zapping the ROM because voltage is applied to the wrong pin! If anyone else is trying to use one of these on a modern PC with a serial port, you can use PROMPROG in DOS box or the windows version in VirtualPC (only tested on win7 before fixing the cable). The DOSBox option is much better as it boots in about 1 second and the config file contains an AUTOEXEC.BAT so PROMPROG will start immediately and DOSBox close when the program does. Since I’ve already written code to write to a chip with software data protection via a Z80 I thought it would be helpful to update my own ‘BenPrommer’ to handle the 28C256 and to document both the hardware and software changes needed. Hardware Changes Mike, your intro nails my situation. I’ve built Ben’s 8-bit computer and am working on an expanded version using AT28C256 chips. I only stumbled onto SDP a couple of days ago by using a TL866ii Plus programmer, experimenting with the EEPROM I so far could not write to, and then later was able to write to the chip using Ben’s programmer (already modified to fit the AT28C256). My brisk research turned up a number of references but yours stood out. However, I’ve now made the HW changes and have tried to get your code to work with it but nothing I’ve tried seems to result in disabling SDP, including adding capacitors to my board. Additionally, when I ran your code as is, I was able to discover that without manipulating /CE, a read after write was actually always returning the value that had last been written, and, in fact, nothing had been written to the EEPROM. This was verified by making sure /CE was low when reading and the actual contents of the EEPROM were returned. Have you been able to verify the contents of your one AT28C256 separately from your sketch code? On the other hand if you DID actually get it to work, I’m curious as to what I am overlooking and would welcome any additional insights you may have. NOTE: Although I do have a separate EEPROM programmer, I really want to get the BenEater version working for this.

Why is MCM68766 difficult to program?

Auto Increment of Serial Numbers Auto-generation of electronic serial numbers is available on Superpro 610P. This feature is implemented by setting Auto Increment in Operation Option. Auto Increment allows users to add unique serial number into the device. After each successful programming, the software automatically changes the value by the specified increment mode. BAW574252, GRM-003, GRM-004, GRM-005, KKZ-06F, MCM2814, PCA8581, PCF8581, PCF8582, PCF8594, PCF8598, PCF85102, PCF85116, SDA2516, SDA2526, SDA2546, X24C00, X24C01 Read-Only Memory ( ROM) is a type of computer memory which, generally speaking, is only programmed once (or very occasionally) and then gets read from the rest of the time. This is because it's very slow — or impossible — to write new data to ROM. The trade-off for very slow write times — traditionally — is that it's also non-volatile meaning that the data doesn't go away when power is removed from the device. This makes it ideal for things like firmware which need to be "remembered" by the computer, but never actually change. The BIOS in your PC is stored on a form of ROM. A Brief History of ROM What I'm thinking of doing is double-programming them. Program each chip as normal and ensure they verify okay. Wait a day, then verify again. If they verify properly, then program them again (and verify). So try a test file made up of 0XFE, 0xFD, 0xFB, 0xF7, 0xEF, 0xDF, 0xBF, 0x7F, 0x00 ensuring that you use a ‘blank’ EPROM. That way, it may be possible to work out if all bits are affected or just one or some are affected.

I'd like comments on the above. This has worked well for me in the past but I'd like the guidance of people smarter than myself. It has a better monitoring function as the usual ones (voltage, signal strength & everything else). I think it is easy to fall in love with it, if you can accept the missing extras: It won’t tell you which adapter to use like the O5 & VVDI does, but has such extras, what the others not: Oscilloscope function, live monitoring and so on. Works slower as the others, but the result is first class. MC68HC912B32, MC68HC912BE32, MC68HC912D60, MC68HC912D60A, MC68HC912DC128A, MC68HC912DG128, MC68HC912DG128A They are ones I got with a whole bunch of other stuff when I bought a job lot of BBC stuff. So my idea is to build the programmer from the beebug magazine and see if I can use those that I already have. I qoukd of course need to erase them first using a UV box.First rule is to know the kind of EPROMS you want (or are likely to want) to burn and get a programmer that can handle them. There are a number of programmers on the market. Beware though, as many modern ones will not handle the smaller capacity ICs like the 2716 and 2732 ones found in very old microcomputers.