From PICLIST@MITVMA.MIT.EDU Fri Nov 15 06:35:59 2002 Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-7.13) id A64FF7B00A2; Fri, 15 Nov 2002 06:35:59 -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 <14.007DB86C@cherry.ease.lsoft.com>; Fri, 15 Nov 2002 9:21:55 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 2872 for PICLIST@MITVMA.MIT.EDU; Fri, 15 Nov 2002 09:21:45 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 0376; Fri, 15 Nov 2002 09:20:30 -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:20:30 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 <20021115142030.FHDY1423.pop017.verizon.net@djm> for ; Fri, 15 Nov 2002 08:20:30 -0600 References: 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:20:29 -0600 Message-ID: <001701c28cb2$2c5301e0$0a01a8c0@djm> Date: Fri, 15 Nov 2002 09:20:37 -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: 277600666 X-Evolution-Source: pop://mailinglist%40farcite.net@mail.farcite.net/ X-Evolution: 0000076e-0000 I agree with you, Mike. I'm sorry I lost it with Olin. Olin, if you're reading this, I apologize. We do need to keep this list impersonal and address the issues at hand and not degrade someone's programming ability (or lack of it). ----- Original Message ----- From: "Michael Rigby-Jones" To: Sent: Friday, November 15, 2002 3:25 AM Subject: Re: [PIC]:failed data location? > > -----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. > > -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.