Thing Plus not connecting to NRFCloud

occurrentarts

Hi there!

I have a Thing Plus with a Hologram Sim card.

I’m following this guide:
https://learn.sparkfun.com/tutorials/nrf9160-thing-plus-hookup-guide
I have the AGPS sample loaded on my device and LTE Link Monitor connected.
I have my Sim set up through Hologram and it shows a blue dot with the word “Connected” in their devices list.

Here’s my log:
*** Booting Zephyr OS build v2.4.0-ncs2 ***I: A-GPS sample has startedI: Connecting to LTE network. This may take minutes.I: PSM mode requested+CEREG: 2,"0982","01AFD011",7,0,0,"11100000","11100000"+CSCON: 1+CEREG: 5,"0982","01AFD011",7,,,"00001000","00011111"AT+COPS=3,2I: Connected to LTE networkD: COEX0 set: AT%XCOEX0=1,1,1565,1586D: GPS socket created, fd: 1232491587I: CLOUD_EVT_CONNECTINGOKAT+COPS?+COPS: 0,2,"310410",7OKAT%XCBAND%XCBAND: 12OKAT+CGDCONT?+CGDCONT: 0,"IP","hologram","100.65.228.153",0,0OKAT+CGACT?+CGACT: 0,1OKI: CLOUD_EVT_CONNECTING+CSCON: 0
So it appears to be connected to LTE but hangs on CLOUD_EVT_CONNECTING and never get’s through to sending the GPS signal.

When I visit nrfcloud.com and try and add my thing plus as an LTE device it gives me the following error:
There was an error adding your device: No device found for this id. The device has not yet been provisioned. Troubleshoot nRF Code 40412
I’ve confirmed my IMEI and have tried connecting the LTE device through multiple browsers to eliminate caching issues.

I came across this thread where another user experiences a similar issue:
https://community.jaredwolff.com/d/26-unable-to-connect-to-the-cloud
And followed the command protocol.
Entering
AT%XSYSTEMMODE?
returns
%XSYSTEMMODE: 1,0,1,0
as it should.

Do I need to issue a new certificate to resolve the provisioning issue?
Are there any other ways I can re-provision my device to get it to connect correctly to NRFCloud?

Thanks for considering my issue!

jaredwolff

Hey occurrentarts

I believe Sparkfun guys are provisioning their devices (if they are provisioning them) with the prefix thing-plus. I know for the original version your ID should be something like feather-<IMEI> So make sure your full ID is thing-plus-<YOUR IMEI> You can get your IMEI by running: AT+CGSN=1?

Also, you can check if your device has certificates by running the AT%CMNG=1 command. You’ll want to see if there are any entries for %CMNG: 16842753,0

If you don’t have one on your device, I can provision another one for you. I’ll just need to know the IMEI (I can get that from you over email, don’t share it here)

occurrentarts

Hey Jared, thanks so much for your response.

I entered AT+CGSN=1? and confirmed the value I was using for the IMEI is correct.
I’ve been trying to connect to NRFCloud with:
thing-plus-IMEI_VAL
with pin 7753

I also ran the AT%CMNG=1 command. The following is was the response:
OKAT%CMNG=1%CMNG: 0,6,"0606060606060606060606060606060606060606060606060606060606060606"%CMNG: 42,0,"0000000000000000000000000000000000000000000000000000000000000000"OK

So it seems there are two values there but they are quite different from the 16842753 value you suggest.
Happy to shoot you an email with my IMEI value if that’s the best way to resolve the issue.

Thanks again!

jaredwolff

occurrentarts yea send me your IMEI hello@jaredwolff.com

jaredwolff

@occurrentarts as mentioned in my email, once you have the certificate downloaded you can load them using this procedure:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrf91_dk_gsg%2FUG%2Fnrf91_DK_gsg%2Fupdating_certificates.html

Let me know if you run into any other snags.

occurrentarts

Hey Jared,

I was able to load the certificate and add the device to nrfcloud.com with these values.
Thanks so much for the help with that.

Would you say the prefix and pin you shared will apply to all future thing-plus devices we purchase as well?
In order to get the agps sample to connect I also had to modify the agps prj.conf file to adjust to this new prefix.

