gnupic: Re: [gnupic] picp .hex file problem


Previous by date: 15 Aug 2005 13:51:48 +0100 Re: [gnupic] Learning PIC on the job, Rob Hamerling
Next by date: 15 Aug 2005 13:51:48 +0100 Re: [gnupic] Learning PIC on the job, Byron A Jeff
Previous in thread: 15 Aug 2005 13:51:48 +0100 Re: [gnupic] picp .hex file problem, Chen Xiao Fan
Next in thread:

Subject: Re: [gnupic] picp .hex file problem
From: Byron A Jeff ####@####.####
Date: 15 Aug 2005 13:51:48 +0100
Message-Id: <20050815125143.GB13347@cleon.cc.gatech.edu>

On Mon, Aug 15, 2005 at 09:13:57AM +0200, Gabor Kiss [Bitman] wrote:
> >The 16F88 must be programmed to a 4 word boundary. The purpose of the
> >multiword write is to speed up the time necessary to write the program
> >memory.
> 
> Weeks ago I found a similar problem with 16F87[67]A.
> It seems that these chips must be programmed in two word chunks.

Actually it's 4/8 word chunks for the 16F87XA series.

> Meanwhile 16F87[67] has no such restriction.

Correct. It writes one word at a time.

> And I did not find any information about this "feature" in
> the programming specification.

It's right in the algorithm in Figures 2-2 and 2-3. There's
is a IF flowbox that asks "Eight loads done?". Also in the
datasheet in section 3.6 they discuss that to self program that
you must do 4 loads at a time.

Pretty much any PIC part that has more than 2K words of
program memory will have multi-word writes now.

BAJ

Previous by date: 15 Aug 2005 13:51:48 +0100 Re: [gnupic] Learning PIC on the job, Rob Hamerling
Next by date: 15 Aug 2005 13:51:48 +0100 Re: [gnupic] Learning PIC on the job, Byron A Jeff
Previous in thread: 15 Aug 2005 13:51:48 +0100 Re: [gnupic] picp .hex file problem, Chen Xiao Fan
Next in thread:


Powered by ezmlm-browse 0.20.