From PICLIST@MITVMA.MIT.EDU Fri Nov 15 00:40:11 2002 Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-7.13) id A2EB14AE00EA; Fri, 15 Nov 2002 00:40:11 -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.007DB37E@cherry.ease.lsoft.com>; Fri, 15 Nov 2002 3:26:09 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 0042 for PICLIST@MITVMA.MIT.EDU; Fri, 15 Nov 2002 03:25:54 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 5022; Fri, 15 Nov 2002 03:25:45 -0500 Received: from *unknown [47.211.129.137] by mitvma.mit.edu (IBM VM SMTP Level 320) via TCP with ESMTP ; Fri, 15 Nov 2002 03:25:43 EST X-Warning: mitvma.mit.edu: Host *unknown claimed to be znsgs01r.nortelnetworks.com Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.160.46.124]) by znsgs01r.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id gAF8PfV14700 for ; Fri, 15 Nov 2002 08:25:41 GMT Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Nov 2002 08:25:41 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Message-ID: Date: Fri, 15 Nov 2002 08:25:40 -0000 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Michael Rigby-Jones Subject: Re: [PIC]:failed data location? To: PICLIST@MITVMA.MIT.EDU X-RCPT-TO: Status: R X-UIDL: 277600605 X-Evolution-Source: pop://mailinglist%40farcite.net@mail.farcite.net/ X-Evolution: 00000735-0000 > -----Original Message----- > From: Dale Botkin [SMTP:dale@BOTKIN.ORG] > Sent: Friday, November 15, 2002 1:43 AM > To: PICLIST@mitvma.mit.edu > Subject: Re: [PIC]:failed data location? > > On Thu, 14 Nov 2002, Dennis J. Murray wrote: > > > I've got 6 of these units in the field, and this is the most recent - > > installed in May (the oldest was put in the field in Dec 01). They're > ALL > > running the same code and only this one failed. It failed hard - even > after > > numerous hard resets. It's replacement chip has been working perfectly > for > > 2 weeks. > > OK, so it's a hardware failure. It happens, so you toss the chip and move > on with your life. So why are we now turning this into a pissing match in > front of 1800 people on the PICList?? Both of you need to take it off > list or just drop it. > While I agree about slagging matches on the list, "toss the chip and move on with your life" isn't what any responsible engineer would do. If this happened to me I'd want to know exactly what went wrong, and what the chances are of this happening to other products I have in the field and what MChip are going to do about improved testing. Software bugs are one thing, but if you can't rely on the hardware to work properly for the expected life of your product them you have a big problem. Mike -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.