At work we have purchased a PM3 programmer along with the required socket=
=20
modules in this case the AC164302 Universal SOIC module.

I am having no success in trying to program an SST25VF032B eeprom (SPI), I=
=20
am aware that Microchip recommend using the SST26 series.

We have the 'gold' copies of EEPROMS and I have no difficulty in reading=20
the contents and exporting the hex file to a folder on the PC. When I try=20
to program a new out of tube SST25, th eimage is downloaded to the PM3 and=
=20
it programs and then fails on verification with the error

Address 00000  Good 0009F Bad 0000FF.

When I read back the contents of the failed  chip it bore no relation to=20
the original contents.

Original             programmed
Address 000000 CF		9F
							BB			3D
							A3			F8

from address 000000 07 onwards all remaining addresses are filled with=20
alternating 9A 69.

I've tried storing the hex file on SDCard and reading as a standalone with=
=20
the same result, I've tried even reprogramming with the data in the=20
incorrect result, which actually results in all memory containing 00.

As we need this to repair bespoke obsolete main processor boards,I'd be=20
grateful for any thoughts. There is no problem programming the 24 series of=
=20
eeprom.

Details of setup:

PM3 version 10-00398-R8 ROHS compliant version - so I assume this means it=
=20
will program the SST range which earlier version that were not ROHS=20
compliant wouldn't - source Microchip PM3 docs.

The hex file is 11.522kB in size and co-incidentally so is the faulty file=
=20
when read.

Now we have had to 'bodge' the SOIC module as the SST chips are 200 mil=20
SOIC and the module takes the 150 mil size, Therefore I have run a short=20
ribbon cable about 40 -50 mm long to a spring loaded Microchip socket meant=
=20
for their other programmers, Unlike the PM3 module(with passives installed)=
=20
these are just spring sockets on a dip board.

I wonder if this cable could be causing a program problem even though it=20
seems to read an EEPROM without any hastles.

I have fiddled with the 'hold in reset' option on the PM3 and tried=20
disabling chip ID etc, with no difference in outcome.

The PC is an ancient Apex running XP 32 bit with 490MB RAM (we are only=20
allowed to use obsolete PCs for this kind of thing).

Many thanks

Colin




--
cdb,  on 14/05/2015






--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.