Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!daver!ditka!teda!netcomsv!mcmahan From: mcmahan@netcom.COM (Dave Mc Mahan) Newsgroups: comp.sys.m68k Subject: Re: Programming Roms/Eproms/Pla/etc Message-ID: <1991Apr30.203046.6669@netcom.COM> Date: 30 Apr 91 20:30:46 GMT References: <91107.091241SCP100@psuvm.psu.edu> <1991Apr27.060346.25929@netcom.COM> Sender: netnews@netcom.COM (USENET Administration) Organization: Dave McMahan @ NetCom Services Lines: 39 In a previous article, mcmahan@netcom.COM (Dave Mc Mahan) writes: [ Discussion about wanting to build a EPROM programmer and needing chip specs deleted. ] >Data I/O has literally hundreds (if not >thousands) of supported part numbers listed in their books. It would be >especially nice of you to just read the EPROM ID code from a chip and select >the appropriate alogorithm. I don't know why Data I/O doesn't do this >automatically, but they don't. It KNOWS the proper ROM ID code for the >chip in the socket, why don't they just use the right algorithm? I guess >it could be difficult to even select the proper socket (the Data I/O 29B >programmer has 6 or 8 sockets, all different sizes) and read the ID code >without risking damage to the chip, but it would be nice if they could. Well, sports fans, this is another time when I have the honor of following up my own posting. I did a little research on the above paragraph, and found that a Data I/O programmer does indeed have the intelligence to properly program an EPROM if you just stick it in the socket. You don't _HAVE_ to enter the family and pinout code for a new part, which can save you some time looking up the desired value. It turns out that if you enter the family/pinout code of 'FFFF' when asked, the Model 29B programmer (from Data I/O) will correctly find the right socket, figure out what part type is in there, and program it. Just thought you might want to know. > -dave -dave -- Dave McMahan mcmahan@netcom.com {apple,amdahl,claris}!netcom!mcmahan