gnupic: Re: [gnupic] picp 0.6.7 released
Subject:
Re: [gnupic] picp 0.6.7 released
From:
Wayne Topa ####@####.####
Date:
18 Jul 2005 04:04:34 +0100
Message-Id: <20050718030322.GB19107@intergate.com>
####@####.#### is reported to have said:
>
> On Sunday 17 July 2005 05:54 pm, Wayne Topa wrote:
> >
> > www.sparkfun.com sells a "MPLAB Compatible 8/14/18/28/40 Pin ZIFF+ICSP
> > programmer. They say it is "fully recognized under MPLAB as a
> > PicStart+ device". From the above it seems to fit your Picp to a tee.
> > Am I correct? I write this as I'm downloading picp and friends.
> >
>
> It appears to be the Olimex programmer, which should work, but I don't have
> one to test with.
>
Then I will just have to report back to you when mine gets here. :-)
> You may need to modify the programmer support section in the pic definitions
> in file 'picdev.c' for it to work. It depends on how the programmer
> identifies itself. If it reports that it's a PicStart Plus, then it should
> work with picp. If not, I've begun adding support for Olimex in picdev.c, but
> someone else will have to test it.
Will test and report back.
>
> BTW, in the next version of picp, device info will come from a configuration
> file rather than being compiled into the code.
>
> The config file can have either a short version to keep its size small:
> (example entry)
>
> [16F84]
> 0 0 0 0 0 0 0 0
> 0 0 0 0 0 0 0 0
> PICSTART WARP JUPIC
>
> [16F84:def]
> 04 00 3f ff 3f ff 00 7f
> 00 7f 3f ff 3f ff 00 ff
> 00 ff 00 00 00 00 00 00
> 00 01 20 00 04 20 07 01
> 00 00 00 40 00 00 00 00
> 03 01 02 0f
>
> [16F84:defx]
> 3f ff 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00
> 3f ff 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00
>
> or a long version more meaningful to humans:
>
>
> [16F84] ; pic definition
> 0 ; config word: code protect bit mask
> 0 ; config word: watchdog bit mask
> 0 ; Word alignment for writing to this device
> 0 ; Configuration memory start address
> 0 0 ; ID Locations addr and size
> 0 ; Data eeprom address
> 0 ; number of words in cfg bits with factory set bits
> 0 0 0 0 0 0 0 0 ; fixed bits mask
> PICSTART WARP JUPIC ; bit map of supporting programmers
>
> [16F84:def]
> 04 00 ; size of program space
> 3f ff ; width of address word
> 3f ff ; width of data word
> 00 7f ; width of ID
> 00 7f ; ID mask
> 3f ff ; width of configuration word
> 3f ff ; configuration word mask
> 00 ff ; EEPROM data width
> 00 ff ; EEPROM data mask
> 00 00 ; Calibration width
> 00 00 ; Calibration mask
> 00 00 ; ??
> 00 01 ; ??
> 20 00 ; address of ID locations
> 04 ; size of ID locations
> 20 07 ; address of configuration bits
> 01 ; size of configuration register
> 00 00 ; address of data space
> 00 40 ; size of data space
> 00 00 ; address of internal clock calibration value
> 00 00 ; size of clock calibration space
> 03 ; additional programming pulses for C devices
> 01 ; main programming pulses for C devices
> 02 0f ; ?? ZIF configuration ??
>
> [16F84:defx]
> 3f ff 00 00
> 00 00 00 00
> 00 00 00 00
> 00 00 00 00
> 3f ff 00 00
> 00 00 00 00
> 00 00 00 00
> 00 00 00 00
>
> Picp will read either format.
Very nice! I think even I could understand that...
I got gpicp up and running and it looks really good. I look forward
to getting the PIC-MCP-C running on it.
Thanks Jeff
Wayne
--
Any programming language is at its best before it is implemented and
used.
_______________________________________________________
