Newsgroups: alt.comp.hardware.homebuilt,comp.robotics,sci.electronics
Path: cantaloupe.srv.cs.cmu.edu!nntp.club.cc.cmu.edu!godot.cc.duq.edu!ddsw1!redstone.interpath.net!hilbert.dnai.com!nic.scruz.net!earth.armory.com!rstevew
From: rstevew@armory.com (Richard Steven Walz)
Subject: Re: EPROM, ser-par-EEPROM, PIC programmer damn near FREE!!
Organization: The Armory
Date: Sat, 7 Jan 1995 13:36:34 GMT
Message-ID: <D21F59.8K@armory.com>
References: <3ea4sp$jcg@eis.calstate.edu> <3ebkvo$7k7@jabba.cybernetics.net> <D1vw61.ALM@armory.com> <3eeh09$4pk@kocrsv08.delcoelect.com>
Sender: news@armory.com (Usenet News)
Nntp-Posting-Host: deepthought.armory.com
Lines: 56
Xref: glinda.oz.cs.cmu.edu comp.robotics:16750 sci.electronics:114331

In article <3eeh09$4pk@kocrsv08.delcoelect.com>,
Jim Buchanan <c22jrb@kocrsv01.delcoelect.com> wrote:
>
>In article <D1vw61.ALM@armory.com>, rstevew@armory.com (Richard Steven Walz) writes:
>[...]
>> different devices out of the parallel port, which *I* maintain is the best
>> HOME use of I/O, even if screwing an RS232C onto it IS very froody! (And it
>> deals with the poor Mac owner's needs as well!!) Like I always say, the
>> serial port is for pre-made devices that have that interface, and the
>> parallel port is for the stuff you will just use for your own HOME-SHOP
>> stuff, because it is SO simple!!! The best of both worlds would be a PD
>> schematicized multiport board that was serial and served lots of bench-top
>> I/O bits and could be easily configured with a cheezy menu driven prog
>> which is PD source available! And have code in assembly, C, and BASIC!
>
>I like your thinking here Steve. I'm in the middle (Yes for those of you I
>talked to in the middle of last year, I'm *very* slow on home projects :-)
>) of bread-boarding an EPROM programmer that runs off the parallel
>port. Perhaps I'll re-think my approach and build a universal I/O board
>that can be used for programming and many other things as well.
>
>[...]
>> for device programming. Let's face it. Yes, code can be written, and
>> programmers can be built to program a device in an incredibly short time!
>> However, NONE of the microcontrollers, PIC's or other, and none of the
>> EEPROM's and EPROM's, and none of the GAL's and PAL's DEMAND to be
>> programmed fast!!! That it could take a couple minutes to do a device
>> wouldn't mess with our minds too badly for the chance to do it all with
>> a minimal amount of equipment soldered together with homebrew cheeze board
>> methods! And then you have the I/O system that the loonies SHOULD have
>> built into the IBM/clone and into the Mac!!!
>> -Steve Walz   rstevew@armory.com
>> 
>
>I think my estimate was about 10 minutes for an 8K EPROM. I remember getting
>10 minutes when I did the calculation last August or so, I *think* I used
>an 8K EPROM for may example. My notes are all at home, so I can't look them
>up fast.
>
>I'll try to keep everyone updated, but don't expect speed, I've got at
>least 4 other projects going, and only have about six hours/week for
>electronic/computer hobby stuff.
>Jim Buchanan     c22jrb@kopt0002.delcoelect.com     jbuchana@holli.com
>'73 BMW R75/5                   "Frau Bluecher"
-------------------------------------------
Jim, I wouldn't want to burst your bubble, but even old BASIC is perfectly
able to run a separate simple machine language program by shelling out
control, or to use the old USR command to run a machine code program within
BASIC, or GWBASIC, or QBASIC or QuickBASIC! And it runs much faster than
that! I have programmed old plain 2764's (8K x 8) in under one minute
easy! And plain verification is only 5 seconds! Homebrew does NOT have to
be slow! There is a built-in inherent slowness to the algorithm used by ALL
makers of EPROM programmers, and it's the same one the home builder is
subject to, no more! And using the newer smart algorithms is even faster!
-Steve Walz   rstevew@armory.com

