R
[email protected]
- Jan 1, 1970
- 0
hello, I was wondering if anyone had ever encountered something like
my latest joy.
summary:
unit stops working, yet when you read in the program and e2prom space,
the data looks fine and when reprogrammed, the chips (and circuit)
work fine
details:
we have a circuit using a PIC12F629 with softwareA. been using it for
years. no problem
now, same circuit, new softwareB.
does the same basic thing as A. we developed it, tested it debugged
it. sent it out.
now (after about 80 of the units were assembled and 40 shipped out).
we start seeing these failures.
example:
a unit assembled and burned in here at the plant for less than 1.5
hours.. found dead
2 units, sent in the field, worked.. a day, a week.. then died
so we recalled everything and set 10 units, non-encapsulated, to run
in the lab
after about 2.5 days, one died. being unencapsulated, we were able to
take the chip and read it using our programmer (Promate II).
my original suspicion had been that the E2prom was getting scrambled.
something I had encountered in another project and which could have
resulted in a situation where the program functions, the chip pins are
fine.. but the orders which were in E2prom are now gibberish and so
the unit appears to be dead.
but, when I read this chip. everything was perfect. software
identical to what was programmed in. OSCAL look healthy. E2prom as
was programmed in
tried a different in the circuit.. circuit worked fine. tried the
'bad' chip in the circuit again.. dead. reprogrammed the 'bad' chip
(to see if maybe pins were missbehaving)... works fine; still working
fine after.. roughly 2 days.
no others of my labrats have died (so they have been on for ~~4.5
days)
anyone with ideas... pretty please!
my latest joy.
summary:
unit stops working, yet when you read in the program and e2prom space,
the data looks fine and when reprogrammed, the chips (and circuit)
work fine
details:
we have a circuit using a PIC12F629 with softwareA. been using it for
years. no problem
now, same circuit, new softwareB.
does the same basic thing as A. we developed it, tested it debugged
it. sent it out.
now (after about 80 of the units were assembled and 40 shipped out).
we start seeing these failures.
example:
a unit assembled and burned in here at the plant for less than 1.5
hours.. found dead
2 units, sent in the field, worked.. a day, a week.. then died
so we recalled everything and set 10 units, non-encapsulated, to run
in the lab
after about 2.5 days, one died. being unencapsulated, we were able to
take the chip and read it using our programmer (Promate II).
my original suspicion had been that the E2prom was getting scrambled.
something I had encountered in another project and which could have
resulted in a situation where the program functions, the chip pins are
fine.. but the orders which were in E2prom are now gibberish and so
the unit appears to be dead.
but, when I read this chip. everything was perfect. software
identical to what was programmed in. OSCAL look healthy. E2prom as
was programmed in
tried a different in the circuit.. circuit worked fine. tried the
'bad' chip in the circuit again.. dead. reprogrammed the 'bad' chip
(to see if maybe pins were missbehaving)... works fine; still working
fine after.. roughly 2 days.
no others of my labrats have died (so they have been on for ~~4.5
days)
anyone with ideas... pretty please!