---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id A8F44BA2009A; Wed, 28 Jan 2004 12:17:56 -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 <21.00CC1582@cherry.ease.lsoft.com>; Wed, 28 Jan 2004 15:17:44 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 6368 for PICLIST@MITVMA.MIT.EDU; Wed, 28 Jan 2004 15:17:36 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 2873; Wed, 28 Jan 2004 15:17:11 -0500 Received: from rwcrmhc13.comcast.net [204.127.198.39] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Wed, 28 Jan 2004 15:17:10 EST X-Comment: mitvma.mit.edu: Mail was sent by rwcrmhc13.comcast.net Received: from dragon (pcp04856710pcs.olathe01.ks.comcast.net[68.86.129.42]) by comcast.net (rwcrmhc13) with SMTP id <2004012820171201500kensoe>; Wed, 28 Jan 2004 20:17:12 +0000 X-Mailer: PocoMail 2.64 (1120) - Licensed Version Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: <2004128141712.628136@dragon> Date: Wed, 28 Jan 2004 14:17:12 -0600 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Matt Pobursky Subject: Re: [PIC]: 18FXX2 data sheet inconsistent To: PICLIST@MITVMA.MIT.EDU In-Reply-To: Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856158 On Wed, 28 Jan 2004 13:23:51 -0000, Brian Clewer wrote: > Olin Lathrop wrote: > > > I've never had a need to rely on the power up state of an FSR > > register. In fact, I think it's a bad idea. That's probably why > > nobody had noticed this discrepancy in the manual before. > > > > Why do you care about the power up state of FSR0? > > > > Well I wouldn't, but as I mentioned in another post, I think it is > the cause of a problem seen in the CCS compiler. I find this kind of doubtful. Have you looked at the startup code that CCS generates to see what's going on? i.e. see if the startup code relies on a particular setting of FSR or whether they explicitly initialize it -- I'm betting they do. Failing that, have you sent a sample of your code to CCS tech support to look at? They can probably tell you whether it's a compiler bug (appears to be) and exactly what's causing it... Matt Pobursky Maximum Performance Systems -- 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 .