Hello Jörg,
I could not get avarice to work reliably for me under Debian X64, even the
old libusb was showing this de-synchronization I describe below.
I ended up modifying avarice to use libusb-1.0 directly.
It is a hack more than a nice clea
On Sat, Sep 1, 2012 at 12:25 PM, Francois Lorrain <
francois.lorr...@gmail.com> wrote:
> Hello Jörg,
>
> I changed my setup so the avr dragon is directly connected to the pc to
> make sure it was not a connection issue.
>
> I am still getting desynchronization, please see the attached log file at
> step 1513, there is a break packet received and then something goes wrong
> and I get incrementing "Got message seqno 1513 (command_sequence == 1514)"
> for a while until 1559 where it recovers
> but then it starts again at 1688 and then it does not recover, I had to
> stop avarice ...
> I am using the default timeouts.
>
> the libusb below is : /lib/x86_64-linux-gnu/libusb-0.1.so.4 ->
> libusb-0.1.so.4.4.4
>
> Anything I can try ?
>
> Regards
>
> Francois
>
>
> On Fri, Aug 31, 2012 at 1:44 PM, Francois Lorrain <
> francois.lorr...@gmail.com> wrote:
>
>> Hello Jörg,
>>
>> It should still be the 0.1 libusb :
>>
>> # ldd /usr/local/bin/avarice
>> linux-vdso.so.1 => (0x00007fff265da000)
>> * libusb-0.1.so.4 => /lib/x86_64-linux-gnu/libusb-0.1.so.4
>> (0x00007f743f0a1000)
>> * libbfd-2.22-system.so =>
>> /usr/lib/libbfd-2.22-system.so(0x00007f743ed9e000)
>> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f743eb86000)
>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>> (0x00007f743e87f000)
>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f743e5fd000)
>> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
>> (0x00007f743e3e6000)
>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f743e05f000)
>> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
>> (0x00007f743de5b000)
>> /lib64/ld-linux-x86-64.so.2 (0x00007f743f2d0000)
>>
>> Regards
>>
>> Francois
>>
>>
>>
>> On Fri, Aug 31, 2012 at 11:22 AM, Joerg Wunsch <j...@uriah.heep.sax.de>wrote:
>>
>>> As Francois Lorrain wrote:
>>>
>>> > For libusb, it is the default version provided by debian wheezy.
>>>
>>> Which version is that?
>>>
>>> AVaRICE still uses the libusb 0.1 API. If your libusb is 1.x,
>>> it's probably using an 0.1 API wrapper. It could easily be
>>> possible that wrapper has a bug or two.
>>>
>>> --
>>> cheers, J"org .-.-. --... ...-- -.. . DL8DTL
>>>
>>> http://www.sax.de/~joerg/ NIC: JW11-RIPE
>>> Never trust an operating system you don't have sources for. ;-)
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> avarice-user mailing list
>>> avarice-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/avarice-user
>>>
>>
>>
>
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
avarice-user mailing list
avarice-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avarice-user
