nRF Connect SDK on Mac - Cannot create new build configuration

[len_]

Previously, nRF Connect SDK was working without issue. However, now when I try to create a new build configuration, it hangs at the following step:

It's unclear why this began happening, it was working fine before and occurred in the middle of a session where build configurations had been created successfully several times.

Although I can't create new build configurations, I can still build and flash existing configurations as normal.

This error has happened many times before, but usually is fixed by restarting VS Code. However, this solution is no longer working. I also tried restarting my computer but it didn't help.

I'm aware a similar ticket was raised here but this thread doesn't provide a fix. When using the command line solution provided in the original post, it still hangs at the Gnuld step.

nRF Connect SDK 2.8.0

VS Code 1.95.3

macOS Ventura 13.0

Apple M2

nrfjprog version: 10.24.2

JLinkARM.dll version: 7.94e

[Øyvind]

Hello, 

Testing with my Macbook Air M2 with MacOS Sequoia 15.0 (24A335), I'm not able to reproduce the issue that you describe. I installed NCS v2.8.0 via VS code extension.

Can you please click on the blue text in the pop-up message to show the build log? Can you provide the build logs? 
What sample are you trying to build? 

Kind regards,
Øyvind

[len_]

Hi Øyvind,

I attempted to make a build configuration for the following samples:

• Central and Peripheral HRS
• Central
• GATT Discovery Manager
• Peripheral CTS

and all produced the above error.

However, it was resolved when I closed all my VS Code windows except for one and tried building the configuration again. Now it is working fine and the error is no longer occurring (hence I cannot provide logs, sorry).

Does the nRF Connect SDK for VS Code extension only work in one window at a time? I thought we could work on several applications concurrently. Apologies if I missed this in the documentation.

Thanks,

Elena

[Øyvind]

Hi Elena, 

len_ said:

Does the nRF Connect SDK for VS Code extension only work in one window at a time?

No, not that I'm aware of. I have several windows open at a time without any issues. 

Could you please provide the output from running the nRF Connect: Generate Support information from the Command Palette? 

Thanks.

Kind regards,
Øyvind

[len_]

Hello, the issue has reappeared. I think the sequence that makes it happen is:
1) Have VS Code window open with nRF Connect SDK, with at least one application which has an existing build configuration open. 
2) Open new VS Code window. Either create new nRF Connect SDK application or open existing application in this new window.
3) Application appears to have no build configurations, so you are prompted to create one by clicking on "Add build configuration".
4) Compiler hangs at "Gnu ld" step as described above.

Here is the build log (for the GATT DM example):

   ****************************************
   * Running CMake for peripheral_gatt_dm *
   ****************************************

Loading Zephyr default modules (Zephyr base).
-- Application: /Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm
-- CMake version: 3.21.0
-- Found Python3: /opt/nordic/ncs/toolchains/15b490767d/bin/python (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: /Users/student/Library/Caches/zephyr
-- Zephyr version: 3.7.99 (/opt/nordic/ncs/v2.8.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf52840dk, qualifiers: nrf52840
-- Found host-tools: zephyr 0.16.8 (/opt/nordic/ncs/toolchains/15b490767d/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (/opt/nordic/ncs/toolchains/15b490767d/opt/zephyr-sdk)
-- Found Dtc: /opt/nordic/ncs/toolchains/15b490767d/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6") 
-- Found BOARD.dts: /opt/nordic/ncs/v2.8.0/zephyr/boards/nordic/nrf52840dk/nrf52840dk_nrf52840.dts
-- Generated zephyr.dts: /Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm/build/peripheral_gatt_dm/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm/build/peripheral_gatt_dm/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm/build/peripheral_gatt_dm/zephyr/dts.cmake
Parsing /opt/nordic/ncs/v2.8.0/zephyr/Kconfig
Loaded configuration '/opt/nordic/ncs/v2.8.0/zephyr/boards/nordic/nrf52840dk/nrf52840dk_nrf52840_defconfig'
Merged configuration '/Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm/prj.conf'
Merged configuration '/Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm/build/peripheral_gatt_dm/zephyr/.config.sysbuild'
Configuration saved to '/Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm/build/peripheral_gatt_dm/zephyr/.config'
Kconfig header saved to '/Users/student/nRF_Dev_Academy/central-dm/central-dm/peripheral_gatt_dm/build/peripheral_gatt_dm/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/15b490767d/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version "2.38") 

There is no error message, the compiler simply hangs at this step. I have sent you the support information via private message.