Also, after the green bars were gone I tried to run newtmgr again and now it responded with “Error: The system cannot find the file specified.”

Might this have to do with the initial mistake I made fetching and checking out the latest master in the wrong directory?

As you mentioned, it turns out this build needs 199 kB and I think you said the limit is 192. I’ll be ordering the nRF5340 PDK.
Thanks, Steve

The AGPS example should compile < 195kB. (Since the example binary works A-Ok) It’s hard to tell what could be wrong here without getting a diff of the project. Can you run git status and git log -n 1 within the ncs/nrf directory?

Thanks!

Yes. Here it is:

PS C:\ncs\nrf> git status
HEAD detached from bb259bfa
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   samples/nrf9160/nrf_cloud_agps/prj.conf

no changes added to commit (use "git add" and/or "git commit -a")
PS C:\ncs\nrf> git log -n 1
commit a83f2e623fe81f0eb3873f0138d32c10eb8b8d59 (HEAD)
Author: Steve Doroff <Steve.Doroff@gmail.com>
Date:   Mon Nov 2 11:15:17 2020 -0500

    Add nrf prefix
PS C:\ncs\nrf>

Ahh yea looks like you’ve made some changes. I don’t recommend directly committing to the nrf directory since when you update your changes won’t rebase along with the SDK. I’ll be sharing more about this in my upcoming blog article.

