>only of the tools work, of course :)  that's why it's often (with
>not-so-good tools) a good idea to write your algorithm in some c compiler
>that has a debugger that works, and then port it to the pic. i really don't
>understand why they all have such a hard time to make the cod files work
>with all the compilers and all the emulators/simulators. i use hitech c and
>the tech-tools emulator, and it doesn't work either. and one blames it on
>the other...
>
>ge
>

How could I stay quiet with an open invitation that that!

First, the COD file format is supported to different degrees by different
compilers, simulators and emulators.

Some of the compatibility problems are possible due to different
interpretations of the COD spec, others have been due to incomplete
encoding of debug information in the spec. and still others are probably
due to incomplete parsing of the COD file.

We at TechTools took considerable time and effort to not only interpret the
COD spec, but to look at how ALL of the compiler companies had interpreted
it.  In other words, we did not just build a parser that matched our
interpretation of the spec.  We also inspected the COD files generated by
Byte Craft, HI-TECH, CCS, MPLABC and MPASM to see how THEY interpreted the
spec.  We then developed a COD parser that accomodated all interpretations.

I am not aware of any finger-pointing in regard to COD file support of any
compiler and our TDE/ClearView Mathias.

You mentioned that you are using HI-TECH C...have you tried thier latest?
They just released improved support for COD files.  Registered HI-TECH C
owners can download it from their web pages at   http://www.htsoft.com/



Jerry Merrill

jerrym@tech-tools.com
http://www.tech-tools.com
FAX: (972) 494-5814
VOICE:(972) 272-9392
TechTools
PO Box 462101
Garland,  TX  75046-2101