Open AT Firmware 7.4a Release note

Oct 28, 2009 - Author: Sierra Wireless - Version 7.4a - 5799 Views
1. NEW FEATURES.
2. SOFTWARE RELEASE DESCRIPTION.

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.4.

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 now available in release stage. For more information, refer to AT+WMBS 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 still 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 now available in release stage.

2. Software Release Description

2.1 Software Identification

GSM/GPRS/Edge 3G
Software Identification R74a00 R74a00
Date of generation 10/28/09 12:57 10/28/09 17:43
Binary Size 2106632 1562980
Checksum 0x7C687CD0 0xBB124FA4
Bootloader X-modem V08b0g V08b0g
IMEI SV WMP : 0x25

Q2686/Q2687/Q2687 Classic : 0x46

Fastrack Supreme : 0x46

Q26Extreme : 0x01
Flash type 32/8 Mbits / 32/16 Mbits / 64/16 Mbits 64/16 Mbits

2.2. Compatibility

Wireless CPU® compatibility list
WMP100/WMP50/WMP150/WMP120
Q2687 / Q2687 Classic
Q2686
Q26 Extreme
Fastrack Supreme / FastrackXtend
Q39/Q52Omni/Q55/Q64

2.3. Certifications

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


GCF-CC NAPRD.03
WMP100 v3.35.0 V5.0
WMP150 v3.35.0 V5.0
WMP120 v3.35.0 V5.0
WMP50 v3.35.0 V5.0
Q2687 v3.35.0 V5.0
Q2687 Classic v3.35.0 V5.0
Q2686 v3.35.0 N/A
Q26 Extreme v3.35.0 V5.0

2.4. Upgrade Files

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

Files
Upgrade through M2M Studio (*) Wavecom Open AT® Software Suite v2.31.exe
Upgrade through DWLwin (from DWLWin 4.1.6.9 or more) WMP R74a00-cus-wmp-01.wpk
Q2686/Q2687/Q2687 Classic/Fastrack SupremeClassic/Fastrack Supreme R74a00-cus-q26-01.wpk
Q26Extreme R74a00-cus-q26e-01.wpk
Upgrade through X-modem Bootloader dwl.dwl
Firmware R74a00_full_<pnmkt>.dwl
Upgrade through DOTA2 (*) Bootloader dwl.dwl
Firmware R74a00_full_<pnmkt>.dwl

(*): 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:

3. Known restrictions