Anyways, appreciate the help!

jaredwolff

occurrentarts

occurrentarts Would you say the prefix and pin you shared will apply to all future thing-plus devices we purchase as well?
In order to get the agps sample to connect I also had to modify the agps prj.conf file to adjust to this new prefix.

It should match the documentation that Sparkfun has provided. I’ll double check with them to make sure they’re still provisioning their devices properly.

occurrentarts

Ok sure, so for future devices I’ll continue to use the “thing-plus-” prefix vs this new “feather-” prefix.
While I have the agps example connecting to nrfcloud.com it looks like the GPS of my device has some trouble connecting. It looks like the same issue as this one:

https://community.jaredwolff.com/d/4-nrf-cloud-agps-sample-no-gps-data/9

Here’s my log:
SPM: prepare to jump to Non-Secure image.*** Booting Zephyr OS build v2.4.0-ncs2 ***I: A-GPS sample has startedI: Connecting to LTE network. This may take minutes.I: PSM mode requested+CEREG: 2,"091E","01C4AB11",7,0,0,"11100000","11100000"+CSCON: 1+CEREG: 5,"091E","01C4AB11",7,,,"00001000","00011111"AT+COPS=3,2I: Connected to LTE networkD: COEX0 set: AT%XCOEX0=1,1,1565,1586D: GPS socket created, fd: 1232491587I: CLOUD_EVT_CONNECTINGOKAT+COPS?+COPS: 0,2,"310410",7OKAT%XCBAND%XCBAND: 12OKAT+CGDCONT?+CGDCONT: 0,"IP","hologram","100.65.228.153",0,0OKAT+CGACT?+CGACT: 0,1OKI: CLOUD_EVT_CONNECTEDI: CLOUD_EVT_PAIR_DONEE: Failed to save session state: -2I: CLOUD_EVT_READYI: Service info sent to cloudD: GPS mode is enabledD: GPS operationalI: Periodic GPS search started with interval 240 s, timeout 120 sI: GPS_EVT_SEARCH_STARTEDD: A-GPS data update neededI: GPS_EVT_AGPS_DATA_NEEDEDD: Created A-GPS request: {"appId":"AGPS","messageType":"DATA","data":{"mcc":310,"mnc":410,"tac":2334,"eci":29666065,"phycid":0,"types":[1,2,3,4,7,8,9]}}D: A-GPS request sentI: CLOUD_EVT_DATA_RECEIVEDD: Receievd AGPS data. Schema version: 1, length: 1037D: Parsed_len: 35D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 66D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 97D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 128D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Waiting for time window to operateI: GPS_EVT_OPERATION_BLOCKEDD: Sent A-GPS data to modem, type: 3D: Parsed_len: 159D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 190D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 221D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 252D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 283D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 314D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 345D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 376D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 407D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 438D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 469D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 500D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 531D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 562D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 593D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 624D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 655D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 686D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 717D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 748D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 779D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 810D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 841D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 872D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 903D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 934D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 965D: A-GPS type: NRF_CLOUD_AGPS_ALMANACD: Sent A-GPS data to modem, type: 3D: Parsed_len: 984D: TOWs copied, bitmask: 0x00000000D: SW TOW mask is zero, not copying TOW arrayD: A-GPS type: NRF_CLOUD_AGPS_GPS_SYSTEM_CLOCKD: Sent A-GPS data to modem, type: 7D: Parsed_len: 1002D: A-GPS type: NRF_CLOUD_AGPS_LOCATIOND: Sent A-GPS data to modem, type: 8D: Parsed_len: 1019D: A-GPS type: NRF_CLOUD_AGPS_UTC_PARAMETERSD: Sent A-GPS data to modem, type: 1D: Parsed_len: 1030D: A-GPS type: NRF_CLOUD_AGPS_KLOBUCHAR_CORRECTIOND: Sent A-GPS data to modem, type: 4D: Parsed_len: 1037D: A-GPS type: NRF_CLOUD_AGPS_INTEGRITYD: Sent A-GPS data to modem, type: 9I: A-GPS data successfully processedI: CLOUD_EVT_DATA_RECEIVEDD: Receievd AGPS data. Schema version: 1, length: 1864D: Parsed_len: 66D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 128D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 190D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 252D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 314D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 376D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 438D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 500D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 562D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 624D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 686D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 748D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 810D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 872D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 934D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 996D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1058D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1120D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1182D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1244D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1306D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1368D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1430D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1492D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1554D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1616D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1678D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1740D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1802D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2D: Parsed_len: 1864D: A-GPS type: NRF_CLOUD_AGPS_EPHEMERIDESD: Sent A-GPS data to modem, type: 2I: A-GPS data successfully processed+CSCON: 0D: GPS has time window to operateI: GPS_EVT_OPERATION_UNBLOCKEDD: Tracking: 0 Using: 0 Unhealthy: 0D: Seconds since last fix 15D: Tracking: 0 Using: 0 Unhealthy: 0D: Seconds since last fix 16D: Tracking: 0 Using: 0 Unhealthy: 0

