Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!bevis
From: bevis@en.ecn.purdue.edu (Jeff Bevis)
Newsgroups: comp.sys.m68k
Subject: Re: Programming Roms/Eproms/Pla/etc
Message-ID: <1991Apr30.074218.3023@en.ecn.purdue.edu>
Date: 30 Apr 91 07:42:18 GMT
References: <91107.091241SCP100@psuvm.psu.edu> <1991Apr27.060346.25929@netcom.COM>
Organization: Purdue University Engineering Computer Network
Lines: 36

In article <1991Apr27.060346.25929@netcom.COM> mcmahan@netcom.COM (Dave Mc Mahan) writes:
>
> 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
>>chips? 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

While I hate to prolong a thread which is probably inappropriate to this
group, I have to take the opportunity to ask... Why is it that manufacturers
don't like to include device programming data for GALs/PALs/etc in their
databooks?  In the National "Programmable Logic Devices Databook and Design
Guide," the following phrase is frequently repeated:

	"This section alone, however, does not contain sufficient
	 information to implement the GAL programming algorithm."

The book goes on to suggest that the user contact the National Programmable
Device Support department.  Why not just put it in the book?  AMD's books
are just as mysterious.  How can they expect a poverty-stricken college
student like me to build a GAL programmer if the data is not readily
available?  Well, anyway, I might just end up making some phone calls to
National on this.  But, if anyone knows of any good reference material I
should be reading, please let me know!


-- 
+---------------------------+-------------------------------------------------+
|Jeff Bevis / Purdue EE     |      Three is never equal to four, except       |
|bevis@ecn.purdue.edu       |        for very large values of three...        |
+---------------------------+-------------------------------------------------+