My DOTA app. for customer app. has been working fine: Downloads, reboots and installs new FW automaticaly but recently I 've found some modules on wich the FW gets downloaded and calling adl_adInstall( ) makes the module go weird:
The module does not reboot automatixally, every AT command responds error except for AT+WDWL? wich responds:
+WDWL: QRY
and when I powercycle I can see it didn’t installed the new FW.
I check the return codes of adl_adWrite ( ) and is accepting the FTP data. My code is the exact same code that has been working on other modules…
Same problem, I successfully downloading application using GSM channel, calling adl_adInstall( ) but module doesn’t rebooting (also it doesn,t respond on any At commands, only hardware reset helps).
I,ve found that adl_gpsSubscribe in initialization code of application caused this error this DOTA adl_adInstall( ) function. But using adl_gpsUnsubscribe function befor download process doesn’t help.
Please give some information about features of DOTA API.
hi,
i faced this problem too and i solved by switching AT mode.
Before executing adl_adinstall function, you must switch to AT mode. Then the module restarts automaticly after adl_adinstall as expected.
About these funny “Credits”… what is that?
Maybe a silly question, but how does the adl_fcmReleaseCredits(…) function work?
Where can I read the number of credits to release?
For me it is clear, that the module needs to be in AT mode to make sure that install/reboot is performed.
I’ve tried it with no debug information active, and the reboot is not performed while in data mode.
It could be some +wind responses that fills the buffer, I’m not sure.
The release All credit function makes no difference.
I seem to recall in the other thread that “blocked” AT responses (eg, unsolicited responses while flow control is asserted) can have the same effect?
Have you looked at the other workarounds mentioned in that thread.
As noted in the other thread, I think this really is a serious bug in DOTA - at the very least, Wavecom need to give a clear and complete description of precisely what is necessary &/or sufficient to guarantee that the install/reboot is performed correctly.