[sdiy] working with EPROMs

[Speth, John]

> I've been looking at some 70s delay schematics that use EPROMs to
> create all of their timing signals for the converters and rams and
> everything and it makes me wonder how you create the data for
> those. I have a burner, but the only way I know of to create the
> binary files is with the Wiard/Darwin Grosse WAVE256 application.
> I mean, if I made some graph paper with 256 lines each way I could
> draw the timing that I want and then enter it line by line into
> WAVE256 in the "Numeric" section, but there has to be a better
> way. My googling has not gotten me anywhere. Does anyone have any
> suggestions? Chris Moore, the man behind  Ursa Major, mentions
> punch cards in his history section, but there must be some
> software...other than just HEX editors... right?

Editing by hand would be the last way you would want to do that.  You'd probably make a mistake that will be impossible to debug.

The way I'd do it is to write a desktop program of some sort that will generate the output file containing the data that you desire.  The output could either be generated with no input file (rules implemented in code) or, if you have the time and ability, take some kind of timing diagram file input (invent your own for simplicitys' sake).  The latter method requires a bit more up-front effort but you get a lot of flexibility when it's done.  It's not a small job, for sure.

The nice thing is that just about any programming language would do the trick (perl, C, basic, etc).

JJS


The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. If you are not the intended recipient you are hereby (a) notified that any disclosure, copying, distribution or taking any action with respect to the content of this information is strictly prohibited and may be unlawful, and (b) kindly requested to inform the sender immediately and delete any copies. Coherent is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.