I am trying to implement GPS code.

RE: I am trying to implement GPS code.

Tommi Kangas — Thu, 16 Apr 2026 10:37:59 GMT

Hi Gunjan Yadav ,

nRF9160 supports only GPS and QZSS. QZSS is enabled by default and it does not need to be enabled separately.

Enabled signals can be configured using nrf_modem_gnss_signal_mask_set() if needed.

BR,
Tommi

RE: I am trying to implement GPS code.

Gunjan Yadav — Thu, 16 Apr 2026 06:58:37 GMT

Hello team Tommi Kangas

Hakon

Does nrf9160 support only GPS or we can do all satellite system like use GLONASS GPS galileo etc ?Also in order to enable QZSS do we explicitly need to write some command or is it handled by

nrf_modem_gnss_start();

api internally ?

FYI Karthik

RE: I am trying to implement GPS code.

Gunjan Yadav — Tue, 14 Apr 2026 11:29:46 GMT

Hello Tommi Kangas

Could you please share the correct procedure for capturing enhanced GNSS modem traces over RTT on the nRF9160?

I have enabled the RTT modem trace backend and am monitoring RTT channel 1. After entering GNSS functional mode, I enable tracing using:

nrf_modem_at_cmd(rsp, sizeof(rsp), "AT%%XMODEMTRACE=1,5");

However, I only see AT command transaction logs and no GNSS‑specific modem traces.
Please let me know if there are any additional steps or ordering requirements to get the enhanced GNSS traces over RTT.

devzone.nordicsemi.com/.../modem_5F00_traces6.bin

Regards,

Gunjan

RE: I am trying to implement GPS code.

Tommi Kangas — Mon, 13 Apr 2026 05:36:56 GMT

Hi Karthik,

For some reason, the modem log stops almost immediately (1 second) after GNSS start. Please try to capture a longer log. Let GNSS run at least for a couple of minutes.

BR,
Tommi

RE: I am trying to implement GPS code.

Karthik — Fri, 10 Apr 2026 13:21:13 GMT

devzone.nordicsemi.com/.../GPS_5F00_COEX0_5F00_Modem_5F00_Traces.bin

Hi,

Captured modem traces with COEX0 Enable

RE: I am trying to implement GPS code.

Tommi Kangas — Fri, 10 Apr 2026 12:36:31 GMT

Hi,

I'm referring to Modem_logsOpen1.bin. It was taken before COEX0 configuration was fixed. Please take a new modem log with the current implementation which configures COEX0 correctly.

BR,
Tommi

RE: I am trying to implement GPS code.

Karthik — Fri, 10 Apr 2026 12:20:17 GMT

Hi,

If you see the above picture, we are configuring COEX0 pin before the RF is enabled. Please go through the code gps.c in the attachment.

You referred terminal_logsOpen1.log for modem logs ?

Regards,

Karthik.

RE: I am trying to implement GPS code.

Tommi Kangas — Tue, 07 Apr 2026 09:27:17 GMT

Hi,

I checked the modem log, but in that log the COEX0 pin is not configured correctly, so the LNA is not enabled.

Please make sure that the pin configuration is correct (you can use the AT command AT%XCOEX0=1,1,1565,1586 mentioned earlier) and that it's configured before the RF is enabled (latest before GNSS start). Can you capture a new modem log with the correct configuration, so I can have a look from modem point of view?

Best regards,
Tommi

RE: I am trying to implement GPS code.

Gunjan Yadav — Tue, 07 Apr 2026 09:22:04 GMT

devzone.nordicsemi.com/.../cl5gMCU_2600_hvppGPS-1.txt devzone.nordicsemi.com/.../HVPP_5F00_firmware_5F00_on_5F00_CL5G_5F00_HW_5F00_test2.txt

RE: I am trying to implement GPS code.

Hakon — Thu, 26 Mar 2026 17:31:36 GMT

[quote user="Gunjan Yadav"]We are configuring AT%XCOEX0 before AT+CFUN=0.[/quote]

As long as you send nothing before this and there is no modem activity before issuing this command it's fine.

[quote user="Gunjan Yadav"]Query: We are configuring AT+CFUN=31, is this a correct command?[/quote]

This should also be fine.

RE: I am trying to implement GPS code.

