Directory of C:\nfed

15/12/2020  19:48    <DIR>          .
15/12/2020  19:48    <DIR>          ..
15/12/2020  19:36    <DIR>          .west
15/12/2020  19:45    <DIR>          bootloader
15/12/2020  19:47    <DIR>          mbedtls
15/12/2020  19:52    <DIR>          modules
15/12/2020  19:37    <DIR>          nrf
15/12/2020  19:36    <DIR>          nrf9160-feather
15/12/2020  19:46    <DIR>          nrfxlib
15/12/2020  19:46    <DIR>          test
15/12/2020  19:52    <DIR>          tools
15/12/2020  19:59    <DIR>          zephyr

    mikcatta hmm looks ok. So you’re still getting the “Cannot compile dummy file” error on both Linux and Windows?

    What’s the version of your compiler?

        Evening @jaredwolff

        I’ve got a bit further on Linux, but not quite to point of compiling !

        Both Win & Ubuntu report:

        - The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- The ASM compiler identification is GNU

        I believe I have a compile on Ubuntu !

        Memory region         Used Size  Region Size  %age Used
           FLASH:       12876 B     441856 B      2.91%
            SRAM:        3904 B       128 KB      2.98%
        IDT_LIST:          56 B         2 KB      2.73%
[158/158] Generating zephyr/merged_domains.hex

        Had to follow these instructions on the Nordic site for the Python dependencies, which are ever so slightly different to the instructions on your site. [https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_installing.html#installing-the-required-tools]

        pip3 install –user -r zephyr/scripts/requirements.txt
        pip3 install –user -r nrf/scripts/requirements.txt
        pip3 install –user -r bootloader/mcuboot/scripts/requirements.txt

        I am using CMake 3.18.5 on Ubuntu, but I am not sure that was the issue.

        Hi @jaredwolff Just to clarify….

        I have created a ~/.zephyrrc file which contains

        export PATH=$PATH:/home/mike/cmake-3.18.5-Linux-x86_64/bin
export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
export GNUARMEMB_TOOLCHAIN_PATH="~/gnuarmemb"

        I installed cmake-3.18.5 from source, so it installed it locally. Again not sure, that was the issue. The GNUARMEMB was installed into the directory ~/gnuarmemb

        On first compile, I had to add the “-p” command, so ran west build -b circuitdojo_feather_nrf9160ns -p

        Some of these steps may not be necessary, but it seems to compile a hex file now at least on Ubuntu. Next step will be to see if I can flash it from the VM or maybe in needs to be transferred to Windows for programming the board, but that’s tomorrow little game.

        Got it. I’m looking into utilizing the nRF Desktop SDK Manager. Since you have those already installed, it would make the most sense to use them. Stay tuned..

          HI @jaredwolff

          Apologises, I thought I’d have a go at compiling one of the main apps for the Feather at https://docs.jaredwolff.com/nrf9160-agps-sample.html

          From the /home/mike/nfed/nrf/samples/nrf9160/nrf_cloud_agps, I’ve added the additional lines to the prj.conf, but when I try and compile it says:-

          **/home/mike/nfed/nrf/samples/nrf9160/nrf_cloud_agps/prj.conf:61: warning: attempt to assign the value '"feather-"' to the undefined symbol NRF_CLOUD_CLIENT_ID_PREFIX**
Parsing /home/mike/nfed/nrf/samples/nrf9160/nrf_cloud_agps/Kconfig
Loaded configuration '/home/mike/nfed/zephyr/boards/arm/circuitdojo_feather_nrf9160/circuitdojo_feather_nrf9160ns_defconfig'
Merged configuration '/home/mike/nfed/nrf/samples/nrf9160/nrf_cloud_agps/prj.conf'

error: Aborting due to Kconfig warnings

CMake Error at /home/mike/nfed/zephyr/cmake/kconfig.cmake:217 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /home/mike/nfed/zephyr/cmake/app/boilerplate.cmake:506 (include)
  /home/mike/nfed/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  /home/mike/nfed/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:9 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /home/mike/cmake-3.18.5-Linux-x86_64/bin/cmake -B/home/mike/nfed/nrf/samples/nrf9160/nrf_cloud_agps/build -S/home/mike/nfed/nrf/samples/nrf9160/nrf_cloud_agps -GNinja -DBOARD=circuitdojo_feather_nrf9160ns

          Without that line, it compiles just fine. What I am doing wrong here please?

            mikcatta this example only works on newer versions of the nRF Connect SDK. What version are you using?

                mikcatta @jaredwolff I use the pre-built binary, can I set a custom APN for use with my O2/Telefonica SIM?

                Unfortunately not.

                mikcatta actually you should be able to set a APN if it doesn’t get set already. Have you tried without editing anything? Otherwise you can try something like this in LTE Link Monitor:

                AT+CGDCONT="0,\"IPv4v6\",\"internet.apn\""

                Whereas you can replace internet.apn with your APN.

                Hope that helps!

                      mikcatta Hi @jaredwolf I was just following the instructions on your website, if that doesn’t work, can you clarify that on the site at the URL https://docs.jaredwolff.com/nrf9160-agps-sample.html ?

                      As long as you checkout bb259bfad1fa3572563444edb512fc8a6f12a3f4 or newer for the NRF SDK portion it should work. From the output though it looks like you’re using an older version as NRF_CLOUD_CLIENT_ID_PREFIX didn’t exist before bb259bfad1fa3572563444edb512fc8a6f12a3f4

                      All of this is available in NCS 1.4.0 and above.

                          @mikcatta so I spent some time playing around with compiling with the Toolchain Manager and had some success with the NFED repo.

                          I used v1.4.1 and it work a-ok. Simply open a bash prompt or command prompt. This will pre-load your environment:

                          You’ll have to copy your nrf9160-feather folder from nfed into whichever nRF Connect SDK you’re using. In my case I put my SDK install in C:\ncs\v1.4.1\

                          Change directories and then compile as prescribed before: west build -b circuitdojo_feather_nrf9160ns -p

                            Hi @jaredwolff

                            Yes!!!! That compiled ok on my Windows machine, thank you so much for struggling on with this.

                            My Hologram SIM said it was out of credit after 10 minutes of use, but now showing as “Connected”, so I am a bit confused as to whether that SIM is working or not. I will try again with the O2/Telefonica SIM, now I know how to set the APN.

                            Cheers for your assistance 🙂

                              mikcatta woohoo! Sorry about the SDK setup. Ill be using Nordic’s system since they’ve nicely packaged all the dependencies. I’ll be updating my documentation in the next week to reflect the new change. Very happy it’s working! 😀

                                  Terms and Conditions | Privacy Policy