Verification

• I searched for similar bug reports (including closed issues) and found none was relevant.

What happened?

Building the dev container fails when installing the NRF SDK

What should happen instead?

Dev container build should work

Reproduction steps

Just try to build the container.

More details?

The NRF SDK seems to have changed to be available under a different URL. Currently build.sh tries to wget https://developer.nordicsemi.com/nRF5_SDK/nRF5_SDK_v15.x.x/nRF5_SDK_15.3.0_59ac345.zip -O /tmp/nRF5_SDK_15.3.0_59ac345, but this returns a 404:

--2025-03-11 21:59:12--  https://developer.nordicsemi.com/nRF5_SDK/nRF5_SDK_v15.x.x/nRF5_SDK_15.3.0_59ac345.zip
Resolving developer.nordicsemi.com (developer.nordicsemi.com)... 104.18.26.60, 104.18.27.60, 2606:4700::6812:1b3c, ...
Connecting to developer.nordicsemi.com (developer.nordicsemi.com)|104.18.26.60|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2025-03-11 21:59:12 ERROR 404: Not Found.

When going to the download page, the SDK is now available from https://nsscprodmedia.blob.core.windows.net/prod/software-and-other-downloads/sdks/nrf5/binaries/nrf5sdk153059ac345.zip.

It seems like NRF has moved the download to a new location. I have a commit in my fork which updates the build script to fetch from the same URL the download website currently provides. This solves the build issue for me. I can create a pull request to transfer the fix if you like.

Version

1.15.0

Companion app

No response