Attachments (2) Download All
Nordic Case Info
  • Case ID: 233531
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can not Load nRF Connect project into Segger Studio getting Did not finish "cmake"

Jeff Seaman

I am trying to install the nRF9160 development environment on an additional computer.  We have the system running on 3 computers now but are in the process of setting one up for testing documentation purposes.

I installed following the Getting Stated assistant v1.0.1 directions for installing the tool chain.

We are working on a windows 10 systems.

I have tried matching the versions of the utilities to one of our working systems without success.

This is a list of the Tool chain versions.

 

amir

Non Working

Karma

Working

cmake

cmake version 3.13.4

cmake version 3.14.5

git

git version 2.22.0.windows.1

git version 2.21.0.windows.1

python

Python 3.7.1

Python 3.7.3

ninja

1.8.2

1.9.0

gperf

GNU gperf 3.1

GNU gperf 3.1

west

West bootstrapper version: v0.5.8 (c:\python37\lib\site-packages\west\_bootstrap)

West bootstrapper version: v0.5.8 (c:\python37\lib\site-packages\west\_bootstrap)

Segger Studio

ARM(Nordic Edition)V4.18

 ARM(Nordic Edition)V4.18
Parents
  • 0

    Hi.

    Is cmake in your path?

    Could you paste the output text from Segger Embedded Studio?

    Like this:

    Best regards,

    Andreas

  • 0 in reply to AndreasF

    just to make sure yes cmake is in the path from a command prompt

    Microsoft Windows [Version 10.0.18362.239]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Users\apasdar>cmake -version
    cmake version 3.14.6

    CMake suite maintained and supported by Kitware (kitware.com/cmake).

    C:\Users\apasdar>

    There is nothing in the Segger Studio screen.I am attaching the log files from the build directory

    Fullscreen CMakeOutput.log Download
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    The target system is: Generic - 1.14.99 - arm
    The host system is: Windows - 10.0.18362 - AMD64
    Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded.
    Compiler: C:/gnuarmemb/bin/arm-none-eabi-gcc.exe
    Build flags:
    Id flags: -c
    The output was:
    0
    Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "CMakeCCompilerId.o"
    The C compiler identification is GNU, found in "C:/ncs/nrf/samples/nrf9160/mqtt_simple/build_nrf9160_pca10090ns/CMakeFiles/3.14.6/CompilerIdC/CMakeCCompilerId.o"
    Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded.
    Compiler: C:/gnuarmemb/bin/arm-none-eabi-gcc.exe
    Build flags:
    Id flags: -c
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Fullscreen 3731.CMakeError.log Download
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
    Compiler: C:/gnuarmemb/bin/arm-none-eabi-gcc.exe
    Build flags:
    Id flags:
    The output was:
    1
    c:/gnuarmemb/bin/../lib/gcc/arm-none-eabi/7.3.1/../../../../arm-none-eabi/lib\libc.a(lib_a-exit.o): In function `exit':
    exit.c:(.text.exit+0x2c): undefined reference to `_exit'
    collect2.exe: error: ld returned 1 exit status
    Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
    Compiler: C:/gnuarmemb/bin/arm-none-eabi-gcc.exe
    Build flags:
    Id flags:
    The output was:
    1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Jeff Seaman

    As a Follow up  I replaced the version of cmake with 3.13.4 like on my working system, and copied the gcc compiler from the working system with no difference.

  • 0 in reply to Jeff Seaman

    Hi.

    You mean you replaced cmake version 3.13.4 with 3.13.5, correct?

    Coul you also try to have the same version of python and ninja as well?

    From the output below it seems like there is an issue with the linker script when you try to build, do you use a new build folder?

    Best regards,

    Andreas

Reply
  • 0 in reply to Jeff Seaman

    Hi.

    You mean you replaced cmake version 3.13.4 with 3.13.5, correct?

    Coul you also try to have the same version of python and ninja as well?

    From the output below it seems like there is an issue with the linker script when you try to build, do you use a new build folder?

    Best regards,

    Andreas

Children
No Data
Terms of service