Forums

WTB: EPROM Emulator for 2716

Started by TXMarsh September 30, 2010
"TXMarsh" <timothymarsh@gmail.com> wrote in message news:0be0fe0e-b928-4c85-b8db-b74543c1287a@30g2000yqm.googlegroups.com...
> Does anyone have an emulator for a 2716 eprom that they no longer have > a use for? > In the alternative, does anyone know if anyone is still making these? > Thanks. > Tim
You can try to find 2816 device (EEPROM pin compatible with 2716), so there will be no need for erasure and writing is also faster... I've used them for development at the time... - while(1);
"TXMarsh" <timothymarsh@gmail.com> wrote in message 
news:ac1af224-f55a-4fe7-8eda-2cfe5523d344@a19g2000yql.googlegroups.com...

> I thought about making my own with a propeller micro but I need to > start being more careful about "project creep."
Why worry? I often find the spinoff projects to be more useful than the original aim. Necessity is the mother of invention ...
> I've been on a real retro-computing kick... > reading too many old issues of BYTE!
Me too. It's much more effective than taking the rejuvenation pills ;-) Cheers, Chris Chris Burrows Astrobe v3.2: ARM Oberon-07 Development System http://www.astrobe.com
"TXMarsh" <timothymarsh@gmail.com> wrote in message 
news:0be0fe0e-b928-4c85-b8db-b74543c1287a@30g2000yqm.googlegroups.com...
> Does anyone have an emulator for a 2716 eprom that they no longer have > a use for? > In the alternative, does anyone know if anyone is still making these? > Thanks. > Tim
I have a Dataman Softy S4 - yours for &#2013266083;??? - make an offer by email if you are interested. It supports 2716 and you can still download code and eprom signatures from their website. It programs and emulates and has the emulator lead. Michael Kellett www.mkesc.co.uk
On Thu, 30 Sep 2010 19:16:37 -0700 (PDT) TXMarsh <timothymarsh@gmail.com>
wrote in Message id:
<ac1af224-f55a-4fe7-8eda-2cfe5523d344@a19g2000yql.googlegroups.com>:

>Thanks for looking Jon! Yep... just trying to avoid having to burn, >UV erase and burn again.
Here you go, this should work nicely: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=CAT28C16ALI90-ND They're electrically erasable. As long as your programmer supports the part... There's lots of other sources as well. Use "28C16" in your query here: http://www.findchips.com/
All... thanks for all the info!

Jon... thanks for the tip on the 6800 development harware.

while(1) and JW... thanks for the idea about the 2816.

: )

Tim

TXMarsh wrote:

> Thanks for looking Jon! Yep... just trying to avoid having to burn, > UV erase and burn again. > I thought about making my own with a propeller micro but I need to > start being more careful about "project creep." > That is, it always seems that I have an idea to do something (in this > case design a test rig with custom software for a 6800 based pinball > machine) and then I decide I could do the project more efficiently if > only I build another widget first. > I would also be interested in most any tool that works with the > motorola 6800/6802/6808. I've been on a real retro-computing kick... > reading too many old issues of BYTE! > tim
Might depend on where you are and if one that works for bigger EPROM's could be adapted in some way to give you what you need. I have a pair that I think do up to the 512k size (will have to check) that run from the parallel ports. Made by Computer Solutions Ltd some years back. -- ******************************************************************** Paul E. Bennett...............<email://Paul_E.Bennett@topmail.co.uk> Forth based HIDECS Consultancy Mob: +44 (0)7811-639972 Tel: +44 (0)1235-510979 Going Forth Safely ..... EBA. www.electric-boat-association.org.uk.. ********************************************************************
Hi Paul... thanks for the reply.  I'm in the US (Texas).  From what I
can tell most emulators that did 512 also did smaller eprom emulation
but sometimes they only emulated down to 2732s... but some do emulate
2716s... so kinda depends on the exact model.  Not a real expert on
2716s v. 2732s but there may be some fundamental difference (besides
size).
On Fri, 1 Oct 2010 13:12:17 -0700 (PDT), TXMarsh
<timothymarsh@gmail.com> wrote:

