Specifications

Wireless CPU
®
Q24 Series
Interfaces
©Confidential Page: 55 / 83
This document is the sole and exclusive property of WAVECOM. Not to be distributed or divulged without
prior written agreement.
WM_PGM_Q24NG_PTS_001-005 November 20, 2007
rt the ON/~OFF signal is to use either an AT
®
on of this message is enabled or disabled via an AT command.
Note
on on these
plication from
de-as
If WI unavailable or not used, it is still
possible to de-assert ON/~OFF after a delay long enough (T
on-hold
) to ensure that the
firmware has already completed its power-up initialization.
The table below gives the minimum values of T
for all firmware versions:
ld
mi
The recommended way to de-asse
command or WIND indicators: the application must detect the end of the power-up
initialization and de-assert ON/~OFF afterwards.
• Send an “AT” command and wait for the “OK” answer: once the initialization is
complete the AT interface answers « OK » to “AT” message
1
.
• Wait for the “+WIND: 3” message: after initialization, the Wireless CPU
, if
configured to do so, will return an unsolicited “+WIND: 3” message. The
generati
:
See also “AT Commands Interface Guide” [4] for more informati
commands.
Proceeding thus – by software detection - will always prevent the ap
serting the ON/~OFF signal too early.
ND indicators are disabled or AT commands
on-hold
T
on-ho
nimum values
T
on-hold
Open AT
®
Firmware
Safe evaluations of the firmware
power-up time
6.57 & above 8 s
ses into account: power-loss recovery operations,
they are large enough to ensure that ON/~OFF is not de-asserted too early.
The above figures take the worst ca
slow flash memory operations in high temperature conditions). But they are safe
because
Remarks:
1. Typical power-up initialization time figures for best cases conditions (no
power-loss recovery, fast and new flash me
mory…) approximate 3.5 seconds
after this delay does not
example the power
emory operation, like a phone book
entry update or an AT&W command.
til switch OFF. But this is
performing
.2 Power-OFF for an
in every firmware version. But releasing ON/~OFF
guarantee that the application will actually start-up if for
plug has been pulled off during a flash m
2. The ON/~OFF signal can be left at a high level un
not recommended as it will prevent the AT+CPOF command from
a clean power-off. (see also Note in section 3.15.2
alternate usage)
1
If the application manages hardware flow control, the AT command can be sent during the initialisation
phase.