gnupic: Re: [gnupic] picp 0.6.7 and data eeprom of 16f873
Subject:
Re: [gnupic] picp 0.6.7 and data eeprom of 16f873
From:
"Nestor A. Marchesini" ####@####.####
Date:
29 Oct 2005 19:11:44 +0100
Message-Id: <4363BA29.3030209@xinet.com.ar>
I am not lucky, with the file test.hex and -wp does not record the data
eeprom memory.
I update the firmware to the version 4.30.04 and it follows the same
problem.
Of the unique form that I achieved to make it walk it is with a file
separated
to record the data eeprom memory with -wd data.hex.
I admit that I was bad in using -wd test.hex, since he is tod the
program and it is logical
that of this mistake, but using the -wp test.hex I am not capable of
recording the data
eeprom memory.
Well, I will continue trying ... thank you.
Regards
Néstor A. Marchesini
ICQ # 50983752 colo
MSN ####@####.####
####@####.####
http://www.deselectronica.com.ar
Jeff escribió:
>The log file shows that you're writing test.hex to program space and then
>trying to write the same file to eeprom space.
>
>You don't need to do that. Just -wp test.hex should write both the program
>data and the eeprom data from the hex file. If you -wd test.hex, picp will
>try to interpret the program data as eeprom data, and it exceeds the 128 byte
>limit of eeprom space.
>
>I suppose I should make it more clear in the documentation. I'll add that to
>the TODO list for version 0.6.8.
>
>Jeff
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
