From PICLIST@MITVMA.MIT.EDU Fri Nov 15 04:42:35 2002 Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-7.13) id ABBB1BC60096; Fri, 15 Nov 2002 04:42:35 -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 <8.007DB63C@cherry.ease.lsoft.com>; Fri, 15 Nov 2002 7:28:32 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 1633 for PICLIST@MITVMA.MIT.EDU; Fri, 15 Nov 2002 07:28:22 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 8063; Fri, 15 Nov 2002 07:28:06 -0500 Received: from smtp.comcast.net [24.153.64.2] by mitvma.mit.edu (IBM VM SMTP Level 320) via TCP with ESMTP ; Fri, 15 Nov 2002 07:28:05 EST X-Comment: mitvma.mit.edu: Mail was sent by smtp.comcast.net Received: from ScottTouchton (pcp02285524pcs.potshe01.pa.comcast.net [68.83.254.213]) by mtaout01.icomcast.net (iPlanet Messaging Server 5.1 HotFix 1.5 (built Sep 23 2002)) with SMTP id <0H5M00IXVAL80L@mtaout01.icomcast.net> for PICLIST@MITVMA.MIT.EDU; Fri, 15 Nov 2002 07:27:14 -0500 (EST) MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <00e001c28bfc$d5792120$0a01a8c0@djm> <000501c28c18$83fc02b0$0300a8c0@main> <000e01c28c37$65405500$0a01a8c0@djm> <000801c28c46$063aa060$6501a8c0@potshe01.pa.comcast.net> <011401c28c8f$4d1c7dc0$e7bdf682@sstdwkiwi> Message-ID: <002501c28ca1$33f961c0$6501a8c0@potshe01.pa.comcast.net> Date: Fri, 15 Nov 2002 07:19:10 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Scott Touchton Subject: Re: [PIC]:failed data location? To: PICLIST@MITVMA.MIT.EDU X-RCPT-TO: Status: R X-UIDL: 277600637 X-Evolution-Source: pop://mailinglist%40farcite.net@mail.farcite.net/ X-Evolution: 00000753-0000 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.