• State Not Answered
  • Replies 3 replies
  • Subscribers 25 subscribers
  • Views 135 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289795
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

"arm-none-eabi-gcc"Not Found

user112779

Hi there:

   I were develop product with nrf52832 ,nRF5 SDK version 17.0.2 and  mesh sdk 5.0.0. And i install the toolchain on the ubuntu 20 follow the guidance https://infocenter.nordicsemi.com/index.jsp . I install the arm-none-eabi-gcc through the source code instead of apt-get install but i add the location to the PATH and test the command there was no error. But when i run the command "cmake -GNinja ..", then the output log show that there were no arm-none-eabi-gcc . How can I do to fix that?

  • 0

    Hi,

    The link to the documentation seems wrong. You can use the "Copy URL" link in the top right corner of Infocenter documentation pages, for getting an URL to the given page. I assume you mean:

    In order for us to know what exact error this is, please share the full error output. It will show the exact phrasing of the error, as well as show what happens up to that point.

    Things you can try:

    • Check that you have installed Arm GNU Toolchain, preferrably version 9-2019-q4-major (9.2.1) which is the one tested and confirmed for nRF5 SDK for Mesh v5.0.0, but later versions should also work.
    • Try building with make as build system. This is the default build system for Debian/Ubuntu systems. If you don't have make, you can install it on the system through the package manager.

    Please note that usually you do not need to build the stack. You can build any example using SEGGER Embedded Studio (SES). You can use SES free of charge for nRF SoC projcects, see SEGGER Embedded Studio.

    Regards,
    Terje

  • 0 in reply to user8164
    Hi,

        Thanks reply, my Arm GUN toolchain version is :gcc-arm-none-eabi-10.3-2021.10-x86_64-linux. And i build with make system but the same error was occur.

    detail error output:

    (mesh) parjing@ubuntu:~/code/nrfPrjs/Mesh/build$ sudo cmake -DSDK_ROOT=../../BleSdk ..
    -- Configuring CMake for nRF5 SDK for Bluetooth Mesh 5.0.0
    -- SDK_ROOT=/home/parjing/code/nrfPrjs/BleSdk --- set with command line ARG
    -- Setting build type to 'RelWithDebInfo' as none was specified.
    -- PC-Lint executable not found. Linting disabled.
    -- SDK: nRF5_SDK_17.0.2_d674dde
    -- Platform: nrf52832_xxAA
    -- Arch: cortex-m4f
    -- SoftDevice: s132_7.2.0
    -- Board: pca10040
    -- The C compiler identification is unknown
    -- The ASM compiler identification is unknown
    -- Didn't find assembler
    CMake Error at CMakeLists.txt:75 (enable_language):
    The CMAKE_C_COMPILER:

    arm-none-eabi-gcc

    is not a full path and was not found in the PATH.

    Tell CMake where to find the compiler by setting either the environment
    variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
    the compiler, or to the compiler name if it is in the PATH.


    CMake Error at CMakeLists.txt:75 (enable_language):
    No CMAKE_ASM_COMPILER could be found.

    Tell CMake where to find the compiler by setting either the environment
    variable "ASM" or the CMake cache entry CMAKE_ASM_COMPILER to the full path
    to the compiler, or to the compiler name if it is in the PATH.


    -- Warning: Did not find file Compiler/-ASM
    -- Configuring incomplete, errors occurred!
    See also "/home/parjing/code/nrfPrjs/Mesh/build/CMakeFiles/CMakeOutput.log".
    See also "/home/parjing/code/nrfPrjs/Mesh/build/CMakeFiles/CMakeError.log".
    (mesh) parjing@ubuntu:~/code/nrfPrjs/Mesh/build$
  • 0

    Hi,

    From your first post:

    test the command there was no error.

    What command did you test then, and from what directory?

    Are you able to open and build a mesh example using Segger Embedded Studio (SES)?
    (SES is free of charge for nRF based projects)

    Where did you put the manual install of gcc-arm-none-eabi?

    What path did you add to path?

    Regards,
    Terje

Related
Terms of service