Note: Your user name is not your email address.
Your account is locked out! Please click
here to unlock your account.
Your account is not activated yet. Please check your email and click on the activation link that was sent to you when you registered to our site.
Did not received the activation email? Please click here to contact us.
Login failed, username or password is incorrect.
List of Tables. 6
1. Introduction. 7
1.1. Document Scope. 7
1.2. Document Audience. 7
1.3. New Features/Enhancements. 7
2. Abbreviations and Definitions. 8
3. Related Documentation. 9
4. Compatibility. 10
5. Software Release Description. 11
5.1. Release Identification. 11
5.2. Software Tools Versions. 11
6. Software Changes Description. 12
6.1. Validated Corrections/Improvements. 12
6.2. Interface Changes. 13
7. Troubleshooting.. 14
8. Restrictions and Additional Information. 15
List of Tables
Table 1. New Features/Enhancements. 7
Table 2. Abbreviations and Definitions. 8
Table 3. Related Documentation. 9
Table 4. Hardware Compatibility. 10
Table 5. Software Compatibility. 10
Table 6. OS Release Information. 11
The scope of this document is the OS 6.53.0 release description for the AirPrime modules listed in the compatibility section.
This release note may be distributed to all direct and indirect customers and will be posted in Sierra Wireless Source.
Table 1. New Features/Enhancements
Table 2. Abbreviations and Definitions
Application Development Layer
Application Programming Interface
Access Point Name
GSM Circuit Switched Data Call
General Packet Radio Service
Global System for Mobile communications
Packet Data Protocol
Public Lands Mobile Network
Subscriber Identity Module
Table 3. Related Documentation
AT Commands Interface Guide for Firmware 7.53 (Rev 13.0)
ADL User Guide for Open AT Application Framework OS 6.53 (Rev 13.0)
7.53.0 Firmware Customer Release Note
Table 4. Hardware Compatibility
AirPrime Compatibility List
Table 5. Software Compatibility
Open AT Application Framework
Table 6. OS Release Information
Date of generation
S/W Tools Name
Compilation Tool Chain
ARM_EABI_GCC and RVDS
This section presents all corrections or improvements integrated in OS 6.53.0.
Issues are sorted by alphabetical order of Impacted Domain.
Event "ADL_GPRS_EVENT_ME_CLASS_A" is not raised to the User Application when the GPRS class is changed to class "A".
Error is returned and command handler is not invoked for any custom command when command is sent using the API adl_atCmdSendExt().
Reset when WIPSSL try to set parameter before establish connection (SSLSETOPTS )
When AT+WRIM command is executed to set bit 16 of <events_bit_field>, the Ring Indicator pulse is sent for all the unsolicited responses instead of the unsolicited response initiated by an application.
Spurious ADL_CALL_EVENT_NO_CARRIER events received on initiating a call, when AT+WBHV=2,1 has been executed and the call handler subscribed for call service has returned value equal to “ADL_CALL_NO_FORWARD_ATA”.
When an application subscribes to call service and initiates a voice call, then two ADL_CALL_EVENT_NO_CARRIER events are received on disconnecting the call from remote/receiver side.
If a command with type ADL_CMD_TYPE_PARA is subscribed by using the adl_atCmdSubscribe() API, the handler provided is also called while issuing the test command i.e. "AT+<xxxx>=?". Command handler should be called after confirming that '?' is not given after '='.
AirPrime may reset if parameter "rsphdl" for function adl_atCmdCreate() is set to NULL and the list of subscribed responses is not equal to NULL.
When the Network forces ME to change GPRS mobile class to CC, ADL_GPRS_EVENT_NW_CLASS_CC event is not received.
Incorrect CID value (5) is returned by the GPRS event handler, on trying to activate PDP context on correct CID value (1-4), when an application which subscribes to GPRS service is downloaded onto the module.
AT+WIND=0 does not disable +WIND: 9 indications if an application is running on the AirPrime.
When a GSM Data call is established using an application which has subscribed to Call Service, then on terminating the data call from remote, "ADL_CALL_EVENT_NO_CARRIER" event is received twice.
When an application is running and a concatenated command including “+CPIN2?” is issued, response is not received for commands following “+CPIN2?” in concatenated command string. In addition to this, the command class remains locked. As a result of this +CME ERROR: 515 is received for further AT commands.
AirPrime is not able to go to sleep mode after some time if AirPrime switches between sleep mode and active mode continuously when a location application is running on the AirPrime.
Subscription to Slave flow at a specific UART using ADL FCM service fails, if FCM flow is already subscribed in Master mode on the same UART.
AirPrime does not resume the data transfer when a single credit is released using adl_fcmReleaseCredits() API after consuming all the available credits.
Function adl_simEnterPIN() accepts the PIN code for the third time even if wrong PIN has already been entered twice. Ideally, ADL_RET_ERR_BAD_STATE should be received in this case.
ADL_GPRS_EVENT_ME_CLASS_A event returned if the ME has changed to class A
For Open AT Developers, please refer to the Troubleshooting Guide available in Developer Zone before contacting customer support.
Random value of "Context" is received incase API adl_atCmdSendText() is used after API adl_atCmdSendExt().
When FCM service is running with call and/or SIM services, commands ATA, ATD, ATH, AT+CGANS, AT+CGACT, AT+CGDATA, ATO and AT+CPIN cannot be filtered using the API adl_atCmdSubscribe().
On issuing a pre subscribed command from an application, through the 'adl_atCmdSendExt()' API, an OK and ERROR is received alternatively, i.e. the command is sent to the command handler and the firmware alternatively. Ideally, the command should always be sent to the command handler and OK should be received.
Error is not returned in case an attempt is made to play or listen an audio stream which is not supported by AirPrime.
Subscription to commands beginning with "ATA", "ATD" or "ATH" using the API adl_atCmdSubscribe () fails in case Call service is subscribed prior to subscribing to the commands from the application.
When Using %I64 format specifier for displaying u64/s64 variable through API adl_atSendresponse() in TARGET mode it always prints only "%I64d" instead of the value of the variable. Workaround: use %lld instead of %I64.
Sometimes handler associated with adl_errSubscribe() function is not invoked on reception of error from OS.