[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] AVRDude serial access problem under WinXP
From: |
Colin O'Flynn |
Subject: |
Re: [avr-gcc-list] AVRDude serial access problem under WinXP |
Date: |
Sun, 25 Mar 2007 15:21:20 -0300 |
User-agent: |
KMail/1.8.2 |
Hello,
I CAN confirm this bug. However - it is not quite as reported. The output
looks like (sorry the copy/paste between my windows and linux system doesn't
work so this is roughly what it says) when you have a stk500v2 system, but
call avrdude on windows with a stk500 option:
Sending bytes [some bytes]
STK500 Can't find Sync
ser_open.c: Can't open com1. Access denied.
The important thing here is the error occurs AFTER the port has been opened
and some data has been transferred.... so I guess it's an error with how the
STK500 v2 detection is done?
>Sorry, ser_open() just displays what it gets from the underlying
>perating system. If the operating system tells "access denied", how
>he **** should avrdude know that this was just a joke only?
So maybe for once, it isn't directly Windows' fault ;-)
Regards,
-Colin
On Sunday 25 March 2007 11:32, Eric Weddington wrote:
> > -----Original Message-----
> > From:
> > address@hidden
> > [mailto:address@hidden
> > org] On Behalf Of Joerg Wunsch
> > Sent: Saturday, March 24, 2007 1:29 AM
> > To: address@hidden
> > Subject: Re: [avr-gcc-list] AVRDude serial access problem under WinXP
> >
> > "Vrudny, Noah O" <address@hidden> wrote:
> > > And Bob, your right. It would be much better if the ser_open()
> > > exception would resolve to something like 'try -c stk500v2' instead
> > > of just 'access denied'.
> >
> > Sorry, ser_open() just displays what it gets from the underlying
> > operating system. If the operating system tells "access denied", how
> > the **** should avrdude know that this was just a joke only?
>
> Looking in ser_win32.c, at the implementation of ser_open(), I see that it
> does not print a message of
> "ser_open():failed Access Denied"
> The "failed Access Denied" part of the message must be printed from the OS.
>
> The ser_open() function (for win32) has 5 possible failure modes, and all
> of them call exit(1), instead of returning to the calling function. I find
> it odd that somehow using stk500v2 magically solves the problem. ser_open()
> is used to open the serial port, which comes before any protocol data
> exchange.
>
> There must be other things going on here.
>
> Eric
>
>
>
> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
- [avr-gcc-list] AVRDude serial access problem under WinXP, Vrudny, Noah O, 2007/03/20
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Preston Wilson, 2007/03/20
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Joerg Wunsch, 2007/03/21
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Bob Paddock, 2007/03/22
- RE: [avr-gcc-list] AVRDude serial access problem under WinXP, Vrudny, Noah O, 2007/03/23
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Joerg Wunsch, 2007/03/24
- RE: [avr-gcc-list] AVRDude serial access problem under WinXP, Eric Weddington, 2007/03/25
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP,
Colin O'Flynn <=
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Joerg Wunsch, 2007/03/25
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Colin O'Flynn, 2007/03/25
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Joerg Wunsch, 2007/03/25
- Re: [avr-gcc-list] AVRDude serial access problem under WinXP, Colin O'Flynn, 2007/03/25