>Hi Paul... thanks for the reply. I'm in the US (Texas). From what I >can tell most emulators that did 512 also did smaller eprom emulation >but sometimes they only emulated down to 2732s... but some do emulate >2716s... so kinda depends on the exact model. Not a real expert on >2716s v. 2732s but there may be some fundamental difference (besides >size).
My recollection is that that was a nice period of time where most of the time most of the different sizes were voltage and pin compatible. But that might very well have been at or above the x32 size. The x16 might be different in some way. I'd have to go to a datasheet again, to know. Memory fails. Your point is wise to hold in mind, lacking specifics, while looking around. Jon
On Oct 1, 11:46=A0pm, Jon Kirwan <j...@infinitefactors.org> wrote:
> On Fri, 1 Oct 2010 13:12:17 -0700 (PDT), TXMarsh > > <timothyma...@gmail.com> wrote: > >Hi Paul... thanks for the reply. =A0I'm in the US (Texas). =A0From what =
I
> >can tell most emulators that did 512 also did smaller eprom emulation > >but sometimes they only emulated down to 2732s... but some do emulate > >2716s... so kinda depends on the exact model. =A0Not a real expert on > >2716s v. 2732s but there may be some fundamental difference (besides > >size). > > My recollection is that that was a nice period of time where > most of the time most of the different sizes were voltage and > pin compatible. =A0But that might very well have been at or > above the x32 size. =A0The x16 might be different in some way. > I'd have to go to a datasheet again, to know. =A0Memory fails. > > Your point is wise to hold in mind, lacking specifics, while > looking around. > > Jon
There was no difference between the 16 and 32 from a read point of view, just A11 was added. I think on the 2716 it was the programming voltage pin, but this may be wrong (I have not been designing eprom programmers which would program these for well over 20 years :-) ). But I am quite sure the 32 can "drop in" replace a 16 if the data are written in its upper half (Vpp for the 16 is held at 5V during read and this is where A11 is). Dimiter ------------------------------------------------------ Dimiter Popoff Transgalactic Instruments http://www.tgi-sci.com ------------------------------------------------------ http://www.flickr.com/photos/didi_tgi/sets/72157600228621276/
On Fri, 1 Oct 2010 16:39:17 -0700 (PDT), Didi
<dp@tgi-sci.com> wrote:

>On Oct 1, 11:46&#2013266080;pm, Jon Kirwan <j...@infinitefactors.org> wrote: >> On Fri, 1 Oct 2010 13:12:17 -0700 (PDT), TXMarsh >> >> <timothyma...@gmail.com> wrote: >> >Hi Paul... thanks for the reply. &#2013266080;I'm in the US (Texas). &#2013266080;From what I >> >can tell most emulators that did 512 also did smaller eprom emulation >> >but sometimes they only emulated down to 2732s... but some do emulate >> >2716s... so kinda depends on the exact model. &#2013266080;Not a real expert on >> >2716s v. 2732s but there may be some fundamental difference (besides >> >size). >> >> My recollection is that that was a nice period of time where >> most of the time most of the different sizes were voltage and >> pin compatible. &#2013266080;But that might very well have been at or >> above the x32 size. &#2013266080;The x16 might be different in some way. >> I'd have to go to a datasheet again, to know. &#2013266080;Memory fails. >> >> Your point is wise to hold in mind, lacking specifics, while >> looking around. >> >> Jon > >There was no difference between the 16 and 32 from a read point of >view, just A11 was added. I think on the 2716 it was the programming >voltage pin, but this may be wrong (I have not been designing eprom >programmers which would program these for well over 20 years :-) ). >But I am quite sure the 32 can "drop in" replace a 16 if the data >are written in its upper half (Vpp for the 16 is held at 5V >during read and this is where A11 is). > >Dimiter
Okay. Always good to sweep away a little ignorance and/or recover some lost memory. ;) Thanks, Jon