gnupic: Re: [gnupic] picp 0.6.7 and data eeprom of 16f873


Previous by date: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] picp 0.6.7 and data eeprom of 16f873, Nestor A. Marchesini
Next by date: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] making xwisp2 more UNIX compliant, Easy B
Previous in thread: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] picp 0.6.7 and data eeprom of 16f873, Nestor A. Marchesini
Next in thread: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] picp 0.6.7 and data eeprom of 16f873, Nestor A. Marchesini

Subject: Re: [gnupic] picp 0.6.7 and data eeprom of 16f873
From: Jeff ####@####.####
Date: 27 Oct 2005 07:01:28 +0100
Message-Id: <200510270601.j9R61Nfq024153@ylpvm25.prodigy.net>

On Wednesday 26 October 2005 09:52 pm, Nestor A. Marchesini wrote:
>
> I did a file of example that generates the same mistake, attached in
> test.tar.gz
>

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


Previous by date: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] picp 0.6.7 and data eeprom of 16f873, Nestor A. Marchesini
Next by date: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] making xwisp2 more UNIX compliant, Easy B
Previous in thread: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] picp 0.6.7 and data eeprom of 16f873, Nestor A. Marchesini
Next in thread: 27 Oct 2005 07:01:28 +0100 Re: [gnupic] picp 0.6.7 and data eeprom of 16f873, Nestor A. Marchesini


Powered by ezmlm-browse 0.20.