Q2698: 2V8 supply after AT+CPOF

Legacy Legacy AirPrime modules
1

Hi All,

I’ve found a ‘feature’ with the Q2698 that is not present on the Q2686/RD.

According to the PTS, to turn the module off the ON/OFF pin must be low then the application sends AT+CPOF to the modem and waits for the modem to power down.

On the Q2686 I was monitoring the module’s 2V8 pin - which is 0V when turned off, 2V8 after ON/OFF raised to VBatt, then goes to 0V again after ON/OFF cleared to 0 and AT+CPOF sent - to be sure that the module had shut down. After doing the same sequence on the Q2698, I’ve found that the 2V8 supply remains at around 1V8 or so, and the module is still pulling approx 180mA after the power off command has been sent.

What’s happening here? Has anyone else seen this with the Q2698? Have I missed an errata note in the documentation somewhere?

Any thoughts or solutions appreciated.

ciao, Dave

2

Are you using 1400666_B (Q26 universal dev kit)? It has some issue with the on/off switch. On 1400654_B (an older Q2698 specific dev kit, which I doubt is available anymore) +CPOF & on/off works fine with the latest 7.53 beta version.

You should probably contact your FAE or distributor to fix your dev kit (if you are using universal dev kit).

3

Hiya,

I’m using the Q26 dev kit P/N WM0402301-111-30 (well, that’s what’s printed on the top layer silkscreen). It’s a bit long in the tooth now - but the schematics show the ON/~OFF switch (SW100) being connected as per this picture:


Is there a problem with the ON/~OFF switch in the OFF position floating rather than being tied to GND (as it appears to do in the schematic)? The PTS just says that the pin should be ‘Released’ rather than ‘Pulled to Ground’ to turn the module off.

Is it possible to get the Demo board mods via email rather than having to send it to my Distributor - this is a rush job I’m involved in at the moment…

Thanks for your halp.

ciao, Dave

4

Hiya,

And just to confirm that I have the latest firmware, ATI9 returns the following:

ati9
"DWL"," SWI6200T_02.02.04.14BT R3255 CNSZXD00000132 2014/04/18 13:15:25","","Sierra Wireless",0,"","00000000","00000000"
"FW","FW_753_13.Q268Fx","B7.53.0.201404280939.Q2698","Sierra Wireless",1788672,"042814 09:39","6604dcb7","10002020"
"MODEM 3G+","Revision: SWI6200T_02.02.04.14AP R3255 CNSZXD00000132 2014/04/18 13:41:51"
"ROM","8400000"
"RAM","4000000"
"OATRAM","40000"
"DWLNAME","Q2698"

Thanks, Dave

5

Hiya,

I’ve just flashed up to the latest beta available to me and the issue still exists. ATI9 reports the following after upgrade:

ati9
"DWL"," SWI6200T_02.02.04.15BT R3275 CNSZXD00000132 2014/05/07 18:57:24","","Sierra Wireless",0,"","00000000","00000000"
"FW","FW_753_14.Q268Fx","B7.53.0.201405090945.Q2698","Sierra Wireless",1790560,"050914 09:45","a2d2d3ee","10002020"
"MODEM 3G+","Revision: SWI6200T_02.02.04.15AP R3275 CNSZXD00000132 2014/05/07 19:12:10"
"ROM","8400000"
"RAM","4000000"
"OATRAM","40000"
"DWLNAME","Q2698"

Is this a module specific issue? I’ve got to commit to PCB manufacture almost immediately and need to have a resolution or work-around. Any thoughts appreciated.

ciao, Dave