From PICLIST@MITVMA.MIT.EDU Thu Nov 14 17:50:28 2002 Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-7.13) id A2E416F700EC; Thu, 14 Nov 2002 17:50:28 -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 <1.007DA523@cherry.ease.lsoft.com>; Thu, 14 Nov 2002 20:36:15 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8d) with spool id 5912 for PICLIST@MITVMA.MIT.EDU; Thu, 14 Nov 2002 20:36:05 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 7789; Thu, 14 Nov 2002 20:35:52 -0500 Received: from smtp.comcast.net [24.153.64.2] by mitvma.mit.edu (IBM VM SMTP Level 320) via TCP with ESMTP ; Thu, 14 Nov 2002 20:35:51 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 mtaout03.icomcast.net (iPlanet Messaging Server 5.1 HotFix 1.5 (built Sep 23 2002)) with SMTP id <0H5L00BPBGFOIB@mtaout03.icomcast.net> for PICLIST@MITVMA.MIT.EDU; Thu, 14 Nov 2002 20:35:52 -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> Message-ID: <000801c28c46$063aa060$6501a8c0@potshe01.pa.comcast.net> Date: Thu, 14 Nov 2002 20:26:29 -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: 277600566 X-Evolution-Source: pop://mailinglist%40farcite.net@mail.farcite.net/ X-Evolution: 00000718-0000 I will throw my 2 cents into the ring on the issue: I have seen RAM in the 16C54 that toggles on its own accord. Even duplicated it with a combination of temp and supply voltage. The part was "in specified operating range" all the time. No code bugs, just good ol' marginal wafers. I was using in excess of 500K per year, and Microchip acknowledged the issue with sincere apologies, but no remedy. I find it highly likely this is what you are experiencing. Though human error is usually the main culprit. -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics