These are the files I used to create my ATF22V10C programmer.

If you're hoping to easily build something and just use these files as-is, go
ahead and delete this shit right now before you waste any more time.

I have *weird* ways of doing stuff that are entirely incompatible with the
rest of the world.  That's why I initially didn't post anything about my
design:  No one would be able to reproduce it anyway.  So the only thing I had
to offer was the knowledge of how the programming process works.

http://www.ecstaticlyrics.com/electronics/ATF22V10C/

Anyway, here's what's in this file:

programmer_with_notes.jpg - A picture of the programmer with some notes about
its functionality.  No schematic is provided because you'd seriously be better
off just designing your own.

gal_programmer.asm - The code that goes in the ATtiny48.  This is totally
non-standard, as it is written for an assembler I wrote myself which is unlike
any other assembler you've ever used, unless perhaps you've used my "Sarcasm
Z80 Assembler," in which case there's some resemblence there.

attiny48.asm - A "header file" used by gal_programmer.asm.

awful.pl - My AVR assembler.  There's zero chance you want to use this.

avr.bin - The assembled code for the ATtiny48.  Again, this is a non-standard
format, as I built my own programmer too.  This is just the raw data that goes
into the chip, nothing more.

avr.bs - Tiny file used by my programmer.  The first two bytes are the number
48 so that it knows what kind of chip the code is compiled to.  The next three
bytes are EE, DF, and FF, the values for the three fuse bytes in the ATtiny48.

GAL Programmer.pl - The Perl script that communicates with the ATF22V10C
programmer.  I have zero idea whether this will even work outside of Linux.
Indeed, it's been months since I've used it and so I don't recall whether it
takes a JEDEC file as a command-line argument or if it only reads from a
specific file name.  At the very least it must be modified to know the correct
/dev/ device name for the FT240X.  Again, you probably don't want to use this,
but rather just write your own and only look at this if you become desperate
to understand what your own software is doing differently than mine.

Anyway, good luck with making use of this junk...