Id Description (What / When) Impacted Domain Impacted Sub Domain
ANO41916 When the Open AT 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
ANO41921 When +WDIAGI indications are activated (AT+WDIAG command), some unsolicited responses are returned by the Wireless CPU during an MO data call between CONNECT and NO CARRIER responses. These indications should not be returned AT OTHER
ANO41927 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
ANO41929 Autobauding is not able to resynchronize with the Wireless CPU 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
ANO41934 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 ERRRO: 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
ANO41938 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
ANO41947 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
ANO41948 Incoming Data Call gets connected even when the IPR and the DTE-DCE data rate are different. AT OTHER
ANO41950 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
ANO41952 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
ANO41954 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
ANO41957 When AT+CGDATA=<cid> is entered, GPRS session is not activated and then "NO CARRIER" returned. AT OTHER
ANO41968 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
ANO41969 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
ANO44395 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
ANO45835 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
ANO46467 When Wireless CPU® is in roaming and when PLMN is changed, +CREG: 5 indications are not received. AT OTHER
ANO47805 If an OAT 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
ANO52024 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
ANO54733 When auto answer is activated on a closed port, a reset happen when an incoming call is received. This reset should not happen on target because S0 command is working on the port on which is sent and auto answer is reset when the port is closed. Only can happen when a bad E2P corruption or when a bad E2P file is downloaded. AT OTHER
ANO54845 [Q26Extreme] After network registration, changing the SIM pin code 3 times with incorrect pin code, the unsolicited response +CREG: 0 is not shown (Network registration is enabled with AT+CREG=1 command). AT OTHER
ANO54848 [Q26Extreme]When the SIM pin is blocked and unlocked with the SIM PUK, no unsolicited responses +CREG: 2 and +CREG: 1 are received even when the network registration is enabled (AT+CREG=1,1). AT OTHER
CUS41983 In 14.4 Kbits V.110 connection (+CBST: 75,0,1), the CONNECT response is not sent as DATA but as AT intermediate response. Because of which, in 7E1 framing, the CONNECT string is not in the right format (framing issue). The CONNECT response should be correctly returned by the Wireless CPU® and in the right framing. AT OTHER
CUS45350 When the Wireless CPU is configured with AT+WBHV=0 (to send the terminal response of an outgoing call when the audio path is established), the command AT+CLCC shows active call even when a wrong number is called. AT OTHER
CUS49812 If a port, where the auto answer has been configured (ATS0), is closed, the auto answer value is reset to zero. AT OTHER
CUS54702 When a band change is made with a hot reset (see +WMBS command description), the OK response is returned by the Wireless CPU while the protocol stack is treating the band change. So when this OK response is returned by the Wireless CPU, the protocol stack is not ready to treat any request.
In this case, sending +CSQ command to the Wireless CPU just after the OK response of the band change with a hot reset does not return any response and no more AT commands can be sent to the Wireless CPU (+CME ERROR: 515 response is always return). The Wireless CPU should return an error to the +CSQ command while the band change is not terminated.
AT OTHER
ANO40680 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
ANO41928 When ME phonebook is full and SIM phonebook has 127 entries, module resets immediately after entering the PIN code. AT PHONEBOOK
ANO41953 When an entry from the LND is displayed, sometimes the name field of the entry is missing AT PHONEBOOK
ANO41967 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
ANO42185 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
ANO41992 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
ANO48617 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
CUS41955 SMS present in ME is not displayed correctly in PDU format when PCCP437 character set is selected. AT SMS
CUS54582 When an incoming SMS is received by the Wireless CPU and if this SMS contains a header (User Data Header), this header is displayed in text mode (see +CMGF command) even if the corresponding characters are not ASCII one. Because the Wireless does not support any SMS header, it should not be returned in SMS read response (see +CMGR and +CMGL commands) and only the SMS text (User Data) should be returned in text mode (see +CMGF command) AT SMS
ANO51793 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
CUS55408 STK application failed to send a USSD request to the network when the DCS is equal to 0x40. The Wireless CPU® shall indicate the alphabet used in the operation and shall be set to "SMS default alphabet". The language indicator shall indicate "language unspecified". (i.e. 0x0F) AT STK
ANO55287 From R7.4a, the Wireless does not return anymore +CME ERROR: 545 error when +CMUX command is sent to the Wireless CPU while a MUX session is already launched on another physical port.
Also, several MUX sessions can be launched at the same time on different physical ports.
DEVICE CMUX
CUS53392 During I2C read, when a nack appears the SCL line can stay low DEVICE IOB
ANO49559 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
ANO56345 Working with two simultaneous data flow on the both UART in CMUX mode is difficult, the data flow are often corrupted or interrupted. DEVICE MUX
CUS56232 When CMUX configuration is set and sleep mode is enabled (AT+W32k=1), sleep mode may not be effective. On DTR drop, PSC (sleep frame) is sent, but Wireless CPU® may not have entered in sleep mode. DEVICE MUX
ANO49719 Even if the Device Services are in prohibited state (see +WDSG command), if the firmware is downloaded in the Wireless CPU using the customer or production WPK, the Device Services 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 the size of DOTA one.
DEVICE OTHER
CUS53820 Whenever UART2 is opened by Open AT application using ADL API at AUTO BAUD RATE, baud rate of the UART will get fixed after the first communication with hyper terminal or any other application. The baud rate will not get changed after that which will lead to an erroneous communication with different baud rates. DEVICE OTHER
ANO55620 A MUX session cannot be opened with MuxConfTool on USB port. DEVICE USB
ANO55500 The WCPU resets if a large DLE/ETX sequence is transferred using TCP/UDP socket which is created on UART bearer using WipSoft. DEVICE V24
CUS41981 When an Open AT® application is running, indicating on which unsolicited response a RI PULSE should be made using +WRIM doesn't 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
CUS54050 The Wireless CPU crashes when the handshakes of UART2 are active (AT+IFC=2,2) and nothing is connected to UART2 (free). DEVICE V24
CUS54170 RTS signal is followed even when RTS following is disabled with AT+IFC=0,2 command. Ideally RTS signal toggling should not have any effect after AT+IFC=0,2. No Data is displayed e.g. Response for AT, when the RTS signal is set to low with AT+IFC=0,2. AT Response should be displayed as with AT+IFC=0,2 RTS signal should not impact the behavior after setting RTS to Low. DEVICE V24
ANO55836 The reverse delta is not automatically installed after an IDS update, if the new update causes watchdog resets in loop. DWL OTHER
DEV50869 During an IDS update, if the recovery mechanism has deactivated the oat application, and if there is a hard reset, an XModem download is launched instead of the update agent. DWL OTHER
ANO51372 When the startTime option is used in monitoring (using IDS), the monitoring parameters which use timer does not work properly. Embedded RDMS RDMS
ANO52244 Using IDS services, uplink and downlink bandwidths of a device are not available. However, the bandwidth calculation is always wrong and the reported values by the device should not be taken into account by the IDS server until the correction. The bandwidth calculation should be correct in order to report the correct values to the IDS server. Embedded RDMS RDMS
ANO52346 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
ANO52510 Using IDS services, uplink and downlink bandwidths of a device should be available. However, the bandwidth calculation is always wrong and the reported values by the device should not be taken into account by the IDS server until the correction. The bandwidth calculation should be correct in order to report the correct values to the IDs server. Embedded RDMS RDMS
ANO52636 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
ANO54016 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
ANO56319 [Q26Extreme]Making a connection to the IDS server using +WDSS command returns an error, when the cell capabilities are in 3G R99. The Wireless CPU® should make the connection successfully in all 3G Cell capabilities. Embedded RDMS RDMS
CUS55134 When several IDS connections are interrupted by entering into spy mode, no IDS connection can be performed. Embedded RDMS RDMS
DEV49362 The provisioning for the retry timers doesn't work Embedded RDMS RDMS
CUS54106 [Q26Extreme]The IP header compression is not functional over PPP connection. GPRS OTHER
CUS54549 Impossible to establish/receive calls when network implementation of assignment command message does not comply with 3GPP specifications (spare bit of MultiRate configuration IE set to 1 instead of 0). GSM CC
CUS55977 [Q26Extreme]The cause call of release reported by the Wireless CPU® after a voice call is always +CEER: Error 41 GSM CC
CUS56275 [Q26Extreme] Audio are opened too early in case of incoming call, and this can lead to white noise before ATA is issued. GSM CC
CUS54988 When the network signal strength is zero, and the MS is not able to retrieve the network parameters of any neighboring cells, the +CCED indication is not displayed in automatic mode. GSM RR
CUS55736 PDP Context activation fails in a specific area on Vodafone UK network when Frequency Hopping is used. Problem is observed when Ma Bitmap length (4 bits) passed to function rrc_BuildMaForL1c() becomes too big for CA. GSM RR
CUS55528 There exists an audio loss, when switching from DAI audio configuration at startup to analog audio speaker during a voice call. HWL AUDIO
CUS55126 Sometimes the Wireless CPU® may not enter the alarm mode (low power consumption). HWL OTHER
ANO41900 Slow network synchronization when no antenna is connected. HWL RF
ANO40642 Impossible to use GSM bearer with WIP, "+CME ERROR: 819" is returned when opening a SMTP channel on GSM bearer OTHER OTHER
ANO41903 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
ANO43262 When HTTP session for GET method is created using AT+WIPFILE command, “CONNECT” indication is not received over GSM bearer. OTHER OTHER
ANO43265 Sometime SMTP session cannot be created using GSM bearer. OTHER OTHER
ANO43362 The adl_InitGetType function returns ADL_INIT_POWER_ON even though the application is reset by ADL_INIT_REBOOT_FROM_EXCEPTION OTHER OTHER
ANO51156 After OSA service subscription with adl_osaSubscribe() function, if application tries to unsubscribe to the OSA service without posting back ATR request to the Wireless CPU, ADL_OSA_EVENT_CLOSED cannot be received. When application tries to subscribe the OSA service again, ADL_RET_ERR_ALREADY_SUBSCRIBED returns. OTHER OTHER
ANO52919 The TCP socket is SHUTDOWN on the receiving side when “DLE ETX” file is sent using WIPSoft through MTTY tool. OTHER OTHER
ANO53799 The ADL_INIT_DOWNLOAD_ERROR error is received while trying to write into an already finalized A&D Cell. Error ADL_INIT_DOWNLOAD_ERROR is rightly returned as it is not possible to write into a finalized cell. The finalized Cell_ID should be deleted first in order to write into it and then used to download and install the application. OTHER OTHER
ANO54043 [Q26Extreme]Reset may occur randomly on Wireless CPU®, when operated at low frequencies. OTHER OTHER
ANO55006 [Q26Extreme]The Flash LED still flashing on Wireless CPU®, even after removing the antenna (+CREG: 2). OTHER OTHER
ANO55999 [Q26Extreme]White noise may be heard on the speaker during voice call. OTHER OTHER
ANO56105 [Q26Extreme]With OSA feature, it may be impossible to establish/receive calls with some SIM cards. OTHER OTHER
ANO56157 Products using the Numonyx T8 combo are locked up when any other device is connected to the parallel port. OTHER OTHER
CUS50881 Flash writing operation take too long time. Each time a writing request is done, a complete scan is done on the flash memory space to know the remaining memory space. This process increases the writing process. So writing process should be modified to improve the flash writing operation duration. OTHER OTHER
CUS56088 The Wireless CPU® will reset, when PPP connection is established again and again (1-20times) using wvdial (On Linux-Debian). OTHER OTHER
CUS56255 Using AT+CPOF=1 with the ON_OFF pin set to ON might reset the Wireless CPU® instead of leaving it locked up until the pin is set to OFF. OTHER OTHER
DEV42759 After a KBD reset, up limit of key pressed messages is not well managed. The key press change cannot be correctly taken in count. OTHER OTHER
DEV48161 Interrupts raised with a frequency higher than 1kHz lead to a watch dog reset as soon as a flash memory erase operation occurs. OTHER OTHER
ANO51205 When local SIM is inserted activating remote SIM results in "+WIND: 0" and "+WIND: 1" indications, the remote SIM cannot be detected. SIM OTHER
ANO53297 [Q26Extreme] SIM removal feature is not functional. A reset may occur when the SIM card is removed. SIM OTHER
ANO53763 [Q26Extreme] SIM removal feature is not functional. A reset may occur when the SIM card is removed. SIM OTHER
ANO54919 [Q26Extreme]SIM card interoperability issue would exist with some 2G SIM card. SIM OTHER
ANO54980 [Q26Extreme] SIM removal feature is not functional. A reset may occur when the SIM card is removed. SIM OTHER
ANO55796 Enabling the OSA by "AT+OSASTART=1" command is not possible, if the SIM card reply the ATR request slowly. A longer timeout should be added to the Firmware when waiting for the ATR response from the external SIM. SIM OTHER
ANO56067 [Q26Extreme]Wireless CPU® may reset with some SIM cards when AT+CCID or AT+CRSM is issued. SIM OTHER
CUS50905 Unsubscribe the OSA is impossible when an APDU request is unanswered. SIM OTHER
CUS51796 Wireless CPU resets if we try to read a 256 byte SIM file with OSA SIM OTHER
CUS55444 Backtrace "!WRONG SIM CMD PARAMETER: 67xx" is received for SIM command parameter 3 every time a Wireless CPU® is started. The issue is reproducible in case false/wrong information is present in the SIM EF and the Wireless CPU® tries to read the information at startup. SIM OTHER
CUS55462 [Q26Extreme]SIM card interoperability issue would exist, if a bad TERMINAL_PROFILE response is received from the SIM. SIM OTHER