I didn’t perform the commit of the changes until this morning, but I had the same Error 3 as yesterday, so maybe that is only part of the problem. Also, I don’t know VSC very well and I definitely don’t know it well as a source control tool. this morning I was just trying to see if anything worked, probably to my demise. I performed the staging and commit so it would add the additional configuration commands, so I guess unfortunately I committed the changes thinking that would fix the issue. Is there a way to undo what i did easily? Or, should I delete the entire nrf directory and re-perform the entire windows setup? If I did that would that create an issue in VCS? As I mentioned above, I don’t know that would solve the issue because when I first ran into Error 3 I hadn’t staged nor committed anything. It was the same process as when I was running blinky, button or fade_led, which all ran okay with just updating the config, running west, establishing the com port, going into DFU mode and then running newtmgr for update bin and reset.

    SteveD0 I committed the changes thinking that would fix the issue. Is there a way to undo what i did easily? Or, should I delete the entire nrf directory and re-perform the entire windows setup? If I did that would that create an issue in VCS?

    You can always roll back a change with Git by using the git reset command. I’m a fan of SourceTree which makes navigating things a little easier. 🙂

    SteveD0 It was the same process as when I was running blinky, button or fade_led, which all ran okay with just updating the config, running west, establishing the com port, going into DFU mode and then running newtmgr for update bin and reset.

    Got it. It may be your toolchain which is adding the extra size. What do you get when you run arm-none-eabi-gcc --version?

        PS C:\ncs\nrf> arm-none-eabi-gcc ‘–version’
        arm-none-eabi-gcc.exe (GNU Arm Embedded Toolchain 9-2020-q2-update) 9.3.1 20200408 (release)
        Copyright © 2019 Free Software Foundation, Inc.
        This is free software; see the source for copying conditions. There is NO
        warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

        What I recommend is you uninstall that version of the toolchain and install this one. I changed the documentation last week to reflect this after testing was causing problems. I would try the AGPS example again with the new toolchain when it’s done.

        SteveD0 No worries. Go into your Add/Remove programs and look for the Arm Embedded Toolchain. Uninstall it like any other program that you’ve installed on your Windows PC.

          Got it - went to programs and applications and I’m now installing it.

          Got a “404: Not Found” from the link you provided.

          I’m in the process now and I used the setx in the instructions. I still points to the old toolchain "setx ZEPHYR_TOOLCHAIN_VARIANT gnuarmemb
          setx GNUARMEMB_TOOLCHAIN_PATH “C:\Program Files (x86)\GNU Arm Embedded Toolchain\9 2020-q2-update”
          "
          It bombed out in my west build:

          PS C:\ncs\nrf\samples\nrf9160\nrf_cloud_agps> west build -b circuitdojo_feather_nrf9160ns
          – west build: generating a build system
          Including boilerplate (Zephyr base (cached)): C:/ncs/zephyr/cmake/app/boilerplate.cmake
          – Application: C:/ncs/nrf/samples/nrf9160/nrf_cloud_agps
          – Zephyr version: 2.3.99 (C:/ncs/zephyr)
          – Found west: C:/Python39/Scripts/west.exe (found suitable version “0.8.0”, minimum required is “0.7.1”)
          – Board: circuitdojo_feather_nrf9160ns
          CMake Error at C:/ncs/zephyr/cmake/toolchain/gnuarmemb/generic.cmake:16 (message):
          Nothing found at GNUARMEMB_TOOLCHAIN_PATH: ’C:/Program Files (x86)/GNU Arm
          Embedded Toolchain/9 2020-q2-update’
          Call Stack (most recent call first):
          C:/ncs/zephyr/cmake/generic_toolchain.cmake:64 (include)
          C:/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
          C:/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
          CMakeLists.txt:9 (find_package)

          – Configuring incomplete, errors occurred!
          FATAL ERROR: command exited with status 1: ‘C:\Program Files\CMake\bin\cmake.EXE’ ‘-DWEST_PYTHON=c:\python39\python.exe’ ‘-BC:\ncs\nrf\samples\nrf9160\nrf_cloud_agps\build’ ‘-SC:\ncs\nrf\samples\nrf9160\nrf_cloud_agps’ -GNinja

          I’m going to go back and fix mine now…

          I NOW HAVE THE RIGHT TOOLCHAIN INSTALLED:

          C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major>setx ZEPHYR_TOOLCHAIN_VARIANT gnuarmemb

          SUCCESS: Specified value was saved.

          C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major>setx GNUARMEMB_TOOLCHAIN_PATH “C:\Program Files (x86)\GNU Arm Embedded Toolchain\9 2020-q2-update”

          SUCCESS: Specified value was saved.

          C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major>arm-none-eabi-gcc –version
          arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]
          Copyright © 2019 Free Software Foundation, Inc.
          This is free software; see the source for copying conditions. There is NO
          warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

          C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major>

          BUT WHEN I RUN WEST I GET THIS ERROR:

          Windows PowerShell
          Copyright © Microsoft Corporation. All rights reserved.

          Try the new cross-platform PowerShell https://aka.ms/pscore6

          PS C:\ncs\nrf\samples\nrf9160\nrf_cloud_agps> west build -b circuitdojo_feather_nrf9160ns -p
          – west build: making build dir C:\ncs\nrf\samples\nrf9160\nrf_cloud_agps\build pristine
          – west build: generating a build system
          Including boilerplate (Zephyr base): C:/ncs/zephyr/cmake/app/boilerplate.cmake
          – Application: C:/ncs/nrf/samples/nrf9160/nrf_cloud_agps
          – Zephyr version: 2.3.99 (C:/ncs/zephyr)
          – Found Python3: C:/Python39/python.exe (found suitable exact version “3.9.0”) found components: Interpreter
          – Found west: C:/Python39/Scripts/west.exe (found suitable version “0.8.0”, minimum required is “0.7.1”)
          – Board: circuitdojo_feather_nrf9160ns
          CMake Error at C:/ncs/zephyr/cmake/toolchain/gnuarmemb/generic.cmake:16 (message):
          Nothing found at GNUARMEMB_TOOLCHAIN_PATH: ’C:/Program Files (x86)/GNU Arm
          Embedded Toolchain/9 2020-q2-update’
          Call Stack (most recent call first):
          C:/ncs/zephyr/cmake/generic_toolchain.cmake:64 (include)
          C:/ncs/zephyr/cmake/app/boilerplate.cmake:527 (include)
          C:/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
          C:/ncs/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: ‘C:\Program Files\CMake\bin\cmake.EXE’ ‘-DWEST_PYTHON=c:\python39\python.exe’ ‘-BC:\ncs\nrf\samples\nrf9160\nrf_cloud_agps\build’ ‘-SC:\ncs\nrf\samples\nrf9160\nrf_cloud_agps’ -GNinja -DBOARD=circuitdojo_feather_nrf9160ns
          PS C:\ncs\nrf\samples\nrf9160\nrf_cloud_agps>

          I’M NOT SURE WHERE THIS ISSUE IS….

          Looks like the setx is not quite right:

          Here is mine: C:\Program Files (x86)\GNU Tools Arm Embedded\9 2019-q4-major

          Terms and Conditions | Privacy Policy