Gunjan Yadav — Wed, 25 Mar 2026 12:44:51 GMT

Hi Team,

We have tried as per your suggestion that configured COEX0 pin as below but still unable to get longitude and latitude. Can you please provide your inputs to fix this issue. We have provided our schematics and code below.

at_err = nrf_modem_at_cmd(rsp, sizeof(rsp), "%s", "AT%XCOEX0=1,1,1565,1586");

Note: We are configuring AT%XCOEX0 before AT+CFUN=0. Please see below code snippet. And we are not making AT+CFUN=1 specifically, do we need to do this? If yes, after which command?

Query: We are configuring AT+CFUN=31, is this a correct command?

#define AT_CFUN_GNSS_ONLY_CMD "AT+CFUN=31\r\n"

Code snippet:

/* Query current system mode to avoid unnecessary writes */

at_err = nrf_modem_at_cmd(rsp, sizeof(rsp), "%s", "AT%XSYSTEMMODE?\r\n");

if (at_err)

{

int type = nrf_modem_at_err_type(at_err);

int code = nrf_modem_at_err(at_err);

LOG_WRN("XSYSTEMMODE? failed (type=%d code=%d), proceeding to set", type, code);

}

memset(rsp, 0, sizeof(rsp));

at_err = nrf_modem_at_cmd(rsp, sizeof(rsp), "%s", "AT%XCOEX0=1,1,1565,1586");

if (at_err)

{

LOG_WRN("XCOEX0 set failed: type=%d code=%d ret=%d",

nrf_modem_at_err_type(at_err), nrf_modem_at_err(at_err), at_err);

}

else

{

LOG_INF("XCOEX0 configured for RF coexistence");

}

/* Go to minimum or offline functionality before changing system mode */

at_err = nrf_modem_at_cmd(rsp, sizeof(rsp), "%s", AT_CFUN_OFF_RADIO_CMD);

if (at_err)

