• State Not Answered
  • Replies 11 replies
  • Subscribers 70 subscribers
  • Views 674 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 328651
Options

Issues compiling DECT NR+ examples for evaluation

riconec

I've tried to compile "hello_dect" example using v2.6.1 toolchain and v2.7.0-rc-2 SDK. The sample code is present so I assume the SDK is correct version.

However it fails with this error:

fatal error: nrf_modem_dect_phy.h: No such file or directory


File is present in filesystem, I am using NRF Connect Desktop on Windows with VSCode. Tried reinstalling with cleaning J-link installation, appdata content etc but the issue still persists. Other samples doesn't use any custom settings in CMakeLissts so I assume  nrf_modem_dect_phy.h should be passed in include path to the compiler out of the box.

What am I doing wrong and what are possible solutions? I have option to run linux version of tools via WSL but not sure about USB support there.

  • 0 in reply to Simonr

    I was trying to install SDK and toolchain on another windows PC with the same result. VSCode extension doesn't allow to  install anything above 2.6.1. On windows I used NRF Connect - Toolchain manager to get 2.7.0rc2 from there but still the header gives error.

    Tried to install NRF Connect on fedora, however toolchain manager says SDK above v2 not recomended to be installed with toolchain manager. I tried anyway, gave errors at installation and failed. In the VSCode again there is no 2.7.0 toolchain available, I don't know which toolchain index URL to set so it would appear

  • 0 in reply to riconec

    Hello. I'm facing the same issue. I'm following all the steps to build via the commands line on Mac OS and installed both 2.7.0-rc2 SDK and toolchain. I get the same build error for the dect sample with the nrf9161dk. The command line instruction I'm using is: 

    west build -b nrf9161dk

    Inside the hello_dect directory. I'm facing similar problems with other samples, for example the cellular at_client one. I get the following error (both for the nrf9160 and the nrf9161):

    /opt/nordic/ncs/nrf/include/modem/nrf_modem_lib.h:10:10: fatal error: nrf_modem.h: No such file or directory

    Looks like some configuration step is missing from the dev environment. Any idea what it is?

  • 0

    Hi Yevhenii and Daniel

    I tried this and had some issues on the rc2 as well, but I'm able to build the sample successfully in NCS 2.7.0-rc1 on my end. I had to add the CONFIG_CARRIER to my .conf file (see snippet from the documentation below), but after that it builds successfully.

    On my end I have the v2.7.0-rc1 (and rc2) toolchains after installing the nRF Connect SDK v2.7.0-rc1 with the nRF Connect Toolchain Manager app. How have you installed the SDKs on your end? 

    I'm pretty sure the issue you're seeing is because of the toolchain not matching the SDK version.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Thanks Simonr. I have matching SDK and toolchain versions, but I'm working with the rc2. I will give the rc1 a try today and report back.

  • 0 in reply to Simonr

    Hello Simon,

    i have the same issue. I installed the SDK v2.7.0 and also v2.7.0-rc1/v2.7.0-rc2 with the Toolchain Manager App. It didnt work so far. I made sure the SDK matched the Toolchain.

     : Did rc1 work dor you?

Related