gnupic: Re: [gnupic] Re: picp and 16C765
Subject:
Re: [gnupic] Re: picp and 16C765
From:
Jeff ####@####.####
Date:
16 Aug 2005 00:16:01 +0100
Message-Id: <200508152315.j7FNFnbr025220@ylpvm53.prodigy.net>
On Monday 15 August 2005 12:10 pm, Adralien (sent by Nabble.com) wrote:
> Just sent you links to the files.
>
> I should mention I've tried both a version 2.01.00 picstart plus and a
> 2.30.00 version with the same results...
>
Picp works with older versions of PS+ firmware, but the protocol is not the
same. Your hex file contains two blocks of program data, one starting at
zero, and one starting at 1000 hex. PS+ firmware prior to 3.00.40 expects the
set range command to contain two bytes of address (always 0 since the code is
assumed to always be in one block starting at 0) and two bytes for size.
Starting with PS+ version 3.00.40, set range is sent as three bytes of
address and two bytes for size.
The result is that your second block of data overwrites the first block
starting at address zero, thereby "garbling" the data.
The quick solution is to download and install the latest version of PS+
firmware. If this is not practical for some reason, I can modify the picp
source to handle your situation, assuming that older PS+ firmware will accept
a non-zero address in the set range command.
Jeff