I’m not sure the binary you share with Tonyweil will work since the prefix changed for me, plus I need to be able to modify the code for my own purposes. And seems like the docs you link to seems to be broken:
https://docs.jaredwolff.com/nrf9160-agps-sample.html

I have the device plugged directly into my machine via usb 3.0 and the antenna is sitting in the window. Curious if you have any insight into what I might be able to tweak to get the GPS to connect.

jaredwolff

occurrentarts what kind of antenna is it? (Send me a link)

As for the sample itself, it’s likely that your AT_COEX0 settings are not set properly. The AGPS sample is old though, did you mean GPS? (That’s the only sample in NFED at the moment)

In the GPS sample you’ll need to add a section underneath this one:

#ifdef CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS
#define AT_COEX0 		"AT%XCOEX0=1,1,1565,1586"
#endif /* CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS */

Add:

#ifdef CONFIG_BOARD_SPARKFUN_THING_PLUS_NRF9160NS
#define AT_COEX0 		"AT%XCOEX0=1,1,1565,1586"
#endif /* CONFIG_BOARD_SPARKFUN_THING_PLUS_NRF9160NS */

Alternatively, if you’re using the modem library you can set this in your prj.conf

# COEX0 is used to enable the GPS LNA, but it has to be configured to do so.
CONFIG_NRF9160_GPS_SET_COEX0=y
CONFIG_NRF9160_GPS_COEX0_STRING="AT%XCOEX0=1,1,1565,1586"

This configuration variable essentially turns on the auto switching for GPS. When the modem releases to the GPS it switches on the GPS power. When it needs to use LTE, it switches it off. Otherwise if it was left on, you’d get a lot of interference/noise on the GPS side due to LTE transmissions.

Hope that helps!

occurrentarts

Hey Jared,

It’s this antenna:
https://www.sparkfun.com/products/15053

I’ve tried to run the gps sample with the changes you suggest. I can build, but with every configuration I get an error when I try and flash it to the device:
Error: open build/zephyr/app_update.bin: The system cannot find the file specified.

I do notice the gps sample did not have a section that looks exactly the same as the one you shared:
#ifdef CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS #define AT_COEX0 "AT%XCOEX0=1,1,1565,1586" #endif /* CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS */

But rather shows:
#ifdef CONFIG_BOARD_NRF9160DK_NRF9160NS #define AT_MAGPIO "AT\%XMAGPIO=1,0,0,1,1,1574,1577" #ifdef CONFIG_GPS_SAMPLE_ANTENNA_ONBOARD #define AT_COEX0 "AT\%XCOEX0=1,1,1565,1586" #elif CONFIG_GPS_SAMPLE_ANTENNA_EXTERNAL #define AT_COEX0 "AT\%XCOEX0" #endif #endif /* CONFIG_BOARD_NRF9160DK_NRF9160NS */
As well as an ifdef for the Thingy91.
I did try adding your suggested code beneath the above and it does not flash to the device.