{

int type = nrf_modem_at_err_type(at_err);

int code = nrf_modem_at_err(at_err);

LOG_WRN("CFUN=0 failed: type=%d code=%d ret=%d, trying CFUN=4", type, code, at_err);

memset(rsp, 0, sizeof(rsp));

/* Try offline mode */

at_err = nrf_modem_at_cmd(rsp, sizeof(rsp), "%s", AT_CFUN_OFFLINE_CMD);

if (at_err)

{

type = nrf_modem_at_err_type(at_err);

code = nrf_modem_at_err(at_err);

LOG_ERR("CFUN=4 failed: type=%d code=%d ret=%d", type, code, at_err);

return at_err;

}

/* Small delay to let modem settle */

k_msleep(200);

/* Set GNSS-only system mode */

memset(rsp, 0, sizeof(rsp));

at_err = nrf_modem_at_cmd(rsp, sizeof(rsp), "%s", AT_COMMAND_SYS_GNSS_ONLY_MODE);

if (at_err)

{

int type = nrf_modem_at_err_type(at_err);

int code = nrf_modem_at_err(at_err);

LOG_ERR("XSYSTEMMODE GNSS-only failed: type=%d code=%d ret=%d", type, code, at_err);

return at_err;

}

/* Enter GNSS-only functional mode */

memset(rsp, 0, sizeof(rsp));

at_err = nrf_modem_at_cmd(rsp, sizeof(rsp), "%s", AT_CFUN_GNSS_ONLY_CMD);

if (at_err)

{

int type = nrf_modem_at_err_type(at_err);

int code = nrf_modem_at_err(at_err);

LOG_ERR("CFUN GNSS-only failed: type=%d code=%d ret=%d", type, code, at_err);

return at_err;

}

Schematics:

Firmware files:

devzone.nordicsemi.com/.../gps.c

devzone.nordicsemi.com/.../gps.h

devzone.nordicsemi.com/.../at_5F00_cmd.h

Regards,

Gunjan

RE: I am trying to implement GPS code.

Hakon — Mon, 23 Mar 2026 14:07:50 GMT

Modem can be configured to enable COEX0 pin when GNSS is used with the following AT command: AT%XCOEX0=1,1,1565,1586

The command should be sent during startup, before enabling RF (for example AT+CFUN=1).

RE: I am trying to implement GPS code.

Gunjan Yadav — Wed, 18 Mar 2026 11:03:27 GMT

Hi Hakon Can you please suggest how to explicitly enable coex pin ? We have made some changes in the board and now LNA is connected to COEX0 but when I am trying to run the apis as above it is not being taken care internally and LNA may not be getting powered up. Can you please suggest how to do this now ?

RE: I am trying to implement GPS code.

Hakon — Tue, 10 Mar 2026 08:31:52 GMT

[quote user="Gunjan Yadav"]Can you please confirn how this is being taken care internally ? Is it enabled by COEX or MAGPIO and why it's not needed to enable COEX / MAGPIO explicitly for nrf9160DK board?[/quote]

When building for the nRF9160 DK, the Modem antenna library (CONFIG_MODEM_ANTENNA) gets enabled by default. The Modem antenna library configures COEX0 correctly for the DK based on whether CONFIG_MODEM_ANTENNA_GNSS_ONBOARD or CONFIG_MODEM_ANTENNA_GNSS_EXTERNAL is enabled. LNA is enabled when using the onboard antenna, and disabled when using an external antenna.

RE: I am trying to implement GPS code.

Gunjan Yadav — Fri, 27 Feb 2026 11:23:40 GMT

Hi Hakon I have tried implementing the GPS functionality on nrf9160DK board on this it is working fine and I am able to get the coordinates. but I have not written any code line explicitly to enable the LNA in it.

Can you please confirn how this is being taken care internally ? Is it enabled by COEX or MAGPIO and why it's not needed to enable COEX / MAGPIO explicitly for nrf9160DK board?

RE: I am trying to implement GPS code.

Gunjan Yadav — Fri, 27 Feb 2026 09:50:41 GMT

Hi Hakon As shown in the schematic all COEX and MAGPIO are NC only.

And it's correct that we are trying to enable LNA via GPS_EN GPIO pin and I am already getting the volatge around D1(2.489 at cathode ) , D2 (2.673 at cathode ) which further goes to c1(2.48), c2(2.49) and c3(2.67), c4(2.67) which are sufficient to power up LNA.

Also just for clarification we have separate antennas for LTE and GPS. And here all I am doing is in GNSS mode only.

RE: I am trying to implement GPS code.

Hakon — Wed, 25 Feb 2026 09:17:42 GMT

Can you confirm whether you are using COEX or not?

Modem team; All COEX and MAGPIO pins seem to be NC, so I don’t think the %XCOEX0 configuration matters. I checked the code snippet and it looks like the LNA should get enabled using the GPIO pin (as long as the pin configuration in DT is correct).

From SW point of view, I can’t think of anything else that would be missing.

RE: I am trying to implement GPS code.

Gunjan Yadav — Tue, 24 Feb 2026 06:55:47 GMT

This is an internal GPS setup and has external on-board antenna attached to it.

I can see voltages around D1(2.489 at cathode ) , D2 (2.673 at cathode ) which further goes to c1(2.48), c2(2.49) and c3(2.67), c4(2.67) which are sufficient to power up LNA.

Is there anything else I am missing in the code ?

Also coex is used for coexistence of LTE along with GNSS. Here I am using GNSS mode only in the code.

Hakon

RE: I am trying to implement GPS code.

Hakon — Thu, 19 Feb 2026 09:08:41 GMT

You should check if the LNA gets properly enabled. Since you are using a regular GPIO pin instead of COEX0, there can potentially be issues.

GNSS gets started and is receiving PVT notifications once a second, so it does not look like a GNSS API issue.

RE: I am trying to implement GPS code.

Hakon — Wed, 18 Feb 2026 09:01:12 GMT

Thanks I have forwarded this to modem team.

RE: I am trying to implement GPS code.

Gunjan Yadav — Wed, 18 Feb 2026 08:50:35 GMT

devzone.nordicsemi.com/.../Modem_5F00_logsOpen1.bin

Hi Hakon please find the above logs in .bin format. These were taken under open sky and external antenna connected to the board. Also find terminal logs for your reference.

devzone.nordicsemi.com/.../terminal_5F00_logsOpen1.log

RE: I am trying to implement GPS code.

Hakon — Wed, 18 Feb 2026 08:43:48 GMT

Please follow these instructions on how to capture modem trace, and upload the trace file in .bin or .trace format.

RE: I am trying to implement GPS code.

Gunjan Yadav — Wed, 18 Feb 2026 07:25:06 GMT

MAGPIO and COEX are NC so error coming at last 2 commands shouldn't be an issue.

RE: I am trying to implement GPS code.

Gunjan Yadav — Wed, 18 Feb 2026 07:24:03 GMT

Hi Hakon yes sure ! please find the modem logs as below

1 0.000000 AT 30 Sent AT Command: AT%XMODEMTRACE=1,2
2 0.000915 AT 16 Rcvd AT Command: OK
3 0.001434 AT 34 Sent AT Command: AT%XSYSTEMMODE=0,1,0,0
4 0.003235 AT 16 Rcvd AT Command: OK
5 0.003784 AT 19 Rcvd AT Command: ERROR
6 0.023620 AT 23 Sent AT Command: AT+CFUN=0
7 0.032196 AT 16 Rcvd AT Command: OK
8 2.051971 AT 28 Sent AT Command: AT%XBANDLOCK=0
9 2.052032 AT 16 Rcvd AT Command: OK
10 2.062225 AT 24 Sent AT Command: AT+CEREG=1
11 2.062256 AT 16 Rcvd AT Command: OK
12 2.072235 AT 23 Sent AT Command: AT+CMEE=1
13 2.072266 AT 16 Rcvd AT Command: OK
14 2.082275 AT 21 Sent AT Command: AT+CGMI
15 2.082306 AT 42 Rcvd AT Command: Nordic Semiconductor ASA OK
16 2.100830 AT 23 Sent AT Command: AT+COPS=0
17 2.101013 AT 16 Rcvd AT Command: OK
18 2.120636 AT 30 Sent AT Command: AT%XMODEMTRACE=1,2
19 2.121551 AT 16 Rcvd AT Command: OK
20 16.186554 AT 29 Sent AT Command: AT%XSYSTEMMODE?
21 16.186615 AT 39 Rcvd AT Command: %XSYSTEMMODE: 0,1,0,0 OK
22 16.187103 AT 23 Sent AT Command: AT+CFUN=0
23 16.195740 AT 16 Rcvd AT Command: OK
24 16.402313 AT 36 Sent AT Command: AT%XSYSTEMMODE=0,0,1,0
25 16.403259 AT 16 Rcvd AT Command: OK
26 16.403656 AT 24 Sent AT Command: AT+CFUN=31
27 16.409759 AT 16 Rcvd AT Command: OK
28 16.410248 AT 34 Sent AT Command: AT%XMAGPIO=1,1,1,7,0,0
29 16.410278 AT 19 Rcvd AT Command: ERROR
30 16.410950 AT 27 Sent AT Command: AT%XCOEX0=1,1,0
31 16.410980 AT 19 Rcvd AT Command: ERROR

Corresponding to this modem logs below is the terminal log:

# SEGGER J-Link RTT Viewer V8.82 Terminal Log File
# Compiled: 11:50:24 on Oct 29 2025
# Logging started @ 17 Feb 2026 17:55:08
00> *** Booting nRF Connect SDK v3.1.0-6c6e5b32496e ***
00> *** Using Zephyr OS v4.1.99-1612683d4010 ***
00> [00:00:10.641,510] <inf> modem_trace_backend: Modem_trace RTT backend channel 1
00> [00:00:10.641,540] <inf> nrf_modem_lib_trace: Trace thread ready
00> [00:00:10.649,017] <inf> nrf_modem_lib_trace: Trace level override: 2
00> LED1RED: ON
00> LED1RED: OFF
00> LED2GREEN: ON
00> LED2GREEN: OFF
00> [00:00:26.048,187] <inf> gnss_app: GPS powered ON
00> [00:00:27.057,891] <inf> gnss_app: Modem set to GNSS-only mode
00> [00:00:27.058,410] <wrn> gnss_app: XMAGPIO set failed: type=1 code=0 ret=65536
00> [00:00:27.059,112] <wrn> gnss_app: XCOEX0 set failed: type=1 code=0 ret=65536
00> [00:00:27.079,132] <inf> gnss_app: GNSS event: 4
00> [00:00:27.079,162] <inf> gnss_app: GNSS started.
00> [00:00:27.101,989] <inf> gnss_app: GNSS PVT struct size=232
00> [00:00:27.101,989] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:27.102,020] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:28.103,057] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:28.103,118] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:29.103,240] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:29.103,240] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:30.103,271] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:30.103,302] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:31.103,302] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:31.103,332] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:32.103,424] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:32.103,454] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:33.103,454] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:33.103,485] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:34.103,485] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:34.103,546] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:35.103,454] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:35.103,485] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:36.103,515] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:36.103,546] <inf> gnss_app: PVT: searching... sv_view=1 acc=0.0(m) flags=0x00000000
00> [00:00:37.103,912] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:37.103,942] <inf> gnss_app: PVT: searching... sv_view=1 acc=0.0(m) flags=0x00000000
00> [00:00:38.104,064] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:38.104,095] <inf> gnss_app: PVT: searching... sv_view=1 acc=0.0(m) flags=0x00000000
00> [00:00:39.104,003] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:39.104,003] <inf> gnss_app: PVT: searching... sv_view=1 acc=0.0(m) flags=0x00000000
00> [00:00:40.103,210] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:40.103,240] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:41.103,210] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:41.103,240] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:42.103,698] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:42.103,729] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:43.103,790] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:43.103,790] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:44.103,576] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:44.103,607] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:45.103,820] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:45.103,820] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:46.103,851] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:46.103,881] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:47.103,454] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:47.103,454] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:48.103,485] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:48.103,515] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:49.103,973] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:49.103,973] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:50.104,003] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:50.104,034] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:51.103,363] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:51.103,363] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:52.103,637] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:52.103,668] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:53.104,095] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:53.104,125] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:54.104,217] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:54.104,248] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:55.103,729] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:55.103,759] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:56.103,790] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:56.103,820] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:57.104,248] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:57.104,278] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:58.104,156] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:58.104,187] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:00:59.103,942] <inf> gnss_app: PVT flags=0x00000000
00> [00:00:59.103,973] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:00.103,912] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:00.103,973] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:01.103,942] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:01.103,973] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:02.104,003] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:02.104,034] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:03.104,461] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:03.104,492] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:04.104,522] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:04.104,553] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:05.103,881] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:05.103,881] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:06.104,156] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:06.104,187] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:07.104,248] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:07.104,248] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:08.104,736] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:08.104,766] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:09.104,705] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:09.104,705] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:10.104,278] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:10.104,339] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:11.104,339] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:11.104,339] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:12.104,675] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:12.104,705] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:13.104,858] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:13.104,888] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:14.104,888] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:14.104,919] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:15.104,522] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:15.104,553] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:16.104,522] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:16.104,553] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:17.105,010] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:17.105,010] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:18.105,041] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:18.105,072] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:19.104,949] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:19.104,949] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:20.105,102] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:20.105,163] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:21.104,705] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:21.104,705] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:22.105,255] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:22.105,285] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:23.105,224] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:23.105,255] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:24.104,827] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:24.104,858] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:25.104,827] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:25.104,858] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:26.105,194] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:26.105,224] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:27.105,377] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:27.105,377] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:28.105,407] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:28.105,438] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:29.105,438] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:29.105,438] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:30.105,468] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:30.105,499] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:31.105,377] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:31.105,377] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:32.105,102] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:32.105,133] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:33.105,133] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:33.105,163] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:34.105,163] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:34.105,194] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:35.105,194] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:35.105,224] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:36.105,255] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:36.105,285] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:37.105,712] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:37.105,743] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:38.105,743] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:38.105,804] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:39.105,804] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:39.105,804] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:40.105,834] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:40.105,865] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:41.105,834] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:41.105,865] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:42.105,865] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:42.105,926] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:43.105,895] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:43.105,926] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:44.105,834] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:44.105,865] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:45.106,048] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:45.106,079] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000
00> [00:01:46.106,018] <inf> gnss_app: PVT flags=0x00000000
00> [00:01:46.106,048] <inf> gnss_app: PVT: searching... sv_view=0 acc=0.0(m) flags=0x00000000

# Logging stopped @ 17 Feb 2026 17:59:55

RE: I am trying to implement GPS code.

Hakon — Mon, 16 Feb 2026 08:32:35 GMT

Can you also provide modem trace?