• Support
  • Thing Plus not connecting to NRFCloud

@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?

    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.

    @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?

    @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.

    @jaredwolff
    I found the SUPL flag in the prj.conf file which I turned to n and the Build worked and I was able to flash.

    Here’s the log of my output when I run the code:

    ---------------------------------*** Booting Zephyr OS build v2.4.99-ncs2  ***Flash regionsDomainPermissions00 02 0x00000 0x18000 Securerwxl03 31 0x18000 0x100000 Non-SecurerwxlNon-secure callable region 0 placed in flash region 2 with size 32.SRAM regionDomainPermissions00 07 0x00000 0x10000 Securerwxl08 31 0x10000 0x40000 Non-SecurerwxlPeripheralDomainStatus00 NRF_P0               Non-SecureOK01 NRF_CLOCK            Non-SecureOK02 NRF_RTC0             Non-SecureOK03 NRF_RTC1             Non-SecureOK04 NRF_NVMC             Non-SecureOK05 NRF_UARTE1           Non-SecureOK06 NRF_UARTE2           SecureSKIP07 NRF_TWIM2            Non-SecureOK08 NRF_SPIM3            Non-SecureOK09 NRF_TIMER0           Non-SecureOK10 NRF_TIMER1           Non-SecureOK11 NRF_TIMER2           Non-SecureOK12 NRF_SAADC            Non-SecureOK13 NRF_PWM0             Non-SecureOK14 NRF_PWM1             Non-SecureOK15 NRF_PWM2             Non-SecureOK16 NRF_PWM3             Non-SecureOK17 NRF_WDT              Non-SecureOK18 NRF_IPC              Non-SecureOK19 NRF_VMC              Non-SecureOK20 NRF_FPU              Non-SecureOK21 NRF_EGU1             Non-SecureOK22 NRF_EGU2             Non-SecureOK23 NRF_DPPIC            Non-SecureOK24 NRF_REGULATORS       Non-SecureOK25 NRF_GPIOTE1          Non-SecureOKSPM: NS image at 0x1c200SPM: NS MSP at 0x20018010SPM: NS reset vector at 0x1faa1SPM: prepare to jump to Non-Secure image.*** Booting Zephyr OS build v2.4.99-ncs2  ***Starting GPS applicationGPS Socket createdGetting GPS data...[1;1H[2JTracking: 0 Using: 0 Unhealthy: 0---------------------------------Seconds since last fix: 0Searching [|]NMEA strings:---------------------------------[1;1H[2JTracking: 0 Using: 0 Unhealthy: 0---------------------------------Seconds since last fix: 0Searching [/]NMEA strings:---------------------------------[1;1H[2JTracking: 0 Using: 0 Unhealthy: 0---------------------------------Seconds since last fix: 1Searching [-]NMEA strings:$GPGGA,000001.00,,,,,0,,99.99,,M,0,,*36$GPGLL,,,,,000001.00,V,N*4B$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99,1*2D$GPGSV,1,1,0,,,,,,,,,,,,,,,,,1*54$GPRMC,000001.00,V,,,,,,,060180,,,N,V*09---------------------------------[1;1H[2JTracking: 0 Using: 0 Unhealthy: 0---------------------------------Seconds since last fix: 1Searching [\]NMEA strings:$GPGGA,000001.00,,,,,0,,99.99,,M,0,,*36$GPGLL,,,,,000001.00,V,N*4B$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99,1*2D$GPGSV,1,1,0,,,,,,,,,,,,,,,,,1*54$GPRMC,000001.00,V,,,,,,,060180,,,N,V*09---------------------------------[1;1H[2JTracking: 0 Using: 0 Unhealthy: 0---------------------------------Seconds since last fix: 2Searching [|]

    I believe it’s showing GPS connection.
    But I don’t believe this sample connects to nrfcloud.com and reports the coordinates.
    I suppose I should try and combine this sample with the
    C:\Users\user\ncs\v1.4.1\nrf\samples\nrf9160\agps
    samples’ nrfcloud.com communication code?

    @jaredwolff
    I was granted a SUPL license and download!
    I have turned it on and am definitely getting GPS data from the gps sample:

    ---------------------------------[1;1H[2JTracking: 0 Using: 0 Unhealthy: 0---------------------------------Seconds since last fix: 219Searching [|]NMEA strings:$GPGGA,002317.55,,,,,0,,99.99,,M,0,,*30$GPGLL,,,,,002317.55,V,N*4D$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99,1*2D$GPGSV,1,1,0,,,,,,,,,,,,,,,,,1*54$GPRMC,002317.55,V,,,,,,,021021,,,N,V*00

    I see that the nfed gps sample doesn’t include net/cloud.h
    I suppose there’s no existing current sample code for connecting the gps to nrfcloud.com via nfed?
    Are there any current nfed samples which communicate with nrfcloud?

      occurrentarts AGPS was that sample. So you’d have to go back and configure the 1.4.1 sample for COEX0.

      I have a tracker example but that isn’t fully 100% with nRF Cloud since they re-added nRF Cloud support to Tracker V2 more recently.

      Stay tuned though. Let me see if I can get something working here.

      Hey occurrentarts

      Alright, I restored the instructions on the AGPS sample. (Didn’t realize people still needed it!)

      https://docs.jaredwolff.com/nrf9160-agps-sample.html

      You can reverse what I suggested before by going to the nrf directory and running git reset --hard thengit checkout v1.4.1. Then edit your west.yml to included nfed and then run west update.

      Nordic removed this sample from future versions of the SDK (probably because they want people to use their Tracker sample).

      Hope this gets you going in the right direction!

      Hey Jared,

      Thanks so much for updating the documentation and looking into my issue.
      I ended up removing and re-installing the SDK and have re-run the AGPS sample.

      It looks like it’s connecting to nrfcloud.com and GPS data is being sent to the modem:
      *** Booting Zephyr OS build v2.4.0-ncs2 ***Flash regionsDomainPermissions00 02 0x00000 0x18000 Securerwxl03 31 0x18000 0x100000 Non-SecurerwxlNon-secure callable region 0 placed in flash region 2 with size 32.SRAM regionDomainPermissions00 07 0x00000 0x10000 Securerwxl08 31 0x10000 0x40000 Non-SecurerwxlPeripheralDomainStatus00 NRF_P0 Non-SecureOK01 NRF_CLOCK Non-SecureOK02 NRF_RTC0 Non-SecureOK03 NRF_RTC1 Non-SecureOK04 NRF_NVMC Non-SecureOK05 NRF_UARTE1 Non-SecureOK06 NRF_UARTE2 SecureSKIP07 NRF_TWIM2 Non-SecureOK08 NRF_SPIM3 Non-SecureOK09 NRF_TIMER0 Non-SecureOK10 NRF_TIMER1 Non-SecureOK11 NRF_TIMER2 Non-SecureOK12 NRF_SAADC Non-SecureOK13 NRF_PWM0 Non-SecureOK14 NRF_PWM1 Non-SecureOK15 NRF_PWM2 Non-SecureOK16 NRF_PWM3 Non-SecureOK17 NRF_WDT Non-SecureOK18 NRF_IPC Non-SecureOK19 NRF_VMC Non-SecureOK20 NRF_FPU Non-SecureOK21 NRF_EGU1 Non-SecureOK22 NRF_EGU2 Non-SecureOK23 NRF_DPPIC Non-SecureOK24 NRF_GPIOTE1 Non-SecureOK25 NRF_REGULATORS Non-SecureOKSPM: NS image at 0x1c200SPM: NS MSP at 0x200297b8SPM: NS reset vector at 0x21559SPM: 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 sentD: Waiting for time window to operateI: GPS_EVT_OPERATION_BLOCKEDI: 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 processedI: 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: 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 processed+CSCON: 0D: GPS has time window to operateI: GPS_EVT_OPERATION_UNBLOCKEDD: Tracking: 0 Using: 0 Unhealthy: 0D: Seconds since last fix 16D: Tracking: 0 Using: 0 Unhealthy: 0D: Seconds since last fix 17

      I’m not seeing the map show up on nrfcloud.com but it makes sense that the antenna does not support it.

      Is there an antenna that will work with both LTE and Active GPS for this microcontroller?
      Or is there a way we can have the LTE antenna and the Active GPS Antenna both connected to the device?
      I had the nfed GPS code using SUPL running before, is there SUPL support for AGPS as well?

      Thanks!

        occurrentarts I’m not seeing the map show up on nrfcloud.com but it makes sense that the antenna does not support it.

        The map doesn’t show until it receives coordinates from your device. Does it show that the device is connected though?

        occurrentarts Is there an antenna that will work with both LTE and Active GPS for this microcontroller?
        Or is there a way we can have the LTE antenna and the Active GPS Antenna both connected to the device?

        You need two antennas. One for LTE and one for GPS. The hardware does not support combining the two together unfortunately.

        I had the nfed GPS code using SUPL running before, is there SUPL support for AGPS as well?
        AGPS is getting supplementary GPS data from nRF Cloud which is probably on the backend getting it from Google. SUPL downloads AGPS data directly from Google.

        Hey Jared,
        We’ll try to source a GPS antenna then and see how it works.
        In the meantime I was able to use your nfed Button example as a reference to set up a switch interrupt to start sending other hardware messages to nrfcloud.

        Thanks again for all your help.
        If I encounter more issues I’ll create a new support thread for those specific issues.

          occurrentarts In the meantime I was able to use your nfed Button example as a reference to set up a switch interrupt to start sending other hardware messages to nrfcloud.

          That’s great!

          occurrentarts Thanks again for all your help.
          If I encounter more issues I’ll create a new support thread for those specific issues.

          Please do. Thanks 😀

          Terms and Conditions | Privacy Policy