Currently: the LEDs on the SDK board flash off and on permanently with a 1 second period. HyperTerminal gets absolutely no response from the SDK board (HyperTerminal doesn’t even display any powerup WIND indicators). Battery or soft reset has no effect. If I enable the ‘boot’ switch on the SDK board, HyperTerminal displays üüü üüü üüü instead of the expected üüüüüüüüüüü. A can’t even get in to stop the application if that’s whats causing this funny response.
What I did: I loaded application firmware to the device. I’ve been doing this for the past few weeks now with no problems. No hardware touched today, so it’s not like a static discharge is to blame or anything.
Any advice? I’ve since swapped out the Q2686 for another one and am carrying on, but I’m very concerned that the other module is now useless.
Looking forward to any suggestions!
I have exactly the same issue. I can still download new application firmware in it with DWLWin, or erase the application, but the modem keeps resetting.
It looks like the OS (6.61) is not working correctly anymore. I can only upload a new OS via the X-modem protocol and that’s impossible due to the continuous resetting.
Perhaps a watchdog reset has occurred during firmware install.
Did you already manage to find out the cause of the problem?
If not I will contact my distributor and they will ask the question to Wavecom.
I did not receive a reply yet, but I have sent 3 modems with this issue to Wavecom for analysis.
I have downloaded OS 6.61 via DWLWin and erased my application and data, but the modem still resets.
I’ll post a message here when I have received an answer from Wavecom.
I received feedback on the three modems I sent to Wavecom:
We performed an analysis on this Wireless CPU and found that the problem is a known behaviour (cf CUS39756 and CUS40023).
The problem may occur when a A&D volume which is in a bad state has been formatted or assigned a new size.
Then an unexpected reset occurs while recompacting the A&D memory.
To prevent this, there should be a recompaction of the volume before any format or resize action.
The correction consists in sending an error message when the memory is in a wrong state and the user should then first recompact the memories.
This new error message will be +CME ERROR: 561 (Means : DOTA Volume State = AD_REPAIR; need Recompaction).
Unfortunately, correction for these anomalies are not in the scope of next 6.63 FW.
It will be integrated to the scope of the next FW on 6.6x branch.
If this is also the case with your modem, there is no way to get it working again, you have to take a new one