---- START NEW MESSAGE ---
Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP
  (SMTPD32-8.05) id A6C6448023E; Thu, 29 Jan 2004 13:10:30 -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.00CC3290@cherry.ease.lsoft.com>; Thu, 29 Jan 2004 15:18:56 -0500
Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e)
          with spool id 0746 for PICLIST@MITVMA.MIT.EDU; Thu, 29 Jan 2004
          15:18:49 -0500
Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail
          V1.2d/1.8d) with BSMTP id 1541; Thu, 29 Jan 2004 15:17:57 -0500
Received: from smtp-out6.xs4all.nl [194.109.24.7] by mitvma.mit.edu (IBM VM
          SMTP Level 430) via TCP with ESMTP ; Thu, 29 Jan 2004 15:17:56 EST
X-Comment: mitvma.mit.edu: Mail was sent by smtp-out6.xs4all.nl
Received: from PAARD (a213-84-20-53.adsl.xs4all.nl [213.84.20.53]) by
          smtp-out6.xs4all.nl (8.12.10/8.12.10) with ESMTP id i0TKHwiU067127
          for <PICLIST@MITVMA.MIT.EDU>; Thu, 29 Jan 2004 21:17:59 +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:  <002a01c3e6a4$fe2be360$0b00a8c0@PAARD>
Date:         Thu, 29 Jan 2004 21:17:59 +0100
Reply-To:     pic microcontroller discussion list <PICLIST@MITVMA.MIT.EDU>
Sender:       pic microcontroller discussion list <PICLIST@MITVMA.MIT.EDU>
From:         Wouter van Ooijen <wouter@VOTI.NL>
Organization: Van Ooijen Technische Informatica
Subject: Re: [PIC]: Problem running 'large' programs on pic, or clocking?
To:           PICLIST@MITVMA.MIT.EDU
In-Reply-To:  <000001c3e69d$950a4cc0$0f02a8c0@roo>
Precedence: list
X-RCPT-TO: <mailinglist2@FARCITE.NET>
Status: U
X-UIDL: 371856326

> Are there anything that would cause this? First guess would be the
> programmer software (PonyProg), but that writes, and then
> verifies the PIC fine every time.

1027/1028? Sure it's not 1023/1024? That would sounds like an overflow
problem to me.

Can you progger also read back the code from the chip, so you can verify
by comparing the two .hex files? You might want to use my Xwisp tool as
in 'python target f628 load <file> dump' to see what is realy in the
file.

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

.