You mention the GPS sample is the most up-to-date vs agps, the hookup guide specifically references the agps sample. Could the hookup guide be incorrect about other things? Could my samples be out of date? I am using sdk 1.4.1 as suggested by the Sparkfun Hookup Guide:
http://developer.nordicsemi.com/.pc-tools/toolchain/ncs-toolchain-v1.4.1-20201215-7ecf886-minimal.zip
and the following was added to my west.yml for nrf:
name: nfed repo-path: nrf9160-feather-examples-and-drivers revision: v1.4.x path: nfed remote: circuitdojo

I did see this similar issue:
https://community.jaredwolff.com/d/111-newtmgr-problems
I’ve tried unplugging and replugging and resetting DFU on my device with no luck flashing the GPS sample so far.
Curious if you have any other suggestions.

jaredwolff

occurrentarts try changing your west.yml from v1.4.x to v1.5.x. Then run west update and re-run west build

occurrentarts

@jaredwolff
I tried changing
C:\Users\user\ncs\v1.4.1\nrf\west.yml
to say this:

repo-path: nrf9160-feather-examples-and-drivers
revision: v1.5.x
path: nfed
remote: circuitdojo

Then ran west update. Seems to have found the head suggesting that the samples were updated, but when I look they appear to be the same. When I try and flash to the device the same issue occurs.

jaredwolff

occurrentarts ahh you’re running NCS. You’re going to have to update to NCS 1.5.x (NFED version needs to match the NCS version)

Best way to do that is go to your NRF folder, run git reset --hard then git checkout v1.5.1. Then edit your west.yml and then run west update

The top of gps/main.c should look like so:

#ifdef CONFIG_BOARD_NRF9160DK_NRF9160NS
#define AT_MAGPIO      "AT\%XMAGPIO=1,0,0,1,1,1574,1577"
#ifdef CONFIG_GPS_SAMPLE_ANTENNA_ONBOARD
#define AT_COEX0       "AT\%XCOEX0=1,1,1565,1586"
#elif CONFIG_GPS_SAMPLE_ANTENNA_EXTERNAL
#define AT_COEX0       "AT\%XCOEX0"
#endif
#endif /* CONFIG_BOARD_NRF9160DK_NRF9160NS */

#ifdef CONFIG_BOARD_THINGY91_NRF9160NS
#define AT_MAGPIO      "AT\%XMAGPIO=1,1,1,7,1,746,803,2,698,748,2,1710,2200," \
			"3,824,894,4,880,960,5,791,849,7,1565,1586"
#ifdef CONFIG_GPS_SAMPLE_ANTENNA_ONBOARD
#define AT_COEX0       "AT\%XCOEX0=1,1,1565,1586"
#elif CONFIG_GPS_SAMPLE_ANTENNA_EXTERNAL
#define AT_COEX0       "AT\%XCOEX0"
#endif
#endif /* CONFIG_BOARD_THINGY91_NRF9160NS */

#ifdef CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS
#define AT_COEX0 		"AT%XCOEX0=1,1,1565,1586"
#endif /* CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS */

occurrentarts

Do I need to update my toolchain to 1.5.1 as well?
Is this still the most recent SDK?

http://developer.nordicsemi.com/.pc-tools/toolchain/ncs-toolchain-v1.4.1-20201215-7ecf886-minimal.zip

jaredwolff

Correction: the checkout command is git checkout v1.5.1

jaredwolff

Also check your west update output carefully. If you’ve modified any of the source files, it will not update fully. Usually errors show up as yellow text.

occurrentarts

@jaredwolff
as you suggested i went to ~/ncs/v1.4.1/nrf/
then ran git reset --hard then git checkout v1.5.1.
Then edited ~/ncs/v1.4.1/nrf/west.yml and then run west update
It did not appear to have any issues with this update, no yellow text, though it did require for me to update west beforehand.

I checked on the gps sample in:
C:\Users\mcgaw\ncs\v1.4.1\nrf\samples\nrf9160\gps\src\main.c
It did appear to have changed / been overwritten.

It contains the first two ifdefs you show but does not contain the CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS one.
I tried adding those lines myself ( as you mention above ) but when I go back to try and build it, it results in errors:

