Re: gputils development

> On Wed, Nov 12, 2008 at 1:24 AM, David Barnett <daviebdawg@...> wrote:
> > It's been my experience that gputils has a steep learning curve for
> > development, probably more so than the average open source project.
>

I am working in Linux, programming PICs. But sometimes I need to work in Windows as well. Maybe my comments (as an almost-BFU) would be helpful for somebody.
> so fun. gputils is good.
Agree - I have no problems so far

> gpsim is ok.
Yes, ok. I don't use gpsim too much. Maybe somebody can clarify - can I simulate the code written in C-language compiled with SDCC ? And what about code from Microchip MCC18 ? (I mean stepping through C-lang lines, not ASM lines)

> sdcc for PIC has a long way to go.
I am regularly experimenting with SDCC. A lot of things work. I can't get USB code working compiled with SDCC. I have to use MCC18 for it. Still do not konw why.  And maybe I would like to see some more optimizations to have code more compact. I do not need reentrant functions etc.

> Piklab is not moving.
I never used it

> pk2cmd works fine.
That is true. But I really miss chip autodetection mechanism similar to Windows' PicKit2 programmer. And I do not know how to show revision of the PIC. Maybe nice-to-have: automatically show ID and revision of the target PIC every time pk2cmd is run.

> Still no good debugger support.
That is definitely true. Does ANY debugger for PIC on Linux exist (even some bad debugger) ? Support of PicKit2 debugger will be really cool.

Vaclav

---------------------------------------------------------------------
To unsubscribe, e-mail: gnupic-unsubscribe@...
For additional commands, e-mail: gnupic-help@...