LEA-M8F - Hardware Integration Manual
UBX-14000034 - R03
Early Production
Information
Migration
to u-blox M8 modules
Page 18 of 30
3
Migration to u-blox M8 modules
u-blox is committed to ensuring that products in the same form factor are backwards compatible over several
technology generations. Utmost care has been taken to minimize impact on function and performance and to
make u-blox M8 modules as compatible as possible with earlier modules.
Make sure that the RF path (antenna and filtering parameters) matches that of the GNSS constellations used.
To use BeiDou, review the bandwidth of the external RF components and the antenna. For information about
power consumption, see the
LEA-M8F Data Sheet
It is highly advisable that customers consider a design review with the u-blox support team to ensure the
compatibility of key functionalities.
3.1
Software migration
For an overall description of the module software operation, see the
u-blox M8 Receiver Description
including Protocol Specification
For software migration details, see the
u-blox 7 to u-blox M8 Software Migration Guide
3.2
Hardware migration LEA-6T -> LEA-M8F
This section compares the functionality when a design is migrated from a LEA-6T to a LEA-M8F. Most pins are
compatible however, the following items have changed:-
•
A single timepulse (TP2) output
•
USB interface not recommended for operational use
•
No back-up battery operation supported
•
Interface option serial/SPI selectable by D_SEL line
•
No antenna supervisor(status) function
•
Timepulse 2 replaced with output frequency signal REF_FREQ_OUT
The Timepulse output from LEA-M8F must be allowed to float during start-up and reset (see section 1.6.5)
Table 4 outlines the difference in pin connections between the two modules.