[0/1] Re-running CMake...
Including boilerplate (Zephyr base (cached)): C:/Users/mcgaw/ncs/v1.4.1/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps
-- Zephyr version: 2.4.99 (C:/Users/mcgaw/ncs/v1.4.1/zephyr)
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: circuitdojo_feather_nrf9160ns
-- Cache files will be written to: C:/Users/mcgaw/ncs/v1.4.1/zephyr/.cache
-- Found dtc: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt)
-- Found BOARD.dts: C:/Users/mcgaw/ncs/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160ns.dts
-- Generated zephyr.dts: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/zephyr/include/generated/device_extern.h

warning: NRF9160_GPS_SET_COEX0 (defined at
C:/Users/mcgaw/ncs/v1.4.1/nrf\drivers\gps\nrf9160_gps/Kconfig:86) was assigned the value 'y' but got
the value 'n'. Check these unsatisfied dependencies: NRF9160_GPS_HANDLE_MODEM_CONFIGURATION (=n),
NRF9160_GPS (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_NRF9160_GPS_SET_COEX0.html and/or look
up NRF9160_GPS_SET_COEX0 in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: NRF9160_GPS_COEX0_STRING (defined at
C:/Users/mcgaw/ncs/v1.4.1/nrf\drivers\gps\nrf9160_gps/Kconfig:92) was assigned the value
'AT%XCOEX0=1,1,1565,1586' but got the value ''. Check these unsatisfied dependencies:
NRF9160_GPS_SET_COEX0 (=n), NRF9160_GPS_HANDLE_MODEM_CONFIGURATION (=n), NRF9160_GPS (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_NRF9160_GPS_COEX0_STRING.html and/or
look up NRF9Parsing C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/Kconfig
Loaded configuration 'C:/Users/mcgaw/ncs/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160ns_defconfig'
Merged configuration 'C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/prj.conf'
No change to configuration in 'C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/zephyr/.config'
No change to Kconfig header in 'C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/zephyr/include/generated/autoconf.h'
160_GPS_COEX0_STRING in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

Changed board to secure circuitdojo_feather_nrf9160 (NOT NS)

=== child image spm -  begin ===
Including boilerplate (Zephyr base (cached)): C:/Users/mcgaw/ncs/v1.4.1/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/spm
-- Zephyr version: 2.4.99 (C:/Users/mcgaw/ncs/v1.4.1/zephyr)
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: circuitdojo_feather_nrf9160
-- Cache files will be written to: C:/Users/mcgaw/ncs/v1.4.1/zephyr/.cache
-- Found dtc: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt)
-- Found BOARD.dts: C:/Users/mcgaw/ncs/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160.dts
-- Generated zephyr.dts: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm/zephyr/include/generated/device_extern.h
Parsing C:/Users/mcgaw/ncs/v1.4.1/zephyr/Kconfig
Loaded configuration 'C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm/zephyr/.config'
No change to configuration in 'C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm/zephyr/.config'
No change to Kconfig header in 'C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm/zephyr/include/generated/autoconf.h'
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm
=== child image spm -  end ===

Dropping partition 'nrf_modem_lib_trace' since its size is 0.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build
[0/159] Performing build step for 'spm_subimage'
[1/191] Building C object modules/nrfxlib/nrf_security/src/mbedtls/shared/CMakeFiles/mbedcrypto_shared.dir/C_/Users/mcgaw/ncs/v1.4.1/mbedtls/library/sha512.c.obj
[2/191] Linking C static library modules\nrfxlib\nrf_security\src\mbedtls\shared\libmbedcrypto_shared.a
[3/191] Generating misc/generated/syscalls.json, misc/generated/struct_tags.json
[4/191] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj
FAILED: zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj
C:\Users\mcgaw\ncs\v1.4.1\toolchain\opt\bin\arm-none-eabi-gcc.exe -DBUILD_VERSION=v2.4.99-ncs2 -DEXT_API_MAGIC=0x281ee6de,0xb845acea,23298 -DFIRMWARE_INFO_MAGIC=0x281ee6de,0x8fcebb4c,23298 -DKERNEL -DMBEDTLS_CONFIG_FILE=\"nrf-config.h\" -DNRF9160_XXAA -DUSE_PARTITION_MANAGER=1 -D_FORTIFY_SOURCE=2 -D__PROGRAM_START -D__ZEPHYR__=1 -IC:/Users/mcgaw/ncs/v1.4.1/zephyr/kernel/include -IC:/Users/mcgaw/ncs/v1.4.1/zephyr/arch/arm/include -IC:/Users/mcgaw/ncs/v1.4.1/zephyr/include -Izephyr/include/generated -IC:/Users/mcgaw/ncs/v1.4.1/zephyr/soc/arm/nordic_nrf/nrf91 -IC:/Users/mcgaw/ncs/v1.4.1/nrf/include -IC:/Users/mcgaw/ncs/v1.4.1/nrfxlib/crypto/nrf_cc310_mbedcrypto/include/mbedtls -IC:/Users/mcgaw/ncs/v1.4.1/nrfxlib/crypto/nrf_cc310_mbedcrypto/include -Imodules/nrfxlib/nrf_security/include -Imodules/nrfxlib/nrf_security/include/mbedtls_generated -IC:/Users/mcgaw/ncs/v1.4.1/mbedtls/include -IC:/Users/mcgaw/ncs/v1.4.1/mbedtls/include/mbedtls -IC:/Users/mcgaw/ncs/v1.4.1/modules/hal/nordic/nrfx -IC:/Users/mcgaw/ncs/v1.4.1/modules/hal/nordic/nrfx/drivers/include -IC:/Users/mcgaw/ncs/v1.4.1/modules/hal/nordic/nrfx/mdk -IC:/Users/mcgaw/ncs/v1.4.1/zephyr/modules/hal_nordic/nrfx/. -IC:/Users/mcgaw/ncs/v1.4.1/modules/hal/cmsis/CMSIS/Core/Include -IC:/Users/mcgaw/ncs/v1.4.1/nrf/samples/spm/kernel/include -isystem C:/Users/mcgaw/ncs/v1.4.1/zephyr/lib/libc/minimal/include -isystem c:/users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/include -isystem c:/users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/include-fixed -isystem C:/Users/mcgaw/ncs/v1.4.1/nrfxlib/crypto/nrf_cc310_platform/include -Os -imacros C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/nrf9160/gps/build/spm/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfpu=fpv5-sp-d16 -mfloat-abi=hard -imacros C:/Users/mcgaw/ncs/v1.4.1/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-pointer-sign -Wpointer-arith -Wno-address-of-packed-member -Wno-unused-but-set-variable -Werror=implicit-int -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fno-reorder-functions -fno-defer-pop -fmacro-prefix-map=C:/Users/mcgaw/ncs/v1.4.1/nrf/samples/spm=CMAKE_SOURCE_DIR -fmacro-prefix-map=C:/Users/mcgaw/ncs/v1.4.1/zephyr=ZEPHYR_BASE -fmacro-prefix-map=C:/Users/mcgaw/ncs/v1.4.1=WEST_TOPDIR -ffunction-sections -fdata-sections -mcmse -std=c99 -nostdinc -MD -MT zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj -MF zephyr\CMakeFiles\offsets.dir\arch\arm\core\offsets\offsets.c.obj.d -o zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj   -c C:/Users/mcgaw/ncs/v1.4.1/zephyr/arch/arm/core/offsets/offsets.c
In file included from C:/Users/mcgaw/ncs/v1.4.1/zephyr/include/kernel_includes.h:41,
                 from C:/Users/mcgaw/ncs/v1.4.1/zephyr/include/kernel.h:17,
                 from C:/Users/mcgaw/ncs/v1.4.1/zephyr/arch/arm/core/offsets/offsets_aarch32.c:28,
                 from C:/Users/mcgaw/ncs/v1.4.1/zephyr/arch/arm/core/offsets/offsets.c:12:
C:/Users/mcgaw/ncs/v1.4.1/zephyr/include/sys/kobject.h:351:10: fatal error: syscalls/kobject.h: No such file or directory
  351 | #include <syscalls/kobject.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
ninja: build stopped: subcommand failed.
[1/159] Generating misc/generated/syscalls.json, misc/generated/struct_tags.json
FAILED: modules/nrf/samples/spm_subimage-prefix/src/spm_subimage-stamp/spm_subimage-build spm/zephyr/zephyr.hex spm/zephyr/zephyr.elf spm/libspmsecureentries.a
cmd.exe /C "cd /D C:\Users\mcgaw\ncs\v1.4.1\nrf\samples\nrf9160\gps\build\spm && C:\Users\mcgaw\ncs\v1.4.1\toolchain\opt\bin\cmake.exe --build . --"
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\Users\mcgaw\ncs\v1.4.1\toolchain\opt\bin\cmake.EXE' --build 'C:\Users\mcgaw\ncs\v1.4.1\nrf\samples\nrf9160\gps\build'

I see 1.4.1 is still the toolchain listed for NCS in the filepath, do I need to update the toolchain /sdk in NRFConnect somehow for it to be the same ncs and nfed? I do see a blue ((v1.5.1)) showing up after my path in Bash..

In my build error for the gps sample it looks like it references the values you shared before:

"AT\%XCOEX0=1,1,1565,1586"

It mentions unsatisfied dependencies.
Is the build experiencing an error related to the antenna code?
Do I need to install something else?

jaredwolff

occurrentarts you’ll want to compile the samples within nfed not nrf. Try compiling nfed/samples/gps instead. Also remove your build folder before you re-build whenever you update your SDK version or else you’ll get weird errors like the one above.

occurrentarts

@jaredwolff

So when I check on the nfed/samples/gps main.c does look like how you suggested including the

#ifdef CONFIG_BOARD_CIRCUITDOJO_FEATHER_NRF9160NS

When I try to build it straight off it get this error and log:

-- west build: generating a build system
-- Adding .overlay for mcuboot.
Including boilerplate (Zephyr base): C:/Users/mcgaw/ncs/v1.4.1/zephyr/cmake/app/boilerplat
-- Application: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps
-- Zephyr version: 2.4.99 (C:/Users/mcgaw/ncs/v1.4.1/zephyr)
-- Found Python3: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/python.exe (found suitable eion "3.8.2") found components:  Interpreter
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: circuitdojo_feather_nrf9160ns
-- Cache files will be written to: C:/Users/mcgaw/ncs/v1.4.1/zephyr/.cache
-- Found dtc: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/dtc.exe (found suitable version minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt)
-- Found BOARD.dts: C:/Users/mcgaw/ncs/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf916dojo_feather_nrf9160ns.dts
-- Generated zephyr.dts: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/zephyr.dt
-- Generated devicetree_unfixed.h: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyrgenerated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/inclated/device_extern.h
Parsing C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/Kconfig
Loaded configuration 'C:/Users/mcgaw/ncs/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf9itdojo_feather_nrf9160ns_defconfig'
Merged configuration 'C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/prj.conf'
Configuration saved to 'C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/.config'
Kconfig header saved to 'C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/include/gautoconf.h'
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/arm-none-eabi-gcc.exe
CMake Error at C:/Users/mcgaw/ncs/v1.4.1/zephyr/cmake/extensions.cmake:1735 (message):
  Assertion failed: Cannot locate SUPL Client library, should be located in
  your nrf repo ext/lib/bin/supl.
Call Stack (most recent call first):
  C:/Users/mcgaw/ncs/v1.4.1/nrf/ext/CMakeLists.txt:11 (assert)

-- Configuring incomplete, errors occurred!
See also "C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/CMakeFiles/CMakeError.log".
FATAL ERROR: command exited with status 1: 'C:\Users\mcgaw\ncs\v1.4.1\toolchain\opt\bin\cm'-DWEST_PYTHON=c:\users\mcgaw\ncs\v1.4.1\toolchain\opt\bin\python.exe' '-BC:\Users\mcgaw\n\nfed\samples\gps\build' '-SC:\Users\mcgaw\ncs\v1.4.1\nfed\samples\gps' -GNinja -DBOARD=ci_feather_nrf9160ns

When I try to add the values to the .prj file you previously recommended:

# COEX0 is used to enable the GPS LNA, but it has to be configured to do so.
CONFIG_NRF9160_GPS_SET_COEX0=y
CONFIG_NRF9160_GPS_COEX0_STRING="AT%XCOEX0=1,1,1565,1586"

it gives the following log:

-- west build: making build dir C:\Users\mcgaw\ncs\v1.4.1\nfed\samples\gps\build pristine
-- west build: generating a build system
-- Adding .overlay for mcuboot.
Including boilerplate (Zephyr base): C:/Users/mcgaw/ncs/v1.4.1/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps
-- Zephyr version: 2.4.99 (C:/Users/mcgaw/ncs/v1.4.1/zephyr)
-- Found Python3: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components:  Interpreter
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: circuitdojo_feather_nrf9160ns
-- Cache files will be written to: C:/Users/mcgaw/ncs/v1.4.1/zephyr/.cache
-- Found dtc: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt)
-- Found BOARD.dts: C:/Users/mcgaw/ncs/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160ns.dts
-- Generated zephyr.dts: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/include/generated/device_extern.h

