gnupic: Re: [gnupic] picp .hex file problem
Subject:
RE: [gnupic] picp .hex file problem
From:
Chen Xiao Fan ####@####.####
Date:
15 Aug 2005 09:30:13 +0100
Message-Id: <3B8AEFFADD3DD4118F8100508BACEC2C07F77468@spex>
The following is from XWisp2.cfg file shipped with XWsip2 (Wisp628).
Please take note that the new 16F91x chips support
8-word (like PIC18), 4-word (like PIC16D) and 1-word
(like PIC16) programming mode according to DS41244B.
Regards,
Xiaofan
; - 'Algorithm' is the name of the required method of programming to be
; used by XWisp2 and Wisp628 for the PIC.
; Supported algorithms and main characteristics of each method:
; - PIC10 - (12-bits family '10Fxxx', etc. NOT SUPPORTED yet)
; - PIC16 - Write and read all memory regions word-by-word
; (most older midrange flash PICs).
; This is the default for the 14-bits family (12Fxxx/16Fxxx)
; - PIC16A - Write program memory 2 words at a time, read program
; memory word-by-word,
; write and read other memory regions word-by-word.
; 16F7x, 16F7x7, etc.
; - PIC16B - Write 4 words of program memory at a time,
; read program memory word-by-word
; write and read other memory regions word-by-word
; 16F87xA, etc.
; - PIC16C - Write program memory word-by-word, read program
; memory 4 words at a time,
; write and read other memory regions word-by-word.
; - PIC16D - Write and read 4 words of program memory at a time,
; write and read other memory regions word-by-word
; 16F818/9, 16F87/88, etc.
; - PIC18 - Write and read program memory 8 bytes at a time
; (single panel programming),
; write ID memory 8 bytes at a time, read byte-by-byte,
; write and read other memory regions byte-by-byte.
; All 18Fxxxx.
;
-----Original Message-----
From: Gabor Kiss [Bitman] ####@####.####
Sent: Monday, August 15, 2005 3:14 PM
To: ####@####.####
Subject: Re: [gnupic] picp .hex file problem
> 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.
Meanwhile 16F87[67] has no such restriction.
And I did not find any information about this "feature" in
the programming specification.
Moreover PICSTART PLUS reports no error during programming.
All words are "verified" even the last odd one.
Can somebody confirm my experience?
Gabor
