[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch]
From: |
E. Weddington |
Subject: |
Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch] |
Date: |
Fri, 14 Feb 2003 10:30:04 -0700 |
On 13 Feb 2003 at 23:14, Brian Dean wrote:
> > Version 1.10.
>
> That version should be OK, it's the same as mine. Can you re-update
> your source and try again? I don't expect it to work, but there were
> two functions that output that error message and I just fixed the code
> to report the function name correctly.
>
Updated. I get:
stk500_program_enable: unkown response=0x11
Note that "unknown" is still misspelled. :-)
But! Under verbose it *does* report successfully the hardware version
and the firmware version. And this is when I specified -P com1 which
it is hooked up to. If I turn off the stk500 or when I specify the
wrong serial port (com2) I get the message:
programmer not responding on <port>
So there's *some* level of communication going on.
On both the ppi and stk500 I thought there might be something up with
the delays on cygwin. But usleep() links in OK, and I just tested it
and it works for me.
Any thoughts?
Eric
- [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], Brian Dean, 2003/02/13
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], Theodore A. Roth, 2003/02/13
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], E. Weddington, 2003/02/13
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], Joerg Wunsch, 2003/02/13
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], Brian Dean, 2003/02/13
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], E. Weddington, 2003/02/13
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], Brian Dean, 2003/02/13
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch],
E. Weddington <=
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], Brian Dean, 2003/02/14
- Re: [avrdude-dev] ppi.[ch] -> ppi.[ch] & par.[ch], E. Weddington, 2003/02/14