SV: [avrdude-dev] avrdude: stk500_getsync error message

[Peter Warlich]

Hi,

yes, it was a typo. The value for lfuse is 0x7F.
Regarding Vtarget<Varef, this is shown in the output file
like this because I forgot to set the Vtarget jumper on the
STK500 board at that time.
But it did not change the programming behaviour when the jumper
was set.

Anyway, at the end I did succeed to program my device without
getting the error message every second time or having to reset
the STK500 prior to programming. I switched to another machine
with W2k installation and suddenly it worked.
Probably there is some kind of problem with my com1 port, even if I run
W2k SP4 and there are no conflicts or problems reported for the
com1 port. I use the com1 port also for other purposes and there
it works fine.
I have seen in the avrfreaks.net forum that two other guys had
experienced the stk500_getsync problem as well, but there was no
solution presented.
If I use a USB to RS232 converter (not at com1) then it works
fine as well.
I have an ICH3-M southbridge.

/Peter


> -----Ursprungligt meddelande-----
> Från: Martin Thomas [mailto:address@hidden
> Skickat: den 5 juni 2004 17:41
> Till: Peter Warlich; 'E. Weddington'; address@hidden
> Ämne: Re: [avrdude-dev] avrdude: stk500_getsync error message
>
>
>
> Hi Peter et al,
>
> I could not reproduce your problem here.
> Setup: STK500 (same HW and FW-Versions), ATmega16,
> avrdude-"W32 0.5" (same as in WinAVR 4/04), direct
> RS232 connection to PC and connection with an
> USB to RS232 converter, W2k SP4
>
> Given command-line by PW (mail 3 Jun):
> > avrdude -p m16 -c stk500 -U hfuse:w:0xC0:m -U lfuse:w:0c7F:m
> I expect the value for the lfuse is a typo and should be 0x7F.
> I've programmed this values in a loop around 30 times on a
> mega16 without any program/read/verify problem and without
> reseting the STK inbetween.
>
> Output from PW's test (mail 4 Jun):
>  > Programmer Type : STK500
>  > Description     : Atmel STK500
>  > Hardware Version: 2
>  > Firmware Version: 1.15
>  > Vtarget         : 4.1 V
>  > Varef           : 5.1 V
>  > Oscillator      : 3.686 MHz
>
> Setting Vtarget<Varef is no good idea. This may "confuse" the
> STK500-firmware or the target and may cause your problems.
> (I will not try to "misconfigure" my STK500 to this voltages.)
>
> HTH,
> Martin
>
>
>
>
>
>
>
>
> ----- Original Message -----
> From: "Peter Warlich" <address@hidden>
> To: "'E. Weddington'" <address@hidden>; <address@hidden>
> Cc: "'Martin Thomas'" <address@hidden>
> Sent: Thursday, June 03, 2004 5:40 PM
> Subject: SV: [avrdude-dev] avrdude: stk500_getsync error message
>
>
> >
> > > > Hi,
> > > >
> > > > I am using avrdude 4.3.0 and an STK500 (v1.46) to program
> > > my target board
> > > > with an ATmega16 on it.
> > > > If I attempt to program the flash or the fuses I get the
> > > following message
> > > > (have not tried the EEPROM):
> > > >
> > > > avrdude: stk500_getsync (): not in sync: resp=0x15
> > > >
> > > > If I retry the programming or power cycle the stk500 board
> > > before the
> > > > programming it works fine.
> > > > This occurs if I run avrdude from a command line or from
> > > WinAVR (040404).
> > > >
> > > > Example of fuse programming command I use:
> > > > avrdude -p m16 -c stk500 -U hfuse:w:0xC0:m -U lfuse:w:0c7F:m
> > > >
> > > > Can somebody help me to get around this problem?
> > > >
> > >
> > > Does the problem happen every time? Or only every once in awhile?
> > >
> > > For other reader's information: the avrdude in WinAVR
> 20040404 is the
> > > experimental win32 version from Martin Thomas (who I've CC'd).
> > >
> > > Eric
> > >
> >
> > It does happen every time. I always have to execute the
> command two times
> > before it starts programming.
> >
> > 1. time: avrdude: stk500_getsync (): not in sync: resp=0x15
> > 2. time: avrdude: AVR device initialized and ready to
> accept instructions
> > ... (starts programming)
> >
> > If I power cycle the STK500 before the programming then
> there is no error
> > message
> > and it starts programming at the first attempt.
> >
> > /Peter
> >
> >
> >
>