---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id AC8789EE009A; Sat, 31 Jan 2004 08:49: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 <16.00CC686C@cherry.ease.lsoft.com>; Sat, 31 Jan 2004 11:49:00 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 9088 for PICLIST@MITVMA.MIT.EDU; Sat, 31 Jan 2004 11:48:55 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 1467; Sat, 31 Jan 2004 11:47:01 -0500 Received: from ww7.msen.com [148.59.19.30] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Sat, 31 Jan 2004 11:47:00 EST X-Comment: mitvma.mit.edu: Mail was sent by ww7.msen.com X-Popauth-Info: 1075569282 X-Sent-To: Received: from ww7.msen.com (adsl-67-36-70-238.dsl.sfldmi.ameritech.net [67.36.70.238]) by ww7.msen.com (8.12.9/8.12.9) with ESMTP id i0VGl33Y048037 for ; Sat, 31 Jan 2004 11:47:03 -0500 (EST) (envelope-from ic@ww7.msen.com) X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <401BDC0B.278A82B@ww7.msen.com> Date: Sat, 31 Jan 2004 11:47:07 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Chris Oesterling Subject: [PIC]: Incoming serial data at power-up chokes PIC To: PICLIST@MITVMA.MIT.EDU Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856684 I hope someone has seen this before! I'm using the CCS PCW compiler 3.116 with a PIC16F877A. Using an interrupt or pulling the incoming serial data via getc() I get the same result. If there is a continuous stream of incoming serial data at power-up (or start of the code via my ICE) I will get a character (maybe) then no additional data will ever appear. If I powerup my circuit (or restart my code on the ICE) and then start the stream of incoming serial data everything works fine. I'm using a MAX232, I've used this circuit in production for years, and even the simplest version of the code still demonstrates this anomaly. Using my ICE or burning a chip produces the same results. Any idea??? Thank you! - Chris -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu .