Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!spool.mu.edu!mips!pacbell.com!tandem!zorch!vsi1!teda!netcomsv!mcmahan
From: mcmahan@netcom.COM (Dave Mc Mahan)
Newsgroups: comp.sys.m68k
Subject: Re: Programming Roms/Eproms/Pla/etc
Message-ID: <1991Apr27.060346.25929@netcom.COM>
Date: 27 Apr 91 06:03:46 GMT
References: <91107.091241SCP100@psuvm.psu.edu>
Organization: Dave McMahan @ NetCom Services
Lines: 34


 In a previous article, SCP100@psuvm.psu.edu (STEPHEN POLKOWSKI) writes:
>Hi all,
>
>       I would like to develop my own eprom programmer using a 68000 family pro
>cessor.  My question is: where does one find the specs for programming memory c
>hips? Do the manufactures publish specs on how to program their chips?  Any
>information would be appreciated.

As far as I know, they only definative place to find the techno-info you seek
is in the data book from each manufacturer.  I know that Intel algorithms for
writing are different than Hitachi, for instance.  Programmers like Data I/O
use different algorithms for each type of EPROM, as some EPROMs burn faster
than others.  I would suggest you order the data book or data sheet on each
part you are interested in supporting from the maker.  Although this is a 
pain to do, it is usually free.  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.


>Thanks,
>Steve

   -dave

-- 
Dave McMahan                            mcmahan@netcom.com
					{apple,amdahl,claris}!netcom!mcmahan