gnupic: Re: [gnupic] Dodgy addresses in LST xref of COD files


Previous by date: 25 Apr 2006 09:00:51 +0100 Piklab now supports PICkit 1 and PICkit 2 along With ICD2 under Linux, Xiaofan Chen
Next by date: 25 Apr 2006 09:00:51 +0100 Re: [gnupic] Dodgy addresses in LST xref of COD files, Scott Dattalo
Previous in thread:
Next in thread: 25 Apr 2006 09:00:51 +0100 Re: [gnupic] Dodgy addresses in LST xref of COD files, Scott Dattalo

Subject: Re: [gnupic] Dodgy addresses in LST xref of COD files
From: Robert Pearce ####@####.####
Date: 25 Apr 2006 09:00:51 +0100
Message-Id: <YLsjoWAqbdTEFwAK@jonah.huneausware.local>

On Sat, 22 Apr 2006, Robert Pearce ####@####.#### wrote :
>
>What I find is that for _some_ of these cases, when linked, the 
>generated COD file declares some lines wrongly in the list file 
>cross-reference.

OK, I fetched the source and had a grub around. Here is a patch that 
fixes this. I've checked it produces identical .hex .map and .lst files, 
and the only .cod difference is that the addresses are now right.

-- 
Rob Pearce                       http://www.bdt-home.demon.co.uk

The contents of this | Everyone wants results, but no one is willing to do
message are purely   | what it takes to get them.
my opinion. Don't    |  -- Dirty Harry
believe a word.      |

[Content type application/octet-stream not shown. Download]

Previous by date: 25 Apr 2006 09:00:51 +0100 Piklab now supports PICkit 1 and PICkit 2 along With ICD2 under Linux, Xiaofan Chen
Next by date: 25 Apr 2006 09:00:51 +0100 Re: [gnupic] Dodgy addresses in LST xref of COD files, Scott Dattalo
Previous in thread:
Next in thread: 25 Apr 2006 09:00:51 +0100 Re: [gnupic] Dodgy addresses in LST xref of COD files, Scott Dattalo


Powered by ezmlm-browse 0.20.