4. Interface modifications

This section lists the interfaces that have been modified from the Open AT® Firmware 7.4.

API Comment
AT+WLDB Deprecated
When a CMUX session is started on the Wireless CPU without MUX protocol establishment, the session was formerly closed after 30 seconds, from R74a it is closed only after a 5 minutes timeout.


5. Corrections & Improvements

Id Description (What / When) Impacted Domain Impacted Sub Domain Fixed in
ANO51295 The Wireless CPU® returns CONNECT XXXX for AT+CGDATA=1,1 command and produces data flow even it is not located over network. AT OTHER 7.4a
ANO52081 Wireless CPU® can reset if user wants to enter in DATA mode or exit from DATA mode on a closed port. AT OTHER 7.4a
ANO52946 If there is only one PLMN entry in the sim card, the response of command AT+CPOL? results in the infinite loop which eventually deplete all the heap resources. AT OTHER 7.4a
ANO53087 The Wireless CPU® resets when AT+CUSD command is issued large number of times to send an USSD in UCS2 format. AT OTHER 7.4a
ANO53848 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 7.4a
ANO53934 The command AT+WASR=1,1,"GpioId" gives +CME ERROR: 3 instead of expected CME ERROR: 501 when the GPIO is not allocated.
Also it returns +CME ERROR: 501 instead of expected +CME ERROR: 3 when the GPIO doesn't lies in the possible range.
AT OTHER 7.4a
ANO54124 When the SIM is removed from the SIM rack while the Wireless CPU is listing the preferred PLMN (see +CPLS and +CPOL command), a reset happens. The Wireless CPU should not reset and a specific error should be returned to AT+CPOL? command (+CME ERROR: 556) AT OTHER 7.4a
ANO54586 When the Wireless CPU® is registered on a network and camped to a cell supporting GSM and GPRS services, if the autoquadband mechanism is launched (using +WMBS command) and if a power off is requested (+CPOF, +CFUN, etc...), the Wireless CPU® launches a new registration sequence instead of making a power off. The Wireless CPU® should not register again to the network until the next start up (hot or cold restart using +CFUN command for example). This doesn't happen with a cell supporting the GSM service only (not linked to the device class) AT OTHER 7.4a
ANO54934 On issue of AT+WOPEN=2 command, the first argument was erroneous in case of firmware version B74f. For the ideal scenario, the response should be the correct version of the OS that was released with the Firmware i.e. v06.31 for FW version B74f onwards till B74l. AT OTHER 7.4a
CUS53004 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 7.4a
CUS54251 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. AT OTHER 7.4a
CUS54368 The Wireless CPU® provides an AT command in order to read the IMEI (see +WIMEI command), using it a large number of times (more than 1000 times) makes the Wireless CPU® reset. Ideally, the Wireless CPU® should not reset in this case. AT OTHER 7.4a
CUS54579 No +WIND: 9 and +WIND: 2 indications are received in case AT+WAC command is issued after an attempt to make a voice call with the command ATDxxxxxxxxxx; +WIND:9 and +WIND: 2 indications should be displayed as the functionality of AT+WAC command is used to abort only SMS, SS and PLMN selection related commands. AT+WAC should not have any effect on ATDxxxxxxxxx; command. AT OTHER 7.4a
ANO48610 Although, the phonebook record has not been changed, the phone book status is wrongly displayed in "+WIND 10" indication. AT PHONEBOOK 7.4a
ANO51561 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 7.4a
CUS54033 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 7.4a
CUS53678 The PDU response of the SMS STATUS REPORT is incorrect as some extra bytes are received when status report is stored in FLASH. Also when the status report is stored in the Elementary file of SIM, the response is incorrect. AT SMS 7.4a
CUS55211 If a user sends or write the SMS with DCS as default GSM and store it in ME memory where the character set selected is PCCP437, then the SMS data when read is not displayed correctly when ME memory is selected. The bytes in the user data field will be changed. This problem is not reproducible when SM memory is used. AT SMS 7.4a
ANO53962 When SIM Tool Kit feature is activated and if an application requires the SETUP MENU using AT+STGI=0 command, the OK response to the command is returned after two +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 responses. All +STGI indication for SETUP MENU should be returned as intermediate responses. AT STK 7.4a
CUS55764 Wireless CPU® resets when SET UP IDLE MODE TEXT with large text string is executed. AT STK 7.4a
CUS56077 New option #2 to stop STK SETUP CALL is added. User can accept call and the call is started by applicative software. AT STK 7.4a
CUS56159 If user wants to start the STK SETUP CALL by applicative software. A new option #2 is added (i.e. AT+STGR=4,2), so that user can use ATD to dial a call. AT STK 7.4a
ANO55988 When a large file is transferred through more than 1 UART (physical/virtual) there may be a data loss and data corruption (some junk characters are displayed). The integrity of the transferred data may not be intact. DATA OTHER 7.4a
ANO56043 The UART port becomes unresponsive when large data file is sent using +WIPDATA command using WIPSoft. DATA OTHER 7.4a
CUS53916 Using WIPSoft, if the DTR signal is used to switch from DATA mode (ONLINE) to AT command mode (OFFLINE), in some cases, the V24 request does not go in to OFFLINE. Even after manually trying +++ command the transition does not occur. Wireless CPU® has to be restarted to get out of this state. DATA OTHER 7.4a
CUS54044 If the GSM data call is first accepted and then released at the receiving end before CONNECT indication is received, then the call is just being held there without being connected, and at the dialer side it appears that the call is never answered. DATA OTHER 7.4a
CUS53506 Power consumption does not reduce in off mode after the AT+CPOF command is issued from Open AT® application. DEVICE ADC/BAT 7.4a
ANO55895 When a MUX session is wakeup from a sleep mode (w32k mode), the Wireless CPU® do not respond. DEVICE CMUX 7.4a
ANO55897 During w32k mode, when an incoming call is made, after receiving "RING" indication, CMUX does not respond. DEVICE CMUX 7.4a
ANO55910 When the N1 parameter value is higher than 127 in AT+CMUX command, the responses of the AT commands executed on the DLC are not displayed. DEVICE CMUX 7.4a
ANO56020 On a port configured in CMUX mode with the sleep mode enabled, we can notice the missing of some PSC (sleep frame) frames. The PSC frames are correctly sent only for the first few period. DEVICE CMUX 7.4a
CUS55923 During an incoming call, when the UART is activated in MUX mode, the physical RI pin is not triggered, ideally the physical RI pin should be triggered. DEVICE CMUX 7.4a
ANO56109 When the user switches from AT mode to DATA mode using WIPSoft, sometimes CONNECT indication is received in between the data transfer. If any application specifically checks for CONNECT after switching from AT mode to DATA mode, this will result in a failure.
To correct this issue, a new OPIC_OAT interface has been opened and called by WipSoft 5.21.
DEVICE FCM 7.4a
CUS56064 When DTE doesn't send a wakeup response, DLC disconnection may lead to a reset. DEVICE MUX 7.4a
ANO55849 When the UART speed is set to 9600 baud rate and a MUX session is launched on this UART port, the Wireless CPU® resets. DEVICE OTHER 7.4a
CUS52710 With UART2 enabled for data transfer and data being transferred using Device services, a reset of the Wireless CPU® is observed when we issue AT command from UART1 immediately after data transfer. DEVICE OTHER 7.4a
CUS54169 Customer would not be able to subscribe to the parallel bus service when UART 2 is in open state. DEVICE USB 7.4a
CUS54640 When the host closes the USB link, the communication can be broken after restarting it. DEVICE USB 7.4a
ANO43273 Wireless CPU® resets when making a data call over GSM bearer, by using WIP (WIPSoft) APIs. DEVICE V24 7.4a
ANO55580 When typing AT+IPR=XXXXX on the UART3 (UART emulated on the top of the USB stack) the target store the XXXXX speed. In case the application interrogates the target with the AT+IPR? command the target answers +IPR:XXXXX.
Such a response might destabilizes the application (its current speed let's say YYYYY and the target speed being different)
DEVICE V24 7.4a
ANO55953 With AT&D0 configuration, the Wireless CPU® may not enter in sleep mode on DTR drop. DEVICE V24 7.4a
CUS55629 When the DTR drops to switch in OFFLINE mode (i.e. AT&D1 should be sent earlier), if a data write operation is pending, this operation will be canceled, and so data will be lost. DEVICE V24 7.4a
ANO53965 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 7.4a
ANO53978 When AT+WDSS=1,0 command is executed to deactivate the IDS PDP context, whereas the IDS PDP context is already deactivated. For any IDS connection done after, always returns error code 652. Embedded RDMS RDMS 7.4a
ANO54089 On making a connection to the IDS server with the execution of the command AT+WDSS=1,1, there is a possibility of blocking the AT parser when a wrong IDS APN and a valid user APN are configured. Embedded RDMS RDMS 7.4a
ANO54257 When a download is interrupted by the command AT+WDSS=1,0, sometimes the Wireless CPU® reconnects automatically to the server and postpones the job on the server. The download cannot be resumed anymore. Embedded RDMS RDMS 7.4a
ANO54305 When the device is added on the server and then when the server sends a SMS bootstrap to the device, the SMS bootstrap is not treated by the device. Embedded RDMS RDMS 7.4a
ANO54488 Using IDS services, it's possible to configure the Wireless CPU® to initiate an automatic connection to the IDS server using polling mode (see +WDSC command). If the value for the polling mode is higher than 20 minutes, the timer between two automatic connections is not a correct value and the time is shorter than required. Advice: do not use value higher than 20 for polling mode. Embedded RDMS RDMS 7.4a
ANO54808 When a software or firmware update is launched with IDS whereas the connection was initiated by a generic alert (initiated by a monitored parameter) and a reset occurs during the download of the patch, at the next start of the Wireless CPU®, the generic alert is performed again and the update is failed. The download should be resumed. Embedded RDMS RDMS 7.4a
CUS54229 In GPRS class CG or class B with automatic GPRS attach, when the patch download is suspended the download is resumed after few minutes which is not appropriate. Embedded RDMS RDMS 7.4a
CUS54655 When an IDS connection is done (with AT+WDSS=1,1) and then the spymode is activated (AT+WREGC=1), no IDS connection can be done when the spymode is resumed (+WDSI: 7 or no response). Embedded RDMS RDMS 7.4a
CUS54922 In CG class, when an IDS connection is failed (+WDSI: 7) and then the Wireless CPU® goes in spymode (AT+WREGC=1), the Wireless CPU® may reset (a RTK exception occurs). Embedded RDMS RDMS 7.4a
ANO55198 Even if the GPRS service is not attached to the MT when AT command AT+CGDATA=1 is issued, it returns CONNECT instead of +CME ERROR: 3. GPRS OTHER 7.4a
CUS54682 Subsequent call to start a GPRS Bearer (using wip_bearerStart() or AT+CGACT=1 command) returns error (WIP_BERR_DEV), when a call to stop the previous session (using wip_bearerStop() or AT+CGACT=0,1) is followed by "AT+WAC" command. The issue is reproduced, if "AT+WAC" command is issued after stopping a bearer session and before starting a new bearer session. GPRS OTHER 7.4a
CUS54758 Call index in the +WIND: 5,x and +WIND: 6,x is equal to 2 even if +WIND: 6,1 response has been received for the first call and the call has been disconnected. As the first call has been disconnected successfully the call index for the second call should be 1 in +WIND: 5,x and +WIND: 6,x wind responses. The issue is reproduced when ATD for the second call is made before receiving the CC_REL_IND. GSM CC 7.4a
ANO54248 When the Wireless CPU® is registered on a cell providing only GSM service (and no GPRS/EDGE service), the autoquadband mechanism (see +WMBS command) is not correct. The Wireless CPU® will change every time the frequencies (850/1900 <-> 900/1800) even if the GSM service is available on one frequency. The Wireless CPU® should launch the autoquadband mechanism and should stop it when it's registered on cell. GSM OTHER 7.4a
ANO55823 It is not possible to listen to DTMF in Rx, while playing an AMR memo in Rx. HWL AUDIO 7.4a
CUS54113 When fast idle mode is activated, the part of the Wireless CPU® is shut down, the audio feature like DTMF cannot be used, when DTR is switch.
The correction wakes up the Wireless CPU® each time we need it (for any audio feature).
HWL AUDIO 7.4a
CUS54377 The generated DTMF tone might be distorted if using GPRS and WADS command at the same time. HWL AUDIO 7.4a
CUS54770 The problem occurs when playing AMR memos during a voice call. If several memo are played in a row, memos after the first one may be degraded, it occurs with a 50% rate. The problem is a degradation of the memo played, onto a degradation of the voice call. HWL AUDIO 7.4a
ANO54047 When the Wireless CPU® enters sleep mode with GSM stack (slow idle mode) and there is no network coverage, the Wireless CPU® cannot automatically retrieve network coverage i.e. considered as in sleep mode without GSM stack (slow standby mode). HWL OTHER 7.4a
ANO54589 Using low power consumption (at+w32k=1) mode and DTR as a wake-up condition, will freeze the Wireless CPU® (no wake-up) if not network is found. HWL OTHER 7.4a
ANO47516 Launching an Open AT® WIP application in RTE (Vc6 and Eclipse) mode for opening PPP in server mode, resets the Wireless CPU®. OTHER OTHER 7.4a
ANO52295 TCU Capabilities indicate that no event capture or detection pin is available in fact two pins are available for the customer applications OTHER OTHER 7.4a
ANO54160 The Wireless CPU® can reset when the customer tries to auto answer an incoming call on a closed port. OTHER OTHER 7.4a
ANO54193 TCU Capabilities indicate that no event capture or detection pin is available in fact two pins are available for the customer applications OTHER OTHER 7.4a
ANO54559 Reaction of 1,8V only, MEs on SIM type recognition failure, or MEs on type recognition of 3V SIMs, immediately after the ATR only the two commands "SELECT GSM" and "STATUS/GET RESPONSE" shall be send by the ME. The ME shall then deactivate the SIM/ME interface within 5 seconds and reject the SIM. However, ME sends a Select command instead of Status command and doesn’t deactivate the SIM. OTHER OTHER 7.4a
ANO54588 The Wireless CPU® crashes when invalid melody is provided to API adl_audioMelodyPlayExt(). OTHER OTHER 7.4a
ANO55499 When a large file is transferred through UART1 (or any physical port) there is a data loss and data corruption (some junk characters are displayed). The integrity of the transferred data is not intact. OTHER OTHER 7.4a
CUS47870 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 7.4a
CUS54074 Reading the flash memory using the pointer provided by adl_adInfo after having written data with adl_adWrite can provide a wrong result. Although the data is actually correct in flash memory, this is because of a cache memory inconsistency. OTHER OTHER 7.4a
CUS55257 The Wireless CPU® resets when executing the SEND USSD proactive command. OTHER OTHER 7.4a
CUS49814 When slow idle mode (AT+W32k=1) is activated and a timer with options (non strict, cyclic and rearmed on expiration) is running and the timer expires twice during sleep period, a reset occurs on Wireless CPU®. RTK TIMER 7.4a
CUS50328 In the RTE mode, the time delay taken to invoke the call back handler of the adl_tmrSubscribe () API is 4 times more than it normally takes. RTK TIMER 7.4a
ANO53243 Response for AT+CPWD command is not received when trying to change the SIM PIN code. Issue is faced when AT+CPWD command is given after unblocking the SIM PIN of a blocked SIM by using SIM PUK and AT+CPIN command. SIM OTHER 7.4a
ANO55164 When we issue AT+CPIN=11111111,3699 and AT+CPIN2=22222222,5678 consecutively, then the module enters busy state indefinitely. SIM OTHER 7.4a
ANO55402 The internal SIM cannot be selected in SIM_EXT_PREFFERED mode SIM OTHER 7.4a
CUS54707 Some SIM may not be powered on due to which AT+CPIN commands always return +CME ERROR:10. SIM RESET 7.4a
CUS54540 At high speed of 104 MHz, the Wireless CPU® is in a state where it is switched off immediately when ON/OFF pin is set to OFF, the auto-maintain mechanism doesn't work. SYS INIT 7.4a

Documentation

Comment

©2024 Sierra Wireless. All rights reserved.
×
You have been successfully unsubscribed to this product. To access your subscription click here.