On 02/27/2012 12:44 PM, Tony Duell wrote:
They're
worried about the idiot that builds a one-off programmer for use
in production, and doesn't test it thoroughly, and then destroys
hundreds or thousands of chips.
How does this differ from the ifiot who designes a
PSU which puts a 25V
spike on the 5V rail at power up/power down (and yse I have seen a
regualtor circuit which does that -- in a commercial bench PSU!) and then
tries to cleim all your ICs were defective?
That differs in that usually it
doesn't result in thousands of the same
EPROM being damaged. The problem is usually discovered after only a few.
Or the idiot who takes zero
anti-static precautions and then claims yuor ICs are failing i nthe field
a couple of months later?
If there was some piece of information that the vendor could withhold
from the datasheet that would prevent this problem,
they would. There
obviously isn't.
I'm not saying that I think leaving out the programming specifications
is the best thing for the vendor to do, just that there *is* at least
one reason for it that isn't completely irrational.