• State Suggested Answer
  • Replies 20 replies
  • Answers 1 answer
  • Subscribers 73 subscribers
  • Views 1023 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 324894
Options

Building infinite loop

Joao Colombari

Hi, 

I am currently finishing the intermediate SDK course of yours and suddenly I got a really strange behavior.

The build just endlessly enters a loop in Found GnuLd as the screenshot shows. I have already tried restarting my computer and SDK and also tried touching VScode with a different SDK version. None worked. 

Any idea? 

João.

SDK version: 2.6.0

Build target: nRF5340 Audio DK

OS: MacOS Sonoma 14.1.2

  • 0

    I am also experiencing the same issue since updating to 2.6.0.  I have tried to remove all my previous ncs SDK's, remove and reinstall ncs 2.6.0, toolchain manager, nrf connect for desktop, VSCode and all nRF-associated extensions, to no avail.  The only thing I have noticed is that GnuLd will operate for one time after rebooting my machine.  But all subsequent attempts to build, GnuLd spins forever.  This applies to all the samples.  When building an application with a parent and child after rebooting my machine, it operates for the parent, but stalls when getting to the child application.

    I am also on MacOS, Sonoma 14.4.  This only started being an issue with ncs 2.6.0.  I was previously using ncs 2.5.0.

    I attempted on my personal machine with Windows 11, and had no issues with ncs 2.6.0.

    Kconfig header saved to '/Users/chris1111/Repositories/aaaaaaa/application/build/inner/hci_ipc/zephyr/include/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/580e4ef81c/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd (found version "2.38")

  • 0

    I have the same Problem (Sonoma 14.4.1, NCS 2.6, nrf52840dk_nrf52840)

    It works with NCS 2.5

  • 0 in reply to Schmid

    Hi,

    What happens if you use NCS v2.5.0 with toolchain v2.6.0 (instead of v2.5.0), and NCS v2.6.0 with the older toolchain v2.5.0?

    Best regards,
    Dejan

  • 0 in reply to dejans

    When I restart vscode, the build directory is still there but no build config is shown in the APPLICATIONS tab, I can delete the dir and build with a new one. But only one time, pristine build again will lead to the error. This happens with 2.6 and 2.5 (I overlooked this because I closed it sorry).

  • 0 in reply to dejans

    Dejans,

    I had the exact same behavior Chris had. I didn't try using NCS 2.5 with 2.6 toolchain, but did use NCS 2.6 with older toolchains (not only 2.5, but some others as well) and it made no difference. 

    After trying changing everything and resinstaling the toolchains with no success, I resintalled every other possible thing - NCS, J-Link and the VSCode extensions and by doing this it finally works. No idea why, but it does"

    João.

Related