OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/gnss/Kconfig.u_blox_m8

31 lines
843 B
Plaintext
Raw Normal View History

ADD: GNSS Driver for U-BLOX M10 & Support for UBX Messages MODEM_UBX: Adds Support for UBX Messages in Modem Subsystem. GNSS API Supported: get_supported_systems, set_fix_rate, get_fix_rate, set_enabled_systems, get_enabled_systems, set_navigation_mode, get_navigation_mode. Boards Tested: MIMXRT1062_FMURT6, VMU_RT1170. Note: Partial support for U-BLOX Messages is provided as of now. Signed-off-by: Sumit Batra <sumit.batra@nxp.com> Signed-off-by: Mayank Mahajan <mayankmahajan.x@nxp.com>
2024-01-24 19:22:22 +08:00
# Copyright 2024 NXP
# SPDX-License-Identifier: Apache-2.0
gnss: rename u-blox M10 driver to M8 The driver in tree is for u-blox M8 devices, not M10. The M10 series devices (from Protocol Version 23.01) use a different, non backwards compatible interface for configuring the modem behaviour. Of the two boards tested in the original PR, the "VMU RT1170" is explicitly listed as having a u-blox NEO-M8N modem, while I have been unable to find any information online about the "FMURT6" board. Leaving the naming as-is will cause problems when M10 drivers are contributed. Signed-off-by: Jordan Yates <jordan@embeint.com>
2024-07-29 15:08:39 +08:00
config GNSS_U_BLOX_M8
bool "U-BLOX M8 GNSS Module"
ADD: GNSS Driver for U-BLOX M10 & Support for UBX Messages MODEM_UBX: Adds Support for UBX Messages in Modem Subsystem. GNSS API Supported: get_supported_systems, set_fix_rate, get_fix_rate, set_enabled_systems, get_enabled_systems, set_navigation_mode, get_navigation_mode. Boards Tested: MIMXRT1062_FMURT6, VMU_RT1170. Note: Partial support for U-BLOX Messages is provided as of now. Signed-off-by: Sumit Batra <sumit.batra@nxp.com> Signed-off-by: Mayank Mahajan <mayankmahajan.x@nxp.com>
2024-01-24 19:22:22 +08:00
default y
depends on GNSS
gnss: rename u-blox M10 driver to M8 The driver in tree is for u-blox M8 devices, not M10. The M10 series devices (from Protocol Version 23.01) use a different, non backwards compatible interface for configuring the modem behaviour. Of the two boards tested in the original PR, the "VMU RT1170" is explicitly listed as having a u-blox NEO-M8N modem, while I have been unable to find any information online about the "FMURT6" board. Leaving the naming as-is will cause problems when M10 drivers are contributed. Signed-off-by: Jordan Yates <jordan@embeint.com>
2024-07-29 15:08:39 +08:00
depends on DT_HAS_U_BLOX_M8_ENABLED
drivers: gnss: update drivers to select reference frame Update in-tree device drivers to depend on the reference frame datums they support. Signed-off-by: Bjarki Arge Andreasen <bjarki.andreasen@nordicsemi.no>
2024-07-28 20:42:45 +08:00
depends on GNSS_REFERENCE_FRAME_WGS84
ADD: GNSS Driver for U-BLOX M10 & Support for UBX Messages MODEM_UBX: Adds Support for UBX Messages in Modem Subsystem. GNSS API Supported: get_supported_systems, set_fix_rate, get_fix_rate, set_enabled_systems, get_enabled_systems, set_navigation_mode, get_navigation_mode. Boards Tested: MIMXRT1062_FMURT6, VMU_RT1170. Note: Partial support for U-BLOX Messages is provided as of now. Signed-off-by: Sumit Batra <sumit.batra@nxp.com> Signed-off-by: Mayank Mahajan <mayankmahajan.x@nxp.com>
2024-01-24 19:22:22 +08:00
select MODEM_MODULES
select MODEM_BACKEND_UART
select MODEM_CHAT
select MODEM_UBX
select GNSS_PARSE
select GNSS_NMEA0183
select GNSS_NMEA0183_MATCH
select GNSS_U_BLOX_PROTOCOL
select UART_USE_RUNTIME_CONFIGURE
help
gnss: rename u-blox M10 driver to M8 The driver in tree is for u-blox M8 devices, not M10. The M10 series devices (from Protocol Version 23.01) use a different, non backwards compatible interface for configuring the modem behaviour. Of the two boards tested in the original PR, the "VMU RT1170" is explicitly listed as having a u-blox NEO-M8N modem, while I have been unable to find any information online about the "FMURT6" board. Leaving the naming as-is will cause problems when M10 drivers are contributed. Signed-off-by: Jordan Yates <jordan@embeint.com>
2024-07-29 15:08:39 +08:00
Enable U-BLOX M8 GNSS modem driver.
ADD: GNSS Driver for U-BLOX M10 & Support for UBX Messages MODEM_UBX: Adds Support for UBX Messages in Modem Subsystem. GNSS API Supported: get_supported_systems, set_fix_rate, get_fix_rate, set_enabled_systems, get_enabled_systems, set_navigation_mode, get_navigation_mode. Boards Tested: MIMXRT1062_FMURT6, VMU_RT1170. Note: Partial support for U-BLOX Messages is provided as of now. Signed-off-by: Sumit Batra <sumit.batra@nxp.com> Signed-off-by: Mayank Mahajan <mayankmahajan.x@nxp.com>
2024-01-24 19:22:22 +08:00
gnss: rename u-blox M10 driver to M8 The driver in tree is for u-blox M8 devices, not M10. The M10 series devices (from Protocol Version 23.01) use a different, non backwards compatible interface for configuring the modem behaviour. Of the two boards tested in the original PR, the "VMU RT1170" is explicitly listed as having a u-blox NEO-M8N modem, while I have been unable to find any information online about the "FMURT6" board. Leaving the naming as-is will cause problems when M10 drivers are contributed. Signed-off-by: Jordan Yates <jordan@embeint.com>
2024-07-29 15:08:39 +08:00
config GNSS_U_BLOX_M8_SATELLITES_COUNT
ADD: GNSS Driver for U-BLOX M10 & Support for UBX Messages MODEM_UBX: Adds Support for UBX Messages in Modem Subsystem. GNSS API Supported: get_supported_systems, set_fix_rate, get_fix_rate, set_enabled_systems, get_enabled_systems, set_navigation_mode, get_navigation_mode. Boards Tested: MIMXRT1062_FMURT6, VMU_RT1170. Note: Partial support for U-BLOX Messages is provided as of now. Signed-off-by: Sumit Batra <sumit.batra@nxp.com> Signed-off-by: Mayank Mahajan <mayankmahajan.x@nxp.com>
2024-01-24 19:22:22 +08:00
int "Maximum satellite count"
depends on GNSS_SATELLITES
default 24
help
Maximum number of satellite that the driver that can be decoded from
the GNSS device. This does not affect the number of devices that the
device is actually tracking, just how many of those can be reported
in the satellites callback.