Hello !
you need the exact type (= storage capacity and pinout) ∗and∗ the access
time of the EEPROM, assuming that fast devices can perform slowly, not
the opposite. It is often a suffix after the chip "name", either a
letter or a number.
Some EEPROM share the same pinout with different storage capacities :
the larger can be sometimes a good alternative, more easily available
than the smaller, often early issues in the same package. In this case
you often find a "NC" pin on the small changed into an address pin on
its bigger sister. It is not a big problem but then you need to tie this
unused address pin to 0V (or + Vcc depending on the chip type) to
disable it. It means : take your soldering iron and put a little bit of
wire between 2 pins of the chip on the AN1x PCB.... ∗If you're not
familiar with the job∗, ∗don't do it∗, or ask an electronics hobbyist
friend.
To everyone on the forum : ∗if your AN1x performs normally∗ the software
upgrade is unnecessary , ∗leave it as it is∗.
The soft mods on this type of instrument are mostly completely invisible
for the user, unless he unfortunately uses his synth in an environment
(other instruments, computer, musical software...) that provokes the
corrected bug(s). Never expect something as radical as changing the OS
on your computer !! No extra sounds, no new functions, nothing like that
: a musical instrument like the AN1x is not a computer, it is mostly
hardware, with a bit of software, not the opposite. If you want a
computer analogy, it could be in a sense like the BIOS on your
motherboard, nothing more.
To Jon : i never wanted to launch an EEPROM cottage industry! ;-) I
don't have time, the programmer is not mine and i don't want to get a
full mailbox of messages from disappointed customers... ∗
But, ∗as∗ ∗Ed says, when the manufacturer no longer supports an
"obsolete" product you have to help yourself. And with "modern"
electronics one major problem are the programmable devices : you can
find the replacement part, but empty. If you don't have the soft inside,
you cannot do anything. So a reliable acces to a reliable "bin" file is
useful and worth trying.
Cheers, and enjoy your week end !
J.F.
P.S. I was thinking this forum was sleeping slowly to death, in fact it
is not, fine !
Ed Edwards a écrit :
>
>
> I have to ask someone in the biz for this info.
>
> They are Electronicly Eraseable and Programmable Read Only Memories. They
> vary in the amount of storage (64k was common back in the mid 80's). The
> chip WILL be stamped with a code that will reveal the amount of storage.
> But there are further subsets which include stuff like cyclic redundancy
> check or negative/positive or other stuff such as sub memory. The
> electronics person involved in this area will be very familiar with the
> parameters.
>
> _____
>
> From: AN1x-list@yahoogroups.com <mailto:AN1x-list%40yahoogroups.com>
> [mailto:AN1x-list@yahoogroups.com
> <mailto:AN1x-list%40yahoogroups.com>] On Behalf
> Of jondl_2000
> Sent: Saturday, October 31, 2009 12:55 AM
> To: AN1x-list@yahoogroups.com <mailto:AN1x-list%40yahoogroups.com>
> Subject: Re: [AN1x] In search of OS v1.04 bin file
>
> Many thanks Ed... I've got my v1.02 EEPROM in front of me right now,
> is has
> scarce markings - only a sticker that says copyright 1997 Yamaha XS467 D O
> How do you identify the appropriate blank device type?
>
> Jon
>
> --- In AN1x-list@yahoogrou <mailto:AN1x-list%40yahoogroups.com>
> ps.com, "Ed
> Edwards" <gleobeam@...> wrote:
> >
> > You need to be (or have a friend who is) a nerd that has access to an
> eeprom
> > reader/programmer. As a reader, it will dump the internal bin(ary)
> program
> > to some software storage device. So to obtain the bin file, the actual
> > eeprom needs to be plugged into the unit. To program a chip
> obviously one
> > needs a blank eeprom chip and this can be tough because it has to be the
> > exact match for what it replaces. Some of these have passed into
> > obsolescence. I don't think the blank for the AN1x is obsolete.
> > Unfortunately I no longer am employed in this end of electronics.
> What we
> > need is a volunteer on the list to step up and go with the project. It
> > can't be a "for profit" venture because never have I ever seen more
> than a
> > few dozen (at the most) folks who needed the upgrade. This isn't to say
> > that only a few dozen synths are not fully upgraded. the fact is that
> > hundreds or thousands are behind, but what the results become are
> the few
> > who subscribe to a list and are "brave" enough to attempt this. Only one
> > guy needs to give up his eeprom for reading the bin out of. Then as many
> > duplicates can be made as requested. Once the user receives the
> duplicate
> > it is up to them to unplug the old chip and replace it (really not a big
> > deal for almost anyone coordinated enough to play a keyboard).
> >
> >
> >
> > So I hope this helps.
> >
> >
> >
> > _____
> >
> > From: AN1x-list@yahoogrou <mailto:AN1x-list%40yahoogroups.com> ps.com
> [mailto:AN1x-list@yahoogrou <mailto:AN1x-list%40yahoogroups.com>
> ps.com] On
> Behalf
> > Of jondl_2000
> > Sent: Saturday, October 31, 2009 12:02 AM
> > To: AN1x-list@yahoogrou <mailto:AN1x-list%40yahoogroups.com> ps.com
> > Subject: Re: [AN1x] In search of OS v1.04 bin file
> >
> >
> >
> >
> >
> >
> >
> > --- In AN1x-list@yahoogrou <mailto:AN1x-list%40yahoogroups.com> ps.com,
> "Ed
> > Edwards" <gleobeam@> wrote:
> > >
> > > Pha and phoo I say to my good friend, Jon.
> > >
> >
> > Ha haha :-)
> >
> > > It won't degrade this list in any way by helping abandoned synthisists
> > bring
> > > their machines up to "final upgrade from factory" level.
> > >
> >
> > That's all well and good...
> >
> > >
> > > I have participated on many synth lists that exchanged eprom bin files
> and
> > > eeproms for the purpose of helping out a fellow user whom the
> manufacturer
> > > has abandoned to "go buy our new one, your old junk isn't worth
> > supporting".
> >
> > ...so how do you create a bin from an EEPROM?
> >
> > Jon
> >
> >
> >
> > No virus found in this incoming message.
> > Checked by AVG - www.avg.com
> > Version: 8.5.423 / Virus Database: 270.14.39/2469 - Release Date:
> 10/30/09
> > 07:52:00
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.423 / Virus Database: 270.14.39/2469 - Release Date: 10/30/09
> 07:52:00
>
> [Non-text portions of this message have been removed]
>
>