---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id A1EE78CA008E; Fri, 30 Jan 2004 14:59:58 -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.00CC58E7@cherry.ease.lsoft.com>; Fri, 30 Jan 2004 17:59:47 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 7808 for PICLIST@MITVMA.MIT.EDU; Fri, 30 Jan 2004 17:59:41 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 3586; Fri, 30 Jan 2004 17:58:53 -0500 Received: from bay8-dav7.bay8.hotmail.com [64.4.26.111] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Fri, 30 Jan 2004 17:58:52 EST X-Warning: mitvma.mit.edu: Host bay8-dav7.bay8.hotmail.com claimed to be hotmail.com Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 30 Jan 2004 14:58:54 -0800 Received: from 67.65.155.200 by bay8-dav7.bay8.hotmail.com with DAV; Fri, 30 Jan 2004 22:58:54 +0000 X-Originating-IP: [67.65.155.200] X-Originating-Email: [jsears2027@hotmail.com] X-Sender: jsears2027@hotmail.com References: <27F5AF5F2C1BD2119F860008C7F4730A0853C52B@co-srv06.ridgid.com> 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.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-OriginalArrivalTime: 30 Jan 2004 22:58:54.0757 (UTC) FILETIME=[A2AECD50:01C3E784] Message-ID: Date: Fri, 30 Jan 2004 16:58:51 -0600 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: James Nick Sears Subject: Re: [PIC:] 16LF877A A/D To: PICLIST@MITVMA.MIT.EDU Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856597 Thanks. I found it in the 877A datasheet and while that is good news, there is another spec for VREF = (Vref+ - Vref-) that has a minimum of 2V. Looks like I need a different reference. I reprogrammed the working board so I know all the firmware is the same and it still works so it has to be a hardware issue and I guess that's probably it. I'm getting ready to reprogram one of the faulty boards to use Vdd as the reference and see what results I get. BRB. Nick ----- Original Message ----- From: "Eisermann, Phil [Ridg/CO]" To: Sent: Friday, January 30, 2004 4:22 PM Subject: Re: [PICLIST] [PIC:] 16LF877A A/D > pic microcontroller discussion list wrote: > >> Are you sure about that? The data sheet says MIN (Vdd-2.5V), and > >> MAX (Vdd+0.3V). > > > I couldn't find that in the datasheet. What page is it on? > > In my version of the datasheet (DS30292A), it is Table 15-13 on > page 175 and labeled parameter A21 > > > What exactly does the label of that graph on p.210 mean though > > ("Differential or Integral Nonlinearity (LSB)")? > > see microchip's app note AN546 for a description. Based on a different > chip but does explain the terms. I suspect a google would turn up > a lot more information. > > Phil Eisermann > > -- > http://www.piclist.com#nomail Going offline? Don't AutoReply us! > email listserv@mitvma.mit.edu with SET PICList DIGEST in the body > -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body . Return-Path: <> Received: from mitvma.mit.edu ([18.92.0.3]) by tomts39-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040128150707.KFOX26980.tomts39-srv.bellnexxia.net@mitvma.mit.edu> for ; Wed, 28 Jan 2004 10:07:07 -0500 Received: by mitvma.mit.edu (IBM VM SMTP Level 430) via spool with SMTP id 6731 ; Wed, 28 Jan 2004 10:07:03 EST Received: from MITVMA.MIT.EDU (NJE origin LISTSERV@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 4210; Wed, 28 Jan 2004 10:07:04 -0500 Date: Wed, 28 Jan 2004 10:07:04 -0500 From: "L-Soft list server at MITVMA.MIT.EDU (1.8e)" Subject: PICLIST: error report from NT.MASSMIND.ORG To: listsjosh@3MTMP.COM, "For Blackholeeclipse@Earthlink.Net" 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 4208; Wed, 28 Jan 2004 10:07:04 -0500 Received: from nt.massmind.org [66.13.172.18] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with SMTP ; Wed, 28 Jan 2004 10:07:03 EST X-Comment: mitvma.mit.edu: Mail was sent by nt.massmind.org To: owner-piclist@MITVMA.MIT.EDU From: Mail Administrator Reply-To: Mail Administrator Subject: Mail System Error - Returned Mail Date: Wed, 28 Jan 2004 06:54:55 -0800 Message-ID: <20040128145455738.AAF388@nt.massmind.org> MIME-Version: 1.0 Content-Type: multipart/mixed; Boundary="===========================_ _= 2670898(388)" Content-Transfer-Encoding: 7BIT --===========================_ _= 2670898(388) Content-Type: text/plain This Message was undeliverable due to the following reason: This message passed through a number of mail servers greater than the maximum number specified in the Maximum MTA Hops field. This probably indicates that there are accounts on separate machines that forward mail to each other. There may also be a problem with the host address or Domain Name System records. Maximum Hops: 15 Please reply to Postmaster@nt.massmind.org if you feel this message to be in error. --===========================_ _= 2670898(388) Content-Type: message/rfc822 Received: from cherry.ease.lsoft.com ([209.119.0.109]) by nt.massmind.org (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with ESMTP id org for ; Fri, 23 Jan 2004 06:41:38 -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 <12.00CB2DFE@cherry.ease.lsoft.com>; Fri, 23 Jan 2004 9:43:51 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 6355 for PICLIST@MITVMA.MIT.EDU; Fri, 23 Jan 2004 09:43:44 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 7693; Fri, 23 Jan 2004 09:42:26 -0500 Received: from audiomind.dk [213.237.88.238] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Fri, 23 Jan 2004 09:42:25 EST Received: from winbox.Audiomind.local (192.168.2.3:8158) by audiomind.dk with [XMail 1.16 (Linux/Ix86) ESMTP Server] id for from ; Fri, 23 Jan 2004 15:26:41 +0100 Received: from mail pickup service by winbox.Audiomind.local with Microsoft SMTPSVC; Fri, 23 Jan 2004 15:25:28 +0100 Received: from audiomind.dk ([192.168.2.6]) by winbox.intra.audiomind.dk with Microsoft SMTPSVC(6.0.3790.0); Tue, 20 Jan 2004 13:33:16 +0100 Received: from cherry.ease.lsoft.com (209.119.0.109:1107) by audiomind.dk with [XMail 1.16 (Linux/Ix86) ESMTP Server] id for from ; Mon, 19 Jan 2004 05:20:22 +0100 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.00CAAB5A@cherry.ease.lsoft.com>; 18 Jan 2004 23:20:19 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 2396 for PICLIST@MITVMA.MIT.EDU; Sun, 18 Jan 2004 23:20:15 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 5278; Sun, 18 Jan 2004 23:19:52 -0500 Received: from extsmtp1.localnet.com [207.251.201.54] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with SMTP ; Sun, 18 Jan 2004 23:19:51 EST Received: (qmail 25205 invoked from network); 19 Jan 2004 03:48:20 -0000 Received: from thwerll.localnet.sys (HELO smtp1.localnet.com) (10.0.7.18) by extsmtp1.localnet.com with SMTP; 19 Jan 2004 03:48:20 -0000 Received: (qmail 15180 invoked from network); 19 Jan 2004 04:19:52 -0000 Received: from unknown (HELO kmp) (63.246.198.41) by smtp3.localnet.com with SMTP; 19 Jan 2004 04:19:52 -0000 X-Comment: mitvma.mit.edu: Mail was sent by audiomind.dk X-Comment: mitvma.mit.edu: Mail was sent by extsmtp1.localnet.com X-AV-Scanned: yes 5af8184c397f62e50389e2077c14465c X-AV-Scanned: yes 20d1b1a721c825c984df4fd5b1f5cb6c X-Deliver-To: soren@audiomind.dk 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 IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Precedence: list X-OriginalArrivalTime: 20 Jan 2004 12:33:16.0984 (UTC) FILETIME=[944BB380:01C3DF51] Message-ID: Date: Sun, 18 Jan 2004 23:20:02 -0500 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Ken Pergola Subject: [EE]: NEC's version of the Intel 8255 Programmable Peripheral Interface To: PICLIST@MITVMA.MIT.EDU In-Reply-To: Hi, I was hoping someone might have *NEC's data sheet* (paper or PDF) for NEC's version of the Intel 8255 chip. Or, does anyone have a NEC data book from the 1992 era that has this chip in it? NEC's part # is: D71055C-10 Once again, I'm not looking for Intel's, Intersil's, Harris, AMD's, or Oki's data sheet -- I'm specifically looking for the NEC D71055C data sheet that NEC produced. I'm all googled out right now. I'm having a hard time locating this data sheet -- I'm pretty sure the chip's been discontinued by NEC a long time ago. No trace of it on NEC's web site. Full text on 40-pin DIP: NEC JAPAN D71055C-10 9250L5003 Thanks very much if someone can help me. I'm not asking anyone to search the web for me, but if anyone thinks they may have a NEC data book in your technical library, would you mind helping me out? I'd really appreciate it. I was just hoping that this would ring a bell in someone's head. Thanks very much for your help. Best regards, Ken Pergola -- 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 -- 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 --===========================_ _= 2670898(388)-- . Return-Path: <> Received: from mitvma.mit.edu ([18.92.0.3]) by tomts33-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040127234751.GSKI10753.tomts33-srv.bellnexxia.net@mitvma.mit.edu> for ; Tue, 27 Jan 2004 18:47:51 -0500 Received: by mitvma.mit.edu (IBM VM SMTP Level 430) via spool with SMTP id 6059 ; Tue, 27 Jan 2004 18:47:47 EST Received: from MITVMA.MIT.EDU (NJE origin LISTSERV@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 0489; Tue, 27 Jan 2004 18:47:48 -0500 Date: Tue, 27 Jan 2004 18:47:48 -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 0487; Tue, 27 Jan 2004 18:47:48 -0500 Received: from mta113.mail.sc5.yahoo.com [66.163.174.141] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with SMTP ; Tue, 27 Jan 2004 18:47:47 EST X-Comment: mitvma.mit.edu: Mail was sent by mta113.mail.sc5.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 mta113.mail.sc5.yahoo.com with SMTP; Tue, 27 Jan 2004 14:54:19 -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 <19.00CBF923@cherry.ease.lsoft.com>; Tue, 27 Jan 2004 16:18:34 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 3491 for PICLIST@MITVMA.MIT.EDU; Tue, 27 Jan 2004 16:18:29 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 6271; Tue, 27 Jan 2004 16:18:10 -0500 Received: from sccrmhc12.comcast.net [204.127.202.56] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Tue, 27 Jan 2004 16:18:10 EST X-Comment: mitvma.mit.edu: Mail was sent by sccrmhc12.comcast.net Received: from dragon (pcp04856710pcs.olathe01.ks.comcast.net[68.86.129.42]) by comcast.net (sccrmhc12) with SMTP id <20040127211812012003ccmoe>; Tue, 27 Jan 2004 21:18: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: <2004127151812.207027@dragon> Date: Tue, 27 Jan 2004 15:18:12 -0600 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Matt Pobursky Subject: Re: [PIC:] duplicate device IDs in the 18F series To: PICLIST@MITVMA.MIT.EDU In-Reply-To: <000401c3e50f$ef211a20$0b00a8c0@PAARD> Precedence: list On Tue, 27 Jan 2004 20:58:28 +0100, Wouter van Ooijen wrote: > > 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. I was thinking that these chips just might be the *exact same die*, just a different number of the pins bonded out. It kind of makes sense and lots of other chip makers do this. They could actually be the exact same chip, just a different package and part number. Otherwise I agree with you Wouter -- they should have different device ID's if they truly are different chip types. Matt Pobursky Maximum Performance Systems -- 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 *** .. .