Re: [avr-chat] ATMEL AVR UART Bootloader for AVR-GCC/avr-libc on ATmega16 with avrdude

[Alex Eremeenkov]

Joerg Wunsch writes:
> Alex Eremeenkov <address@hidden> wrote:
>
>   
> > I haven't board near now, so can't check that i got from latest
> > avrdude.  But first difference that i see it's a that your
> > bootloader return correct buffer size for memory access with better
> > h/w and s/w version.
> >     
>
> I think that's been only an issue in your very old AVRDUDE version
> (5.1).  I bet AVRDUDE 5.8 did already much better in that respect.
>
>   
In my case 5.1 version work better - i am able to read/erase memory. 
With newer once - i can't do with memory almost nothing.
Also in docs Martin write about using 5.1 version and i try this oldest 
one after 5.8 don't work


> > > > Programmer supports the following devices:
> > > >     Device code: 0x80
> > > >     Device code: 0x75
> > > >         
>
>   
> > > That's suspicious.  A bootloader should never announce support for
> > > more than a single MCU type.
> > >       
>
>   
> > So in my case, it success with code 0x75, other one just ignored.
> >     
>
> Yes, but a bootloader cannot possibly run on more than a single MCU
> type (at any particular point in time).  Offering a list of device
> codes was intended for the AVR910 standalone programmer (and was a big
> misconception anyway, so now, the device signature is used instead),
> but makes no sense for a bootloader.
>
> Martin Thomas' bootloader reported only one device code for me, but
> more than one in your case.  So I think you did something different
> here.
>
>   
I  just remember that, for a some reason, my bootloader returns 5 bytes 
instead of 1 in your log for request of MCU type.

> > Can i ask you to run your avrdude again with additional -vvvv option
> > and sent result full log to my email?
> >     
>
> Will do in private mail, to not clutter the list.
>
> Btw., I just released AVRDUDE version 5.9.  The log I'll send to you
> is from that version.
>
>   

After watching on log, looks like i have points for me - check and fix 
communication process
between bootloader and avrdude,
because its partially incorrect in my case. Hope it will work  pretty 
fine after  fix my issues.
Thank you for a help.

--
Best regards,
Alex Eremeenkov