Building infinite loop

RE: Building infinite loop

duser — Thu, 30 May 2024 00:11:10 GMT

I had the same issue but have no idea why it was happening. I hadn't changed anything in my toolchain at all and things were working fine. Then MacOS did an update and it broke JLink until I flashed my board to the latest version of JLink firmware (7.96J), then I also found out that I couldn't compile from pristine. Totally removing both the toochain and SDK fixed the issue. Upgrading from 2.5.2 to 2.6.1 in place did NOT fix the issue however. I had to totally uninstall

RE: Building infinite loop

sjobyt — Thu, 11 Apr 2024 19:38:44 GMT

I confirm MacOS 14.4.1 M2. Installing toolchain using VSCode extension works.

RE: Building infinite loop

chris1111 — Thu, 11 Apr 2024 17:35:11 GMT

Ok I finally got this worked out. I think there's a few steps missing from the solutions others provided above. I believe what was happening is when the GnuLD gets into a state where it's stalls and remains spinning, canceling the build does not terminate its stall. So trying to remove and reinstall the toolchain and SDK does not do any good while it remains running in the background.

Here was the steps:

1. Restart the machine.

2. Remove nRF Toolchain Manager

3. Remove nRF Connect for Desktop

4. Restart the machine

5. From VSCode remove the SDK, then remove the toolchain.

6. Remove the nRF VSCode extensions.

7. Restart again.

8. Install nRF VSCode extensions.

9. From VSCode, reinstall the ncs 2.6.0 toolchain.

10. From VSCode reinstall the ncs 2.6.0 SDK.

Only after this was I able to build with ncs 2.6.0. Not sure what the root cause was, but it appears there's some issue with the nRF Connect for Desktop application and the nRF Toolchain Manager application and its initial installation of the ncs 2.6.0 SDK.

Please fix this issue with ncs 2.6.0. This caused a week of disrupted development time.

RE: Building infinite loop

Schmid — Thu, 11 Apr 2024 08:53:48 GMT

Removing the Toolchain/SDK with nrf Desktop and installing them with the extension fixed it for me too, thank you

RE: Building infinite loop

waderq21 — Wed, 10 Apr 2024 22:33:33 GMT

Installing everything from inside VSCode worked for me, I was using the nRF Connect for Desktop to install in the toolchains. Switching to installing them with the VSCode extension resolved it for me.

RE: Building infinite loop

Antonio — Wed, 10 Apr 2024 20:00:23 GMT

Keeps compiling for me. I also erased several other extensions that I had from arm. I also made sure to install only the nRF Connect pack

RE: Building infinite loop

chris1111 — Wed, 10 Apr 2024 17:18:53 GMT

I get the exact same behavior. It will build only the first time.

RE: Building infinite loop

chris1111 — Wed, 10 Apr 2024 17:17:59 GMT

Yes the same issue occurs. GnuLd stalls and spins forever.

I also tried the steps @Antonio provided below, where I removed all extensions and SDK/toolchain, then reinstall all from within VSCode. However that did not resolve the issue. GnuLd still continues to stall and spin forever.

RE: Building infinite loop

Antonio — Wed, 10 Apr 2024 12:13:37 GMT

Just made it work thanks to Øyvind A. Sandberg and the help of my friend FAE Don Janysek.

I was using nRF Connect Desktop to handle the SDK and toolchain. I erased the extensions from VS Code, erased the SDKs with nRF Connect Desktop, and installed the extensions again, followed by installing the toolchain and SDK from inside VS Code. It works perfectly now.

RE: Building infinite loop

dejans — Wed, 10 Apr 2024 09:47:19 GMT

Hi all,

Do you get the same build error when you use "west build" instead of building from VS Code?

Best regards,
Dejan

RE: Building infinite loop

waderq21 — Tue, 09 Apr 2024 22:50:57 GMT

Running into the same error, reinstalling everything did not resolve my issue.

To expand on it, if I restart Vscode it will work one time for me before freezing on GnuLd. After the first build, does not matter which SDK version I try they all freeze on the build.

RE: Building infinite loop

chris1111 — Tue, 09 Apr 2024 16:33:36 GMT

As previously stated in my initial reply, this was not a solution. This is not work.

> 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.

RE: Building infinite loop

Joao Colombari — Tue, 09 Apr 2024 15:57:48 GMT

Hello guys!

Thanks for the relies. chris1111 and Schmid , if you don't want to share anything else, I'll close this issue.

João.

RE: Building infinite loop

dejans — Tue, 09 Apr 2024 09:54:14 GMT

Hi Joao Colombari , chris1111 and Schmid

Joao Colombari It is great to hear that your tools are working properly.
chris1111 andSchmid , please try to do the same. Complete reinstallation of the tools might resolve your issues as well.

Best regards,
Dejan

RE: Building infinite loop

chris1111 — Mon, 08 Apr 2024 17:03:57 GMT

I also tried to use the ncs 2.5.2 toolchain with ncs 2.6.0 sdk, but the behavior was the same.

clude/generated/autoconf.h'
-- Found GnuLd: /opt/nordic/ncs/toolchains/20d68df7e5/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")

Also the same behavior with ncs 2.5.0 toolchain with ncs 2.6.0 sdk.

The project I am trying to build is on ncs 2.6.0 sdk, so doing the reverse would not work.

RE: Building infinite loop

Joao Colombari — Mon, 08 Apr 2024 14:36:15 GMT

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.

RE: Building infinite loop

Schmid — Mon, 08 Apr 2024 13:45:22 GMT

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).

RE: Building infinite loop

dejans — Mon, 08 Apr 2024 12:21:54 GMT

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

RE: Building infinite loop

Schmid — Mon, 08 Apr 2024 08:01:43 GMT

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

It works with NCS 2.5

RE: Building infinite loop

chris1111 — Fri, 05 Apr 2024 23:03:58 GMT

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")