gnupic: .COD file problems with MPLAB
Subject:
Re: .COD file problems with MPLAB
From:
Craig Franklin ####@####.####
Date:
13 Sep 2004 19:10:00 +0100
Message-Id: <4144F365.6080102@users.sourceforge.net>
Scott Dattalo wrote:
> On Sun, 12 Sep 2004, Craig Franklin wrote:
>
>> Aaron Colwell wrote:
>>
>>> I've been having trouble using MPLAB with the .cod files generated
>>> by GPLINK. After looking at
>>> the code for a little bit, I figured out that making the following
>>> change allows MPLAB to properly
>>> read the .cod files.
>>
>
> <snip>
>
>> This is a known problem. Not only with gplink, but gpasm. It is
>> first on the gpasm TODO list in the source code.
>>
>> It hasn't been changed because it requires gpsim to be changed too.
>> If gpsim makes a release soon we could change it. Scott, what are
>> your plans?
>
>
> I had wanted to make a release of gpsim a while back, but there were
> too many things that needed to change. Some of the major changes have
> been made, but (as some can surely attest) they've created bugs too.
> The last major change I need to make has to do with triggers/actions
> (what formerly were just break points). And the biggest aspect
> associated with this change has to do with using expressions as inputs
> for things like break points.
>
> Once that is done, I have to go through and update the documentation.
>
> 2 days ago I bumped the revision of gpsim to 0.21.3. However, this was
> not a release. One option is to make the gputils change, then I can
> update gpsim and make an interim 0.21.4 release. The earliest I'd be
> ready for a major release will be 4 weeks.
>
Lets try to catch the gpsim major release. I will do a major release of
gputils at the same time. You will have to update the version checks
for gpasm and gplink versions (0.13.0).
I will maintain a patch on the gputils website until the release.
It would be good if we could find all of the incompatibilities with
MPLAB at once. Anyone out there have some time to research this? You
don't have to fix the bugs, just find them. You can use gpvc and maybe
a hex editor. Manipulate the tools and find the differences.
> Scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
