[avr-chat] AvrDude programming an AtMega2561 with USBProg

[Mau]

Dear all,
I wish you all a Happy new year.

I have a problem as described in the subject line, with the addition
that the file is larger that 128K.
I already checked the following:
1) the hex intel file looks correct with the appropriate segment address
lines at correct places and with correct contents.
2) Programming directly the ELF file with AvrStudio (and the same
programmer) works.

Here is a file with the full communication between the AvrDude and
USBProg: http://www.studioferraris.it/files/AvrDude_Full.txt, and
attached there is a file containing a small excerpt of that communication.

I want to focus on the segment selection commands, which should result
in CMD_LOAD_ADDRESS sent by AvrDude to the USBProg.
According to the manual this command should contain the desired address
with the highest (32th) bit set if the command should be sent to the
target which is the case is this situation
Now I see, during programming:

avrdude: Sent: . [06] . [80] . [00] . [00] . [00]
avrdude: Recv: . [06] . [00]
then
avrdude: Sent: . [06] . [80] . [01] . [02] . [80]
avrdude: Recv: . [06] . [00]

and during verify:

avrdude: Sent: . [06] . [80] . [00] . [00] . [00]
avrdude: Recv: . [06] . [00]
then
avrdude: Sent: . [06] . [80] . [00] . [80] . [00]
avrdude: Recv: . [06] . [00]
and then
avrdude: Sent: . [06] . [80] . [01] . [00] . [00]
avrdude: Recv: . [06] . [00]

It looks to me that the second CMD_LOAD_ADDRESS sent during programming
is wrong. It looks like containing garbage after the first two correct
bytes.

Does anyone have similar problems, and is there a solution?

Thanks you all.
Mau.

AvrDude.txt
Description: Text document