---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id A237A710200; Tue, 27 Jan 2004 16:28:39 -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.00CBFDB6@cherry.ease.lsoft.com>; Tue, 27 Jan 2004 19:28:30 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 6569 for PICLIST@MITVMA.MIT.EDU; Tue, 27 Jan 2004 19:28:22 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 1341; Tue, 27 Jan 2004 19:28:20 -0500 Received: from ns1.cypress.com [157.95.67.4] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Tue, 27 Jan 2004 19:28:19 EST X-Comment: mitvma.mit.edu: Mail was sent by ns1.cypress.com Received: from corpmail.cypress.com (corpmail [157.95.1.2]) by ns1.cypress.com (8.12.10/8.12.10) with ESMTP id i0S0KfMZ024567 for ; Tue, 27 Jan 2004 16:20:41 -0800 (PST) Received: from kenmore.ipdsd.cypress.com (kenmore.ipdsd.cypress.com [157.95.129.67]) by corpmail.cypress.com (8.12.10/8.12.10) with ESMTP id i0S0PMXo021545 for ; Tue, 27 Jan 2004 16:25:22 -0800 (PST) Received: from aiw ([157.95.129.128]) by kenmore.ipdsd.cypress.com (8.11.6+Sun/8.11.6) with ESMTP id i0S0SDg08306 for ; Tue, 27 Jan 2004 16:28:13 -0800 (PST) MIME-Version: 1.0 Priority: normal References: <40151C8E.30886.10AF4A3@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Message-ID: <401692EC.30901.6C18DFC@localhost> Date: Tue, 27 Jan 2004 16:33:48 -0800 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Andrew Warren Organization: Cypress Semiconductor Subject: Re: [PIC:] duplicate device IDs in the 18F series To: PICLIST@MITVMA.MIT.EDU In-Reply-To: <000101c3e4a9$93717c80$0b00a8c0@PAARD> Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856001 Wouter van Ooijen wrote: > As far as I can make out from the datasheet they realy have less > FLASH, the remaining is ROM. That seems unlikely, especially since they have the same device ID as an all-flash PIC. > > it's trivially easy, in most cases, to overcome the restrictions > > on CALL destination addresses in the 12-bit parts. > > It is just the place of that one fixed bit I was complaining about. > IMHO it should be either the LSB or the MSB, not somewhere inbetween. On the 16C54, that bit IS the MSB... And if you don't count the page-select bits as part of the address, it's the MSB on the other 12-bit PICs, too. > And how do you overcome that limitation easily, without using call > vesctors or re-arraging your code? Note that I am looking at it > from the compiler writers perspective. Although the destination of every CALL must be in the lower half of a 512-word page (i.e., in the 0xnn00-0xnnFF area), there's no similar restriction on the destination of GOTOs... So you just put your subroutine entry-points at the low end of a page and have them GOTO the body of the subroutine which can be anywhere in memory. For an example "from a compiler writer's perspective", see the output of Bytecraft's C compiler; Walter Banks uses what I believe he calls "CALL islands" to solve this problem and the related problem of cross-page GOTOs. Presumably, the other C compilers deal with the problem in a similar way. I'm not familiar with JAL; is there something inherent in its design that makes this approach unworkable? -Andy === Andrew Warren -- aiw@cypress.com === Principal Design Engineer === Cypress Semiconductor Corporation === === Opinions expressed above do not === necessarily represent those of === Cypress Semiconductor Corporation -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads . Return-Path: <> Received: from mitvma.mit.edu ([18.92.0.3]) by tomts29-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040127233641.OTS19788.tomts29-srv.bellnexxia.net@mitvma.mit.edu> for ; Tue, 27 Jan 2004 18:36:41 -0500 Received: by mitvma.mit.edu (IBM VM SMTP Level 430) via spool with SMTP id 6049 ; Tue, 27 Jan 2004 18:36:37 EST Received: from MITVMA.MIT.EDU (NJE origin LISTSERV@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 0258; Tue, 27 Jan 2004 18:36:37 -0500 Date: Tue, 27 Jan 2004 18:36: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 0256; Tue, 27 Jan 2004 18:36:37 -0500 Received: from mta138.mail.dcn.yahoo.com [216.155.197.38] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with SMTP ; Tue, 27 Jan 2004 18:36:37 EST X-Comment: mitvma.mit.edu: Mail was sent by mta138.mail.dcn.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 mta138.mail.dcn.yahoo.com with SMTP; Tue, 27 Jan 2004 14:53:20 -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.00CBFA52@cherry.ease.lsoft.com>; Tue, 27 Jan 2004 16:10:50 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 3269 for PICLIST@MITVMA.MIT.EDU; Tue, 27 Jan 2004 16:10:42 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 5863; Tue, 27 Jan 2004 16:09:08 -0500 Received: from smtp-out2.xs4all.nl [194.109.24.12] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Tue, 27 Jan 2004 16:09:07 EST X-Comment: mitvma.mit.edu: Mail was sent by smtp-out2.xs4all.nl Received: from PAARD (a213-84-20-53.adsl.xs4all.nl [213.84.20.53]) by smtp-out2.xs4all.nl (8.12.10/8.12.10) with ESMTP id i0RL99Ml035244 for ; Tue, 27 Jan 2004 22:09:09 +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 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: <000a01c3e519$cedda080$0b00a8c0@PAARD> Date: Tue, 27 Jan 2004 22:09:06 +0100 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Wouter van Ooijen Organization: Van Ooijen Technische Informatica Subject: Re: [PIC:] Picstart plus as an in circuit programmer? (16F627A) To: PICLIST@MITVMA.MIT.EDU In-Reply-To: <37FB7AA6F5F9814FB634A7BF4C35A6F5640CDC@ESEALNT442.al.sw.ericsson.se> Precedence: list > Does the PS+ perform verify over the full Vcc range ? > (As a "production programmer" does ?) Nope, it's a prototype programmer. But I guess in a pinch you could use a bench supply to do a multiple-vcc verification. But combined with code protection this becomes a bit tedious. IMHO the prototype-production distinction is not so hot any more with the flash PICs. When you use a (flash) PIC for let's say a Mars rover you might of course feel different. 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 *** .. .