This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Segger Errors

Hi there!

I am currently trying to follow the SDK instructions to get everything up and running. I followed all steps closely and didn't run into any errors apart from the last step.

When entering the nRF connection options in Segger I get the following error:

I tried v1.2 and the master branch, both won't work with the same error messages. I am on macOS Catalina, nRF Connect 3.3, Segger 4.42a, ARM 8-2019-q3-update toolchain.

Dependencies/requirements were installed successfully and I didn't have any errors while walking through the steps. I am a bit confused what would cause this. If more details are needed please ask :)

Thanks for any help! :)

Parents
  • Hi.

    What board did you choose?

    When building an application that uses the modem, you must build the application as non-secure.

    You can do that (for pre-defined boards) by selecting the non-secure version of the board. It will have "ns" at the end of the name, e.g. nrf9160_pca10090ns.

    Best regards,

    Didrik

  • Hi.

    Thanks for the response. I tried using the Actinius Icarus first (this is the board I have) and the nrf9160_pca10090. Both with and without the ns definition. It's the same error for all 4 scenarios. I have the feeling some dependency or something is missing, but I didn't get any error when going through the SDK instructions.

  • Do you get the same errors when building from the command line?

    Can you send me the output you get when using west from the command line?

  • Here is the output when running:

    west build -b actinius_icarus_ns

    -- west build: build configuration:
           source directory: /Users/nik/nrf/ncs/nrf/samples/nrf9160/at_client
           build directory: /Users/nik/nrf/ncs/nrf/samples/nrf9160/at_client/build
           BOARD: actinius_icarus_ns (origin: command line)
    -- west build: generating a build system
    -- Zephyr version: 2.1.99
    -- Selected BOARD actinius_icarus_ns
    -- Found west: /Users/nik/Library/Python/3.7/bin/west (found suitable version "0.7.2", minimum required is "0.6.0")
    Traceback (most recent call last):
      File "/Users/nik/Library/Python/3.7/bin/west", line 5, in <module>
        from west.main import main
    ModuleNotFoundError: No module named 'west.main'
    Traceback (most recent call last):
      File "/Users/nik/Library/Python/3.7/bin/west", line 5, in <module>
        from west.main import main
    ModuleNotFoundError: No module named 'west.main'
    
    CMake Error at /Users/nik/nrf/ncs/zephyr/cmake/zephyr_module.cmake:45 (message):
      Traceback (most recent call last):
    
        File "/Users/nik/nrf/ncs/zephyr/scripts/zephyr_module.py", line 236, in <module>
          main()
        File "/Users/nik/nrf/ncs/zephyr/scripts/zephyr_module.py", line 200, in main
          returncode=p.returncode)
    
      subprocess.CalledProcessError: Command
      '['/Users/nik/Library/Python/3.7/bin/west', 'list',
      '--format={posixpath}']' returned non-zero exit status 1.
    
    Call Stack (most recent call first):
      /Users/nik/nrf/ncs/zephyr/cmake/app/boilerplate.cmake:458 (include)
      CMakeLists.txt:10 (include)
    
    
    -- Configuring incomplete, errors occurred!
    FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -B/Users/nik/nrf/ncs/nrf/samples/nrf9160/at_client/build -S/Users/nik/nrf/ncs/nrf/samples/nrf9160/at_client -GNinja -DBOARD=actinius_icarus_ns

  • Do you have libgit2 installed?

    We are also in the process of updating the macOs documentation. You can find the open pull request here: https://github.com/zephyrproject-rtos/zephyr/pull/23445

    P.S.

    I would prefer that you show the output of nrf9160_pca10090ns, not actinius_icarus_ns. That way, it is easier to compare to other issues.

  • Thanks for the suggestion, and yup, I installed libgit2 earlier via homebrew. Sadly the errors are still there.

    I also removed the ncs folder completely and ran through the steps again. But the same errors again in Segger as well as via the CLI. Hmm...

Reply Children
No Data
Related