25 Dec
2009
25 Dec
'09
2:34 a.m.
Does anyone have a stash of them? I have one fo them and it is getting old
burning it, testing the device, erasing it, and burning different code into
it, lather ? rinse ? repeat.
25 Dec
25 Dec
2:43 a.m.
On Fri, 25 Dec 2009 09:04:59 pm Geoffrey Reed wrote:
Does anyone have a stash of them? I have one fo them
and it is getting old
burning it, testing the device, erasing it, and burning different code into
it, lather ? rinse ? repeat.
Perhaps you could use an EEPROM? I use them for just about everything because
I don't have an eraser.
If pins compatibility is an issue, you can put the EEPROM into two machine
sockets stacked on top of each other, then break off the pins from the middle
socket and route wires to where they should go.
Alexis.
12:58 p.m.
Alexis wrote:
On Fri, 25 Dec 2009 09:04:59 pm Geoffrey Reed wrote:
One of the Dallas devices (Maxim these days) would work well for you,
Geoffrey - and most eprom programmers can erase and reprogram them -
actually you just dump the fresh data in, it simply over-writes the old.
Data retention of 10 years at a minimum, when you are happy with the
code then burn to a 2732 (I have lots of them if you are near Vancouver,
BC).
http://para.maxim-ic.com/en/search.mvp?fam=memory&489=NV%20SRAM&232…
John :-#)#
--
John's Jukes Ltd. 2343 Main St., Vancouver, BC, Canada V5T 3C9
Call (604)872-5757 or Fax 872-2010 (Pinballs, Jukes, VideoGames)
www.flippers.com
"Old pinballers never die, they just flip out"
Does anyone have a stash of them? I have one fo
them and it is getting old
burning it, testing the device, erasing it, and burning different code into
it, lather ? rinse ? repeat.
Perhaps you could use an EEPROM? I use them for just about everything because
I don't have an eraser.
If pins compatibility is an issue, you can put the EEPROM into two machine
sockets stacked on top of each other, then break off the pins from the middle
socket and route wires to where they should go.
Alexis.
5:16 a.m.
--- On Fri, 12/25/09, Geoffrey Reed <geoffr at zipcon.net> wrote:
Does anyone have a stash of
them?? I have one fo them and it is getting old
burning it, testing the device, erasing it, and burning
different code into
it, lather ? rinse ? repeat.
This guy does:
www.epromman.com
-Ian
7:08 a.m.
On Dec 25, 2009, at 5:34 AM, Geoffrey Reed wrote:
Does anyone have a stash of them? I have one fo them
and it is
getting old
burning it, testing the device, erasing it, and burning different
code into
it, lather ? rinse ? repeat.
I have some. Send me your shipping address if you still need them.
And, Merry Christmas!
-Dave
--
Dave McGuire
Port Charlotte, FL
10:16 a.m.
On 25 Dec 2009 at 2:34, Geoffrey Reed wrote:
Does anyone have a stash of them? I have one fo them
and it is
getting old burning it, testing the device, erasing it, and burning
different code into it, lather ? rinse ? repeat.
Futurlec has them (2732, 32A and C32) as well as the 16's:
http://www.futurlec.com/ICEPROM.shtml
I've been dealing with Futurlec for years and find their service
fairly prompt and their communication very good, even if they are in
Thailand.
--Chuck
11:03 a.m.
On Fri, 25 Dec 2009, Chuck Guzis wrote:
I've been dealing with Futurlec for years and find
their service
fairly prompt and their communication very good, even if they are in
Thailand.
Their web site shows a location at 1133 Broadway in NYC. Have budget
issues forced Manhattan to relocate? :-)
Steve
--
26 Dec
26 Dec
8:39 a.m.
On 25 Dec 2009 at 14:03, Steven Hirsch wrote:
Their web site shows a location at 1133 Broadway in
NYC. Have budget
issues forced Manhattan to relocate? :-)
I have never received a thing from the NYC location. My packages
always bear a Thai return address. Sometimes they're sent from
Bangkok, but lately, they've been shipped from Hongkong. I suspect
that the super-cheap China-to-US shipping (you could never ship in
the reverse direction for a like amount. Some "free" trade...) is
very attractive to them.
--Chuck
27 Dec
27 Dec
7:03 a.m.
On Fri, 25 Dec 2009 02:34:59 -0800
Geoffrey Reed <geoffr at zipcon.net> wrote:
I have one fo them and it is getting old
burning it, testing the device, erasing it, and burning
different code into it, lather ?rinse ?repeat.
Time to get (or build) an EPROM
emulator?
Build a FLASH-EPROM to EPROM adapter socket?
(As erasing a FLASH-EPROM is faster then erasing a EPROM and doesn't
need a UV lamp.)
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
9:08 a.m.
Hi
Even faster would be to use a CMOS RAM and
a battery. No special voltages or special
write sequences.
Dwight
Date: Sun, 27 Dec 2009 16:03:11 +0100
From: jkunz at unixag-kl.fh-kl.de
To: cctalk at classiccmp.org
Subject: Re: 2732 eproms.
On Fri, 25 Dec 2009 02:34:59 -0800
Geoffrey Reed <geoffr at zipcon.net> wrote:
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
http://clk.atdmt.com/GBL/go/171222986/direct/01/
I have one fo them and it is getting old
burning it, testing the device, erasing it, and burning
different code into it, lather ?rinse ?repeat.
Time to get (or build) an EPROM
emulator?
Build a FLASH-EPROM to EPROM adapter socket?
(As erasing a FLASH-EPROM is faster then erasing a EPROM and doesn't
need a UV lamp.)
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
9:41 a.m.
On Dec 27, 2009, at 9:08 AM, dwight elvey wrote:
Hi
Even faster would be to use a CMOS RAM and
a battery. No special voltages or special
write sequences.
Battery == bad. Use FRAM. It's just like RAM except it retains it's
contents when power's off. Comes in x8 and x16 varieties.
TTFN - Guy
Date: Sun, 27 Dec 2009 16:03:11 +0100
From: jkunz at unixag-kl.fh-kl.de
To: cctalk at classiccmp.org
Subject: Re: 2732 eproms.
On Fri, 25 Dec 2009 02:34:59 -0800
Geoffrey Reed <geoffr at zipcon.net> wrote:
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
http://clk.atdmt.com/GBL/go/171222986/direct/01/ I have one fo them and it is getting old
burning it, testing the device, erasing it, and burning
different code into it, lather rinse repeat.
Time to get (or build) an EPROM
emulator?
Build a FLASH-EPROM to EPROM adapter socket?
(As erasing a FLASH-EPROM is faster then erasing a EPROM and doesn't
need a UV lamp.)
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
10:42 a.m.
On Dec 27, 2009, at 9:48 AM, Chuck Guzis wrote:
On 27 Dec 2009 at 9:41, Guy Sotomayor wrote:
Unless you're really cramped for space, why not create a "custom" chip
carrier? Use one of the SMT packages (vs DIP). Many of the Ramtron
parts are marketed as replacements for RAM+battery so I suspect that
you'd run the same problem with that solution too.
TTFN - Guy
Battery == bad. Use FRAM. It's just like
RAM except it retains it's
contents when power's off. Comes in x8 and x16 varieties.
Doesn't help--the Ramtron 8Kx8 (smallest available) is still a 28-pin
package.
11:08 a.m.
On 27 Dec 2009 at 10:42, Guy Sotomayor wrote:
Unless you're really cramped for space, why not
create a "custom" chip
carrier? Use one of the SMT packages (vs DIP). Many of the Ramtron
parts are marketed as replacements for RAM+battery so I suspect that
you'd run the same problem with that solution too.
Given that this involves EPROMs, why not spend the $5 or so for a new
one, program it and forget about it? I don't understand that there
would be any sort of positive ROI in this particular application. I
can see the benefit of MRAM or FRAM where the data changes often, but
this doesn't appear to be such an application.
--Chuck
11:40 a.m.
--- On Sun, 12/27/09, Guy Sotomayor <ggs at shiresoft.com> wrote:
Unless you're really cramped for space, why not
create a
"custom" chip carrier?? Use one of the SMT packages (vs
DIP).? Many of the Ramtron parts are marketed as
replacements for RAM+battery so I suspect that you'd run the
same problem with that solution too.
All these "solutions" seem like a heck of a lot more work than the EPROMs
they're meant to replace. I mean, used EPROM chips are fifty cents each or less, and
they are quite easy to get. Even if you're doing code development, changing the code
in the chip many times a day, having a dozen chips on hand would be the simple, cheap way
to go. Erasing them isn't that big a deal.
I've done development on homemade stuff requiring the constant reburning of EPROMs to
test code, and it's really not any sort of problem - just have a handful of chips, and
when you start running low, throw some into the eraser and they'll be ready when you
need them next.
If everyone else is this opposed to the simple, reliable, inexpensive EPROM - then
I'll happily take any unwanted chips :)
-Ian
4:07 p.m.
On Dec 27, 2009, at 2:40 PM, Mr Ian Primus wrote:
Absolutely. It has been done this way for decades; parts and
equipment are cheap and readily available.
Unless
you're really cramped for space, why not create a
"custom" chip carrier? Use one of the SMT packages (vs
DIP). Many of the Ramtron parts are marketed as
replacements for RAM+battery so I suspect that you'd run the
same problem with that solution too.
All these "solutions" seem like a heck of a lot more work than the
EPROMs they're meant to replace. I mean, used EPROM chips are fifty
cents each or less, and they are quite easy to get. Even if you're
doing code development, changing the code in the chip many times a
day, having a dozen chips on hand would be the simple, cheap way to
go. Erasing them isn't that big a deal. I've done development on homemade stuff requiring
the constant
reburning of EPROMs to test code, and it's really not any sort of
problem - just have a handful of chips, and when you start running
low, throw some into the eraser and they'll be ready when you need
them next.
Yup, if you rotate through them, there's no waiting. I've done
tons of development this way, as I suspect many here have.
Sure, flash or FRAM chips do have a convenience advantage, but IMO
it is very slight. The fact that something is newer doesn't
automatically make it better, and because something is better doesn't
automatically make it "better enough" to ignore everything that came
before it.
-Dave
--
Dave McGuire
Port Charlotte, FL
6:18 p.m.
On Sun, Dec 27, 2009 at 2:40 PM, Mr Ian Primus <ian_primus at yahoo.com> wrote:
I've done development on homemade stuff requiring
the constant reburning of EPROMs to test code, and it's really not any sort of problem
- just have a handful of chips, and when you start running low, throw some into the eraser
and they'll be ready when you need them next.
I've done that lots, but there was one case where I was very, very
happy to have an EPROM emulator... it was embedded firmware for a
VAXBI peripheral card we were making (COMBOARD-BI). By being able to
update the firmware over a serial port and not have to shut down the
machine to swap out the chips, I was able to test a new version of
code in under two minutes vs a 20-minute shutdown, power-off,
power-on, boot cycle.
For normal, table-top sorts of projects, though, real EPROMs aren't so
bad if you have 4-5 sets.
-ethan
6:42 p.m.
All these "solutions" seem like a heck of a
lot more work than the EPROMs they're meant to replace. I mean, used EPROM chips are
fifty cents each or less, and they are quite easy to get. Even if you're doing code
development, changing the code in the chip many times a day, having a dozen chips on hand
would be the simple, cheap way to go. Erasing them isn't that big a deal.
Yes, 2732s (and below) are still easy to get - even for free. I may
still have a bunch, unless Ian has culled them out of my EPROM box.
Now 2704s are a different story. I found a board with a few of them
digging thru all this CDC stuff. Of course I had to rescue them...
--
Will
6:47 p.m.
Someone mentioned epromman.com, it seems that there was a fire at their
storage? Or warehouse?
In reply to a query I sent them...
-
Sorry again....since the fire, there have been some problems with our
insurance and they have forced us to stop our move in midstream.? It seems
that they want to salvage the entire eprom section as part of our claim.?
Not the worst thing for us but I honestly don't think I'll be able to
restock until late January.
-
7:40 p.m.
--- On Sun, 12/27/09, William Donzelli <wdonzelli at gmail.com> wrote:
Yes, 2732s (and below) are still easy to get - even
for
free. I may
still have a bunch, unless Ian has culled them out of my
EPROM box.
Hehe. Nah, you still have quite a few in there. Which reminds me, you really should take
this box of EPROMs back, lest they all find their way into my projects. Some of them are
looking nervous.
Now 2704s are a different story. I found a board with
a few
of them
digging thru all this CDC stuff. Of course I had to rescue
them...
Good point. *Those* are very rare. I really should try to talk you out of one of those,
just so I can say I have one. If I was ever working on any hardware that used those,
I'd simply build an adapter and use part of a 2732 or something. That's the nice
thing about EPROM chips - even if you don't have the right one, it's usually not
that big a deal to use a more common chip and tie the unused address lines to ground.
The only annoying thing is on the other side of the spectrum - needing a bigger chip.
Lately I've been working with hardware that requires much larger chips, and 16 bit
wide ones at that. 16 and 32 megabit EPROMs are out there, but aren't nearly as easily
scavenged as, say, 27512's are.
-Ian
10:01 a.m.
Guy Sotomayor wrote:
On Dec 27, 2009, at 9:08 AM, dwight elvey wrote:
I use FRAM in my drive controller. Not that I needed the non-volatile
properties. It's serial(great for small number of pins, opcodes very
easy to use), 8 pins, no wait write/reads, fast (up to 20mhz),
reprogrammable virtually unlimited number of writes.
I got samples from local Ramtron distributor.
(I haven't followed the thread, so no idea if this is applicable to task
at hand, but I still think these are neat chips. :)
Keith
Hi
Even faster would be to use a CMOS RAM and
a battery. No special voltages or special
write sequences.
Battery == bad. Use FRAM. It's just like RAM except it retains it's
contents when power's off. Comes in x8 and x16 varieties.
5254
days inactive
5257
days old
21 comments
13 participants
participants (13)
-
cclist＠sydex.com -
dkelvey＠hotmail.com -
ethan.dicks＠gmail.com -
geoffr＠zipcon.net -
ggs＠shiresoft.com -
ian_primus＠yahoo.com -
jkunz＠unixag-kl.fh-kl.de -
keithvz＠verizon.net -
mcguire＠neurotica.com -
pinball＠telus.net -
snhirsch＠gmail.com -
thrashbarg＠kaput.homeunix.org -
wdonzelli＠gmail.com