Integration Manual
Table Of Contents
- Document information
- Contents
- 1 System description
- 1.1 Overview
- 1.2 Architecture
- 1.3 Pin-out
- 1.4 Operating modes
- 1.5 Supply interfaces
- 1.5.1 Module supply input (VCC)
- 1.5.1.1 VCC supply requirements
- 1.5.1.2 VCC current consumption in LTE connected mode
- 1.5.1.3 VCC consumption in deep-sleep mode (low power mode and PSM enabled)
- 1.5.1.4 VCC current consumption in low power idle mode (low power mode enabled)
- 1.5.1.5 VCC current consumption in active mode (low power mode and PSM disabled)
- 1.5.2 Generic digital interfaces supply output (V_INT)
- 1.5.1 Module supply input (VCC)
- 1.6 System function interfaces
- 1.7 Antenna interfaces
- 1.8 SIM interface
- 1.9 Data communication interfaces
- 1.10 Audio
- 1.11 General purpose input / output (GPIO)
- 1.12 Reserved pin (RSVD)
- 2 Design-in
- 2.1 Overview
- 2.2 Supply interfaces
- 2.2.1 Module supply (VCC)
- 2.2.1.1 General guidelines for VCC supply circuit selection and design
- 2.2.1.2 Guidelines for VCC supply circuit design using a switching regulator
- 2.2.1.3 Guidelines for VCC supply circuit design using low drop-out linear regulator
- 2.2.1.4 Guidelines for VCC supply circuit design using a rechargeable battery
- 2.2.1.5 Guidelines for VCC supply circuit design using a primary battery
- 2.2.1.6 Guidelines for external battery charging circuit
- 2.2.1.7 Guidelines for external charging and power path management circuit
- 2.2.1.8 Guidelines for removing VCC supply
- 2.2.1.9 Additional guidelines for VCC supply circuit design
- 2.2.1.10 Guidelines for VCC supply layout design
- 2.2.1.11 Guidelines for grounding layout design
- 2.2.2 Generic digital interfaces supply output (V_INT)
- 2.2.1 Module supply (VCC)
- 2.3 System functions interfaces
- 2.4 Antenna interfaces
- 2.5 SIM interface
- 2.6 Data communication interfaces
- 2.6.1 UART interfaces
- 2.6.1.1 Guidelines for UART circuit design
- Providing 1 UART with the full RS-232 functionality (using the complete V.24 link)
- Providing 1 UART with the TXD, RXD, RTS, CTS, DTR and RI lines only
- Providing 1 UART with the TXD, RXD, RTS and CTS lines only
- Providing 2 UARTs with the TXD, RXD, RTS and CTS lines only
- Providing 1 UART with the TXD and RXD lines only
- Providing 2 UARTs with the TXD and RXD lines only
- Additional considerations
- 2.6.1.2 Guidelines for UART layout design
- 2.6.1.1 Guidelines for UART circuit design
- 2.6.2 USB interface
- 2.6.3 SPI interfaces
- 2.6.4 SDIO interface
- 2.6.5 DDC (I2C) interface
- 2.6.1 UART interfaces
- 2.7 Audio
- 2.8 General purpose input / output (GPIO)
- 2.9 Reserved pin (RSVD)
- 2.10 Module placement
- 2.11 Module footprint and paste mask
- 2.12 Schematic for SARA-R5 series module integration
- 2.13 Design-in checklist
- 3 Handling and soldering
- 4 Approvals
- 5 Product testing
- Appendix
- A Migration between SARA modules
- B Glossary
- Related documents
- Revision history
- Contact
SARA-R5 series - System integration manual
UBX-19041356 - R03 Product testing Page 103 of 123
Confidential
5.2 Test parameters for OEM manufacturers
Because of the testing done by u-blox (with 100% coverage), an OEM manufacturer does not need to
repeat the firmware tests or measurements of the module RF performance or tests over analog and
digital interfaces in their production test.
However, an OEM manufacturer should focus on:
Module assembly on the device; it should be verified that:
o The soldering and handling process did not damage the module components
o All module pins are well soldered on the device board
o There are no short circuits between pins
Component assembly on the device; it should be verified that:
o Communication with the host controller can be established
o The interfaces between the module and device are working
o Overall RF functional test of the device including the antenna/s
Dedicated tests can be implemented to check the device. For example, the measurement of the
module current consumption when set in a specified status can detect a short circuit if compared with
a “Golden Device” result.
In addition, module AT commands can be used to perform functional tests on the digital interfaces
(communication with the host controller, check the SIM interface, GPIOs, etc.) or to perform RF
functional tests (see the following section 5.2.2 for details).
5.2.1 “Go / No go” tests for integrated devices
A “Go / No go” test is typically used to compare the signal quality with a “Golden Device”.
The cellular RF functionality should be checked with the DUT (Device Under Test) placed in a location
with excellent cellular network coverage and known cellular signal quality. This test should be
performed after the data connection has been established. +CSQ is the typical AT command used to
check signal quality in term of RSSI, comparing the DUT with a “Golden Device”. See the SARA-R5
series AT commands manual [2] for detail usage of the AT command.
☞ These kinds of test may be useful as a “go / no go” test but not for cellular RF performance
measurements neither for certifications purpose.
This test is suitable also to check the communications with the host controller, the SIM card and the
power supply. It is also a mean to verify if components at the cellular RF interface are well soldered.
The GNSS RF functionality should be checked with the device under test (DUT) placed in an outdoor
position, with excellent sky view (HDOP < 3.0). Let the receiver acquire satellites and compare the
signal strength with a “Golden Device”.
☞ As the electro-magnetic field of a redistribution antenna is not homogenous, indoor tests are in
most cases not reliable to check the GNSS RF functionality. These kind of tests may be useful as
a ‘go/no go’ test but not for GNSS sensitivity measurements.