---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id A0F8437B007A; Thu, 29 Jan 2004 16:10:32 -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.00CC3A8C@cherry.ease.lsoft.com>; Thu, 29 Jan 2004 18:52:56 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 5335 for PICLIST@MITVMA.MIT.EDU; Thu, 29 Jan 2004 18:52:51 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 8641; Thu, 29 Jan 2004 18:52:07 -0500 Received: from relais.videotron.ca [24.201.245.36] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Thu, 29 Jan 2004 18:52:06 EST X-Comment: mitvma.mit.edu: Mail was sent by relais.videotron.ca Received: from HOME1 ([69.70.77.61]) by VL-MO-MR001.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0HS900IVQZL912@VL-MO-MR001.ip.videotron.ca> for PICLIST@MITVMA.MIT.EDU; Thu, 29 Jan 2004 18:51:10 -0500 (EST) MIME-version: 1.0 X-Mailer: Calypso Version 3.30.00.00 (4) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable References: <200401291650230512.001912CC@relais.videotron.ca> Message-ID: <200401291851100262.0087A66B@relais.videotron.ca> Date: Thu, 29 Jan 2004 18:51:10 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: "Michael J. Pawlowsky" Subject: [PIC:] Using GPIO.3 as input for PULSIN on 12F675 Comments: To: picbasic-l@qunos.net To: PICLIST@MITVMA.MIT.EDU Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856379 Hello, I'm trying to get a reading using PULSIN (PicBasic Pro) on a PIC12F675 on= port GPIO.3 The DataSheet Give the description of the pin as such. 3.3.4 GP3/MCLR/VPP Figure 3-3 shows the diagram for this pin. The GP3 pin is configurable to function as one of the following: =95 a general purpose input =95 as Master Clear Reset Other notes of interest: Each of the GPIO pins, except GP3, has an individually configurable weak internal pull-up. The datasheet can be found at: http://www.microchip.com/download/lit/pline/picmicro/families/12f6xx/41190c.= pdf I can get a decent reading on any other Pin, just not GPIO.3 I set MCLR off using. @ Device MCLR_OFF Do I need a pullup resistor on this pin for PULSIN? If so what value? And it would go like: VDD | | / \ / ?ohm resistor \ | | -----------------------PWPin | | -------- GPIO.3 I've tried with several resistors like that but no go. Thanks, MIke -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details. . Return-Path: <> Received: from mitvma.mit.edu ([18.92.0.3]) by tomts30-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040128012240.GLPL1796.tomts30-srv.bellnexxia.net@mitvma.mit.edu> for ; Tue, 27 Jan 2004 20:22:40 -0500 Received: by mitvma.mit.edu (IBM VM SMTP Level 430) via spool with SMTP id 6129 ; Tue, 27 Jan 2004 20:22:36 EST Received: from MITVMA.MIT.EDU (NJE origin LISTSERV@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 2722; Tue, 27 Jan 2004 20:22:37 -0500 Date: Tue, 27 Jan 2004 20:22:37 -0500 From: "L-Soft list server at MITVMA.MIT.EDU (1.8e)" Subject: PICLIST: error report from YAHOO.COM To: listsjosh@3MTMP.COM, piclist_errors@SYMPATICO.CA Message-ID: X-LSV-ListID: None The enclosed message has been identified as a delivery error for the PICLIST list because it was sent to 'owner-piclist@MITVMA.MIT.EDU'. ------------------------------ Message in error ------------------------------- Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 2720; Tue, 27 Jan 2004 20:22:37 -0500 Received: from mta130.mail.scd.yahoo.com [66.218.86.46] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with SMTP ; Tue, 27 Jan 2004 20:22:36 EST X-Comment: mitvma.mit.edu: Mail was sent by mta130.mail.scd.yahoo.com From: MAILER-DAEMON@yahoo.com To: owner-piclist@mitvma.mit.edu X-Loop: MAILER-DAEMON@yahoo.com Subject: Delivery failure Message from yahoo.com. Unable to deliver message to the following address(es). : Sorry, your message to hbarregrd@yahoo.com cannot be delivered. This account is over quota. --- Original message follows. Return-Path: Received: from 209.119.0.109 (EHLO cherry.ease.lsoft.com) (209.119.0.109) by mta130.mail.scd.yahoo.com with SMTP; Tue, 27 Jan 2004 14:17:54 -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 <8.00CBF7DF@cherry.ease.lsoft.com>; Tue, 27 Jan 2004 14:59:28 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 1576 for PICLIST@MITVMA.MIT.EDU; Tue, 27 Jan 2004 14:59:18 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 3062; Tue, 27 Jan 2004 14:58:27 -0500 Received: from smtp-out3.xs4all.nl [194.109.24.13] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Tue, 27 Jan 2004 14:58:26 EST X-Comment: mitvma.mit.edu: Mail was sent by smtp-out3.xs4all.nl Received: from PAARD (a213-84-20-53.adsl.xs4all.nl [213.84.20.53]) by smtp-out3.xs4all.nl (8.12.10/8.12.10) with ESMTP id i0RJwSq3063819 for ; Tue, 27 Jan 2004 20:58:28 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Message-ID: <000401c3e50f$ef211a20$0b00a8c0@PAARD> Date: Tue, 27 Jan 2004 20:58:28 +0100 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Wouter van Ooijen Organization: Van Ooijen Technische Informatica Subject: Re: [PIC:] duplicate device IDs in the 18F series To: PICLIST@MITVMA.MIT.EDU In-Reply-To: <37FB7AA6F5F9814FB634A7BF4C35A6F5640CD9@ESEALNT442.al.sw.ericsson.se> Precedence: list > What is the difference, from the programmers point of view, > between programming a 28pin device and a 40pin device ? > If everything else is the same. Did you also check the programming specifications and fuses bits? And besides that, I often use scripts that check which chip I am programming - this has occasionally saved me from blunders. > As far as I can see from the line card the 16F767 and 777 have > the same amount of flash, no eeprom and so on. Even if this were completely true it would still be a bad sign of screw-up (lack of quality control) from uChip. AFAIK there used to be no chip types were indistinguishable for a programmer. Wouter van Ooijen -- ------------------------------------------- Van Ooijen Technische Informatica: www.voti.nl consultancy, development, PICmicro products -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads *** MESSAGE TRUNCATED *** .. .