From PICLIST@MITVMA.MIT.EDU Fri Nov 15 07:11:02 2002 Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-7.13) id AE8615DA0048; Fri, 15 Nov 2002 07:11:02 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <22.007DC48C@cherry.ease.lsoft.com>; Fri, 15 Nov 2002 9:56:55 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 3208 for PICLIST@MITVMA.MIT.EDU; Fri, 15 Nov 2002 09:36:06 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 0803; Fri, 15 Nov 2002 09:34:37 -0500 Received: from pop017.verizon.net [206.46.170.210] by mitvma.mit.edu (IBM VM SMTP Level 320) via TCP with SMTP ; Fri, 15 Nov 2002 09:34:36 EST X-Comment: mitvma.mit.edu: Mail was sent by pop017.verizon.net Received: from djm ([151.199.99.63]) by pop017.verizon.net (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP id <20021115143436.FJZG1423.pop017.verizon.net@djm> for ; Fri, 15 Nov 2002 08:34:36 -0600 References: <00e001c28bfc$d5792120$0a01a8c0@djm> <000501c28c18$83fc02b0$0300a8c0@main> <000e01c28c37$65405500$0a01a8c0@djm> <000801c28c46$063aa060$6501a8c0@potshe01.pa.comcast.net> <011401c28c8f$4d1c7dc0$e7bdf682@sstdwkiwi> <002501c28ca1$33f961c0$6501a8c0@potshe01.pa.comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Authentication-Info: Submitted using SMTP AUTH LOGIN at pop017.verizon.net from [151.199.99.63] at Fri, 15 Nov 2002 08:34:35 -0600 Message-ID: <007a01c28cb4$24a83300$0a01a8c0@djm> Date: Fri, 15 Nov 2002 09:34:43 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: "Dennis J. Murray" Subject: Re: [PIC]:failed data location? To: PICLIST@MITVMA.MIT.EDU X-RCPT-TO: Status: R X-UIDL: 277600673 X-Evolution-Source: pop://mailinglist%40farcite.net@mail.farcite.net/ X-Evolution: 00000774-0000 Thanks for your input, Scott. I only had one failure, but it was enough to get my attention. I don't LIKE failures I can't explain. I guess I'm too complacent about the inherent reliability of the PIC chips - I just never expected one to fail without help! ----- Original Message ----- From: "Scott Touchton" To: Sent: Friday, November 15, 2002 7:19 AM Subject: Re: [PIC]:failed data location? > Well aware of MTBF.... but not 15,000 parts in a row in a very well > controlled facility. Apparently something in the masking process yielded a > section of memory that got real flaky at 35F (as confirmed by Microchip). > Just sharing, not attacking or trying to bash Microchip. I love their > products. Life just sucks sometimes. > > And yes, there has been a lot of discussion on this simple issue. I find it > surprising that the "sounds like a bad chip to me" came out in the thread a > little late although it was the obvious answer (might have missed it in the > thread, computer is real flaky at the moment)!! > > > > >I have seen RAM in the 16C54 that toggles on its own accord. > > > > > > I am a little surprised at all the discussion this particular failure has > > produced. Chips do fail. They have an MTBF figure. It may have even got an > > ESD zap without anyone realising during assembly/programming handling, > which > > will often not produce a failure at the time, but some time (often months) > > later. > > > > It is just that chips these days are so reliable that we don't expect > > failures. > > > > -- > > http://www.piclist.com hint: The PICList is archived three different > > ways. See http://www.piclist.com/#archives for details. > > > > > > -- > http://www.piclist.com hint: The PICList is archived three different > ways. See http://www.piclist.com/#archives for details. > > > -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.