warning: NRF9160_GPS_SET_COEX0 (defined at
C:/Users/mcgaw/ncs/v1.4.1/nrf\drivers\gps\nrf9160_gps/Kconfig:86) was assigned the value 'y' but got
the value 'n'. Check these unsatisfied dependencies: NRF9160_GPS_HANDLE_MODEM_CONFIGURATION (=n),
NRF9160_GPS (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_NRF9160_GPS_SET_COEX0.html and/or look
up NRF9160_GPS_SET_COEX0 in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: NRF9160_GPS_COEX0_STRING (defined at
C:/Users/mcgaw/ncs/v1.4.1/nrf\drivers\gps\nrf9160_gps/Kconfig:92) was assigned the value
'AT%XCOEX0=1,1,1565,1586' but got the value ''. Check these unsatisfied dependencies:
NRF9160_GPS_SET_COEX0 (=n), NRF9160_GPS_HANDLE_MODEM_CONFIGURATION (=n), NRF9160_GPS (=n). See
http://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_NRF9160_GPS_COEX0_STRING.html and/or
look up NRF9Parsing C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/Kconfig
Loaded configuration 'C:/Users/mcgaw/ncs/v1.4.1/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160ns_defconfig'
Merged configuration 'C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/prj.conf'
Configuration saved to 'C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/.config'
Kconfig header saved to 'C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/zephyr/include/generated/autoconf.h'
160_GPS_COEX0_STRING in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU
-- Found assembler: C:/Users/mcgaw/ncs/v1.4.1/toolchain/opt/bin/arm-none-eabi-gcc.exe
CMake Error at C:/Users/mcgaw/ncs/v1.4.1/zephyr/cmake/extensions.cmake:1735 (message):
  Assertion failed: Cannot locate SUPL Client library, should be located in
  your nrf repo ext/lib/bin/supl.
Call Stack (most recent call first):
  C:/Users/mcgaw/ncs/v1.4.1/nrf/ext/CMakeLists.txt:11 (assert)

-- Configuring incomplete, errors occurred!
See also "C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/CMakeFiles/CMakeOutput.log".
See also "C:/Users/mcgaw/ncs/v1.4.1/nfed/samples/gps/build/CMakeFiles/CMakeError.log".
FATAL ERROR: command exited with status 1: 'C:\Users\mcgaw\ncs\v1.4.1\toolchain\opt\bin\cmake.EXE' '-DWEST_PYTHON=c:\users\mcgaw\ncs\v1.4.1\toolchain\opt\bin\python.exe' '-BC:\Users\mcgaw\ncs\v1.4.1\nfed\samples\gps\build' '-SC:\Users\mcgaw\ncs\v1.4.1\nfed\samples\gps' -GNinja -DBOARD=circuitdojo_feather_nrf9160ns

So it appears to have the same issue it just adds the new stuff regarding the GPS as errors?
Do I need to install a SUPL client library somehow?

occurrentarts

@jaredwolff
I’ve found this information about SUPL:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/others/supl_os_client.html#supl-client
and
https://www.nordicsemi.com/Products/Development-hardware/nrf9160-dk/download#supl-c

I submitted my email to get a download link.
Hopefully they will approve me and then I can install SUPL to resolve the above build issue for the gps sample, but they seem to rely on DevZone login records, I just created an account now, but I haven’t used DevZone so I’m not sure they’ll approve me.