
AT&T: 09.93 A02.50
Verizon: 09.94 A01.02
AT&T: 09.93 A02.52
Verizon: 10.04 A01.01
AT&T: 20.03 A01.04
Verizon: 20.04 A01.00
09.93 A02.50
Verizon: 09.94 A01.02
09.93 A02.52
Verizon: 10.04 A01.01
20.03 A01.04
Verizon: 20.04 A01.00
Information note – update to note from 31-Aug-2020
TOBY-L2 / MPCI-L2 default configuration setting change in production
UBX-19058317 C1-Public
Drazen Drinic
31 August 2020
Copying, reproduction, modification or disclosure to third parties of this document or any part thereof is only permitted with the express written permission of u-blox. The information
contained herein is provided “as is” and u-blox assumes no liability for its use. No warranty, either express or implied, is given, including but not limited, with respect to the accuracy,
correctness, reliability and fitness for a particular purpose of the information. This document may be revised by u-blox at any time. For most recent documents, visit www.u-blox.com.
Copyright© u-blox AG.
1 Affected products in production
Table 1: Affected products in production
UBX-19058317 TOBY-L2 / MPCI-L2 default configuration setting change in production 1/4
C1-Public

☐ Hardware/component change
☐ Certification information
☐ Firmware/software update
2 Type
3 Description of change
In order to ensure forward compatibility with possible future Radio Access Network (RAN)
releases, all TOBY-L2 and MPCI-L2 series modules will include new default configuration
settings.
Reason: [CA-085450] A risk has been identified that in very specific scenarios, when the RAN
introduces new 3GPP release 10 or later Information Elements (IE), incompatibility issues
between the module and network are detected, which causes registration failures. Applying the
new configuration script / new default configuration settings eliminates this risk.
3.1 Default configuration setting change in production
New default configuration settings are applied in production. The new configuration of the LTE
decoder is loaded in RAM allowing tolerant handling of decoding errors related to detection of
new, unrecognized IEs that might become available in future 3GPP releases, thus eliminating
potential risk related to incompatibility issues.
3.2 Applying changes on products in the field
A software package will be made available and can be used to update units in the field with the
new configuration (for example by using FOTA).
The size of the package is approximately 1 MB. Applying the package to products in the field
does not affect module performance. Once the package is applied, the new module
configuration will stay in non-volatile-memory (NVM).
3.3 Traceability
For traceability reasons, the application version will be changed after the script has been
applied and corresponding SVN number will be changed to 10. On Verizon variants (on
TOBY-L201/MPCI-L201) the modem version for Verizon will change.
Error! Reference source not found. and Table 2 each show the version numbers before and
after. Customers can identify those units in which the new configuration settings have been
applied reading the version by means of the ATI9 command.
3.4 Additional fix for TOBY-L220-02S
In addition to the fix for [CA-085450], the following issue has been resolved:
[u-blox id 2-3430] – missing support for ELLA-W131 Wi-Fi module in TOBY-L220-02S
UBX-19058317 TOBY-L2 / MPCI-L2 default configuration setting change in production 2/4
C1-Public

AT&T: 09.93 A01.25
Verizon : 10.03 A01.00
4 Affected products in field
Table 2: Affected products in field
☞ All the product type numbers in this table are products that are no longer in production.
4.1 How to apply patch in field
☞ Before applying an update it is important to check status of the cache partition used for
FOAT/FOTA update. In rare cases this cache partition can become damaged or be removed.
This is typically caused by an improper power on/off sequence applied to the module.
4.1.1 Checking status of the cache partition:
If AT+ULSTFILE=1,"RAMDUMP" returns a value other than zero, then it is safe to do a
firmware update. This indicates that there is a cache partition that is intact and a firmware
update can be performed.
If AT+ULSTFILE=1,"RAMDUMP" returns 0 then, then it is not safe to do a firmware update.
A value of 0 indicates that there is no available memory space in the cache partition (cache
partition has been damaged/removed). In this case, contact u-blox technical support.
4.1.2 Applying update:
Customers can apply the patch on the modules in the field via FOAT (+UFWUPD AT command)
and FOTA (+UFWINSTALL AT command). For more information, see u-blox AT commands
manual [1] and u-blox cellular modules firmware update application note [5].
UBX-19058317 TOBY-L2 / MPCI-L2 default configuration setting change in production 3/4
C1-Public

Estimated first shipment date:
Documentation (e.g. release note)
All needed files (*.bin or *.zip) are provided by u-blox together with the md5 to be used in the
related AT commands.
Customers must take care to use the correct file that corresponds to the starting firmware
version in the module where the patch has to be applied. If the patch is correctly applied, then
the module will present itself with the expected destination firmware version (see Table 2).
Otherwise, if the patch is applied on a wrong starting firmware version, then the firmware
version will remain the same as before the patch. Furthermore, if the patch is correctly applied,
by issuing AT+ULSTFILE=0 customers can check the presence of a file called “config_0000”.
5 Schedule
6 Customer impact and recommended action
Because of the high severity of the issue, it is highly recommended to apply the configuration
change to all products in the field. Applying these changes does not affect modem performance
and makes no changes to interfaces.
Certification impact:
Mobile network operators:
AT&T: for customers using the TOBY-L200 and TOBY-L201 product versions, u-blox
recommends notifying AT&T of the change in the configuration (no testing is expected;
paperwork only).
Verizon: according to Verizon requirements, any host device that picks up an approved
module update will have to provide a FOTA self-compliance report showing a successful
module update from the source module version to the target module version.
Conformance:
PTCRB: for customers using the TOBY-L200 and TOBY-L201 product versions, u-blox
recommends implementing the necessary PTCRB ECO process due to the change in
the configuration (no testing is expected, paperwork only).
GCF: no impact, no actions required.
Regulatory:
FCC/ISED: no impact, no actions required.
RED: no impact, no actions required.
Other: no impact, no actions required.
7 Related documentation
[1] u-blox AT commands manual, UBX-13002752
[2] TOBY-L2 series data sheet, UBX-13004573
[3] MPCI-L2 series data sheet, UBX-13004749
[4] TOBY-L2 / MPCI-L2 series system integration manual, UBX-13004618
[5] u-blox firmware update application note, UBX-13001845
UBX-19058317 TOBY-L2 / MPCI-L2 default configuration setting change in production 4/4
C1-Public