Open AT Firmware 7.4 Release note

2.1. Software Identification.
2.2. Compatibility.
2.3. Certifications.
2.4. Upgrade Files.

3. KNOWN RESTRICTIONS.
4. INTERFACE MODIFICATIONS.
5. CORRECTIONS & IMPROVEMENTS.

1. New Features.

This section lists the features added from the previous Open AT^® Firmware 7.3a.

Pre-programmed flash for WMP : software package in WPK format allows to create a flash image through DWLWin tool (4.1.6.13 or further). This image can be used to pre-program flash to ease the Wireless Microprocessor production.

Auto quad-band: In auto quad-band mode, the Wireless CPU^® automatically chooses between the 900/1800 MHz bi-band or the 850/1900 MHz bi-band according to the radio environment. This feature is only available in beta stage. For more information, refer to AT+WMBS in AT commands Interface Guide.

Silent Sim Toolkit: In silent Sim Toolkit mode, the Wireless CPU^® can receive and execute Sim Toolkit commands coming from the network without disturbing the customer application by several indications. For more information, refer to AT+STSF in AT commands Interface Guide.

1K-Xmodem download through USB and UART2: The new bootloader is supporting the 1K-Xmodem protocol over USB and all UARTs to download a new binary in DWL format (either bootloader, Open AT^® Firmware or Open AT^® applications). It also means that the M2M Studio is able to download over USB and all UARTs any binary in DWL format. This feature is only available in beta stage. For more information, refer to AT+WDWL in AT commands Interface Guide.

Wireless CPU ^® default serial port is UART1 and USB: UART1 and USB serial ports are activated by default for all Wireless CPU^® produced with Open AT^® Firmware 7.4. This feature is only available in beta stage.

The following table summarizes the certifications passed for this software version.

The following table summarizes the files needed to upgrade your Wireless CPU^® with this Open AT^® Firmware version.

(*) : It is assumed that the former Open AT ^® Firmware v7.x has been already installed on your Wireless CPU ^® .

Note: Open AT ^® Application built with a version before Open AT ^® Software Suite v2.10 has to be rebuilt with this Open AT ^® Software Suite

For the upgrade procedure, you can refer to:

• The M2M Studio in-line help for upgrade procedure through M2M Studio
• The upgrade procedure through DWLwin
• The upgrade procedure through X-modem
• The upgrade procedure through DOTA2

3. Known restrictions

Id	Description (What / When)	Impacted Domain	Impacted Sub Domain
41086	When AT commands sequence (combination of multiple and single commands) is sent quickly from external application, the response is not received in proper order.	AT	OTHER
41916	When the application use the AT+CUSD command to send USSD strings to the network by using the GSM 7 bit default alphabet table (defined in GSM 23.38 specs) and when the USSD string contains some extended characters like [,], {,}, , ¦, ~ and ^, that are not defined into the GSM 7 bit alphabet table, the Wireless CPU® replaces each extended characters by 0x20.	AT	OTHER
41921	When +WDIAGI indications are activated (AT+WDIAG command), some unsolicited responses are returned by the Wireless CPU® during an outgoing data call between CONNECT and NO CARRIER responses. These indications should not be returned.	AT	OTHER
41927	A command is sent and an unsolicited response (+CREG: 2) is returned before the OK response. Normally the unsolicited response has to be returned after.	AT	OTHER
41929	Autobauding is not able to resynchronize with the modem after a NO CARRIER response is received after releasing an active GSM data call. This is only met if customer changes speeds between establishing and releasing the data call.	AT	OTHER
41934	Interrogating the Call Forwarding state on a specific class (voice (AT+CCWA=1,2,1 )or data (AT+CCWA=1,2,2) or fax (AT+CCWA=1,2,4)) returns +CME ERROR: 30. The Call Forwarding state of the required class should be returned by the Wireless CPU®. Interrogating the Call Forwarding state of all classes (AT+CCWA=1,2,7) is working.	AT	OTHER
41938	When an outgoing call is in progress (ATD command) and not yet established, +WAC command resets the ATI automaton. In this case, all AT commands sent after +WAC command and before OK response to Dial command returns the corresponding response instead of +CME ERROR: 515. The Wireless CPU® should return +CME ERROR: 515.	AT	OTHER
41947	Impossible to modify PIN1 value before receiving +WIND: 4 indication. It should be possible to modify the PIN 1 code between the moment when this code is entered (and validated) and +WIND: 4 indication.	AT	OTHER
41948	Incoming Data Call gets connected even when the IPR and the DTE-DCE data rate are different.	AT	OTHER
41950	If the SIM contains sufficient EXT files, AT+CPBW=? can return a max phone length equal to 80 digits. But if an entry with a phone number containing between 61 and 80 digits is tried to be written, +CME ERROR: 20 is returned by the Wireless CPU®. The entry should be written (if SIM contains sufficient EXT files).	AT	OTHER
41952	In SLOW CONNECT mode (AT+WGPRS=5,1) for PALM OS, when a GPRS session is launched, CONNECT response is sent as response instead of data response.	AT	OTHER
41954	When setting the speed of serial link to a speed lower than 9600, this speed is displayed into the CONNECT response instead of the data call connection rate.	AT	OTHER
41957	When AT+CGDATA=<cid> is entered, GPRS session is not activated and then "NO CARRIER" returned.	AT	OTHER
41968	When MCC Lock feature is activated and an invalid SIM is inserted, the "SIM NOT ALLOWED FOR THIS MODULE" message is not returned by the Wireless CPU® through all opened ports (physical or virtual). If only UART 1 is opened, the message is always returned through UART 1 but if several ports are opened, the message is not sent to all ports. This message should be returned by the Wireless CPU® through all opened ports.	AT	OTHER
41969	When the MCC lock feature is activated, the SIM removal is not detected in the following procedure: 1) Insert an invalid SIM card (SIM NOT ALLOWED FOR THIS MODULE is returned by the Wireless CPU®. 2) Remove the invalid SIM and insert a valid SIM 3) Enter the CHV1 code. 4) Remove the SIM. The SIM removal is not detected, +WIND: 0 is not returned by the Wireless CPU®. The SIM removal should be immediately detected and +WIND: 0 indication should be returned by the Wireless CPU®.	AT	OTHER
44395	When the AT command parser is locked (see AT+WCMF command), if an Open AT® application is downloaded and executed on the Wireless CPU®, it is possible to issue AT commands. Ideally, since the AT command parser is locked, AT commands should not be allowed, even when Open AT® application is under execution.	AT	OTHER
45350	When the WIRELESS CPU® is configured with AT+WBHV=0 (to send the terminal response of an outgoing call when the audio path is establish), the command AT+CLCC shows active call even when a wrong number is called.	AT	OTHER
45835	If user configures CGAUTO different from default value (3), it is impossible to answer to an incoming GSM voice call (automatic or manual).	AT	OTHER
47805	If an OPEN AT® application is started and when the user establishes a GPRS call, the +ILRR indication is returned by Wireless CPU® after the call (i.e. after the NO CARRIER indication) and not before the switch in data mode (before the CONNECT indication).	AT	OTHER
49812	If a port, where the auto answer has been configured (ATS0), is closed, the auto answer value is reset to zero.	AT	OTHER
52024	As a response to "AT+WGPRS=?" command, the PDP context identifier should be in the range of 1-4 and not in the range of 0-4.	AT	OTHER
52081	Wireless CPU® can reset if user wants to enter in DATA mode or exit from DATA mode on a closed port.	AT	OTHER
53004	Audio (Melody) is stopped when a Call Waiting indication is received for the second incoming call over an ongoing call. No melody is heard after the BEEP sound of the Call Waiting indication as the audio resource SPEAKER is now allocated to Call Waiting indication and context for audio (Melody) is lost.	AT	OTHER
53529	When AT+CFUN is sent from 0x80 and UART1 is closed using AT+WMFM=0,0,1, then just after initialization data abort error occurred. This is due to fact that when we try to get context for UART1 the firmware returns NULL.	AT	OTHER
53848	When repeatedly sending blocks of data for some time with AT+CPOF sent through an application at regular intervals the Wireless CPU® hangs up and does not responds to AT commands.	AT	OTHER
40680	On deleting an entry while FDN to ADN swap is in progress, the module goes in hang state. No further AT commands can be processed in this state.	AT	PHONEBOOK
41928	When ME phonebook is full and SIM phonebook has 127 entries, module resets immediately after entering the PIN code.	AT	PHONEBOOK
41953	When an entry from the LND is displayed, sometimes the name field of the entry is missing.	AT	PHONEBOOK
41967	When the format used to search a phone number into a phonebook is not the same as the stored number, the AT+CPBP command does not list the matching entry.	AT	PHONEBOOK
42185	When the flash phonebook is full with all the entries with the same name, the Wireless CPU® resets when we try to delete some entries.	AT	PHONEBOOK
48610	Although, the phonebook record has not been changed, the phone book status is wrongly displayed in "+WIND 10" indication.	AT	PHONEBOOK
51561	ATDxxxxpxxxxxxxxxxxxxxxxxxxx; calls the number with the DTMF Sequence and this sequence is stored in the LND phonebook wrongly reserving an EXT Record as DTMF sequence (after 'p') should not be stored in the LND phonebook. When the user again dials a similar sequence, the number is not stored in the LND as the EXT record has been reserved by the LND for the previous dialed number.	AT	PHONEBOOK
54033	When the size of the phonebook object is set with 0xFFFF in the Wireless CPU®, a watchdog reset is observed few seconds after the SIM PIN code entry (if the SIM PIN code check is enabled) or few seconds after the SIM insertion (if the SIM PIN code check is disable).	AT	PHONEBOOK
41955	SMS present in ME is not displayed correctly in PDU format when PCCP437 character set is selected.	AT	SMS
41992	When the Wireless CPU® is configured to display and record the SMS-STATUS-REPORT, several +CDSI indication are displayed and saved into memory for the same SMS (instead of only one per SMS).	AT	SMS
48617	If a user send or write the SMS with DCS as default GSM and store it in ME memory, then the SMS data when read is not displayed correctly. The bytes in the user data field got changed. This problem is not reproducible when SM memory is used.	AT	SMS
51793	When a get input is received with @ (i.e 0x00) in the text string, only the characters before the @ are displayed. It is because the intermediate response can only display a null-terminated string.	AT	STK
53962	When SIM Tool Kit feature is activated (see +STSF command description) and if an application requires the SETUP MENU using AT+STGI=0 command, the OK response to the command is returned after 2 +STGI response even if more +STGI responses have to be returned by the Wireless CPU®. These indications are then returned as unsolicited responses instead of intermediate response. All +STGI indication for SETUP MENU should be returned as intermediate responses.	AT	STK
53506	Power consumption does not reduce in off mode after the AT+CPOF command is issued from Open AT® application.	DEVICE	ADC/BAT
49559	Using AT+W32K=1,0 and AT+CMUX AT commands to authorize Slow idle mode on enabled CMUX com port and ignoring DSR state, the Wireless CPU® does not enter low power mode.	DEVICE	MUX
41981	When an Open AT® application is running, indicating on which unsolicited response a RI PULSE should be made using +WRIM does not work and RI pulse is not working. Currently, if bit 16 of 2nd parameter of +WRIM command is activated, RI pulse will happen for all unsolicited response when an Open AT® application is running. The behavior should be the same than when no Open AT® application is running : selecting specific unsolicited responses on which RI pulse is made should work when an Open AT® application is running.	DEVICE	V24
54153	In case the Wireless CPU® is in sleep mode the customer is not able to notice the mode as sleep mode because the CTS signal does not follow the DTR signal. CTS signal should not follow the DTR signal in case of normal mode but in case of sleep mode the CTS signal should follow DTR signal.	DEVICE	V24
51372	When the startTime option is used in monitoring (using IDS), the monitoring parameters which use timer does not work properly.	Embedded RDMS	RDMS
52346	When an update package tries to be downloaded by a device using IDS services and when the user agreement for download is activated, a "+WDSI: 2" indication is returned by the device. If the application decides to launch another IDS session with the server using AT+WDSS=1,1 instead of responding to the user agreement using +WDSR command, the download is made. In this case, the response to +WDSS command should be OK, a new "+WDSI: 2" indication should be returned indicating that the user agreement for download is requested and the package should not be downloaded.	Embedded RDMS	RDMS
52636	When a manual fallback is asked with the +WDSF command whereas no install succeeded before, the manual fallback should be failed and +WDSF should be answered an error.	Embedded RDMS	RDMS
53965	When the URL set in internal e2p is wrong, the Wireless CPU® doesn't display any +WDSI indications, or it displays a +WDSI: 4 indication (it shouldn't, no socket is opened).	Embedded RDMS	RDMS
54016	Using IDS service, the Wireless CPU® can send an automatic report to the IDS server when a trigger is configured for coverage. When the triggered value is reached, the value sent to the IDS server can be out of range (range = [0-100]). The value should be always in range and correct. Workaround: On server side, when an automatic report is received for coverage in case of trigger, a GET command can be requested for coverage (the value is always correct in this case).	Embedded RDMS	RDMS
41900	Slow network synchronization when no antenna is connected.	HWL	RF
41903	In the RTE mode, with some applications which use the ADL API frequently (e.g. to send/receive a large amount of data), the application should sometimes stop on an assertion failure (afxtempl.h file, line 666). Most of time, using the "Ignore" button should allow the application to go further.	OTHER	OTHER
47870	When attempting to use simultaneously CS2 & ADD25 signals (which are multiplexed on the same pin) no error is given to the ADL application.	OTHER	OTHER
48161	Interrupts raised with a frequency higher than 1kHz lead to a watchdog reset as soon as a flash memory erase operation occurs.	OTHER	OTHER
52295	TCU Capabilities indicate that no event capture or detection pin is available in fact two pins are available for the customer applications.	OTHER	OTHER
53196	In Telemetry sample, before writing into flash, the flash handle is not subscribed (there is no usage of "adl_flhSubscribe()"), this causes problem while saving the parameter via custom command +IOSET and +TEL.	OTHER	OTHER
49719	Even if the IDS feature is in prohibited state (see +WDSG command), if the firmware was downloaded in the WIRELESS CPU® using a WPK, the IDS related flash volume is allocated (one 64kB sector for a 32Mb flash and four 64kB sectors for a greater capacity flash). Then, AT+WOPEN=6 command sets and returns the size of DOTA+DS volume and not only DOTA one.	OTHER	OTHER
54248	If only one frequency is available in the RF environment, in Autoquadband configuration, the application fails to register.	HWL	RF

This section lists the interfaces that have been modified from the Open AT^® Firmware 7.3a.