I have made sync tests in various conditions with Sagem800 Vendor=1110 ProdID=900f Rev=40.0b and with: dsp_code_pots.bin (win2.031 or eagleIII DTAG 44E2EA17), CMVep.txt from win sagem 2.031 or eagle-usb 2.0.0rc3
My first test was a loop for i in `seq 1 20`; do /etc/rc.d/rc.eagleusbadsl start; /etc/rc.d/rc.eagleusbadsl cleanup; /bin/sleep 5; done It basically load the module, try to sync with 90s of time limit and unload the module Result does not vary significantly with dsp_code or CMV change. win2.031 dspcode, CMVep from win sagem2.031 : 9 failures to sync in 19 attempts eagleIII dspcode, CMVep from win sagem2.031 : 10 failures to sync in 20 attempts eagleIII dspcode, CMVep from eagleIII 44E2EA17 : 5 failures to sync in 15 attempts Time to sync in case of success was between 30 to 45 s and mostly 35 s I next try with a modified loop for i in `seq 1 20`; do resetusb; /etc/rc.d/rc.eagleusbadsl start; /etc/rc.d/rc.eagleusbadsl cleanup; /bin/sleep 5; done resetusb is a script wich remove the usb controller module :usb-uhci in my case (and so unpower the modem) eagleIII dspcode, CMVep from eagleIII 44E2EA17 : 0 failures to sync in 20 attempts So the conclusion I found from those tests are : - the problem to sync should be related to the way the reset order is taken or not by the modem, - test if the modem is in operational state if you can avoid to try to sync actually. This is still a problem because if Encapsulation value is changed, modem need to be initialised again to take the new Encapsulation. I next try to activate some debug messages but when -x 0xFFFF is added to the same line where eaglectrl -d -o, every attempt to sync fail.
