Feedback Request: Self-Contained NCS Local SDK/Toolchain

RE: Feedback Request: Self-Contained NCS Local SDK/Toolchain

dejans — Thu, 05 Jun 2025 17:17:15 GMT

Hi,

Your approach looks reasonable as you use repository structure which is similar to the official in NCS example application.
We have some resources in the documentation about this which can provide additional information. You can look at following webpages (if you have not already):
adding code
creating manifest repository from scratch
workspace application repository
redistributing NCS
west manifests

Best regards,
Dejan

RE: Feedback Request: Self-Contained NCS Local SDK/Toolchain

longo92 — Tue, 03 Jun 2025 11:36:30 GMT

Hi Dejan,

yes it is similar- the main difference is the presence of zephyr/module.yml which allows to add custom board/driver/library without relying on EXTRA_ZEPHYR_MODULES in CMakeLists.txt of the application.

My question is on the methodology:

If you needed to implement something similar, how would you approach it in a Nordic environment? All the examples I’ve found, including those from the Developer Academy, assume having nrfutil, the SDK, and the toolchain already installed on the system.
Is in your opnion my approach the "right" way?

Regarding scalability/reliability:

Since the SDK/Toolchain and nrfutil (along with its subcommands) are updated quite frequently, I want to maintain full control over them within our repository. We develop many projects under NCS, each with its own SDK, toolchain, and nrfutil version. Managing these at the system level would be messy and impractical for our needs.

Regarding nrfutil:

in folder tools/nrfutil/nerfutil.exe a specific version is commited with the repo.
All subcommands are installed there by setting $env:NRFUTIL_HOME = "tools/nrfutil/.nrfutil"
All subcommands are called by setting also $env:NRFUTIL_HOME = "$cwd\tools\nrfutil\.nrfutil", for example here the flash_build.ps1 called by my binding tasks (check the .code-workspace file):

param (
    [string]$build_folder,
    [bool] $erase_all = $false
)
$cwd = Get-Location
$nrfutil_command = "$cwd\tools\nrfutil\nrfutil.exe"
#set the env variable pointing nrfutil install dir
$env:NRFUTIL_HOME = "$cwd\tools\nrfutil\.nrfutil"
# program fw
if($erase_all){
    $erase_option = "chip_erase_mode=ERASE_ALL"
} else{
    $erase_option = "chip_erase_mode=ERASE_RANGES_TOUCHED_BY_FIRMWARE"
}
$nrfutil_program_command = "$nrfutil_command device program  --traits jlink --firmware $build_folder/merged.hex  --options $erase_option,reset=RESET_SYSTEM"
Invoke-Expression -Command $nrfutil_program_command

RE: Feedback Request: Self-Contained NCS Local SDK/Toolchain

dejans — Tue, 03 Jun 2025 11:16:26 GMT

Hi Alessandro,

Is your setup the same as in your other ticket linked below?
devzone.nordicsemi.com/.../vsc-extension-nrf-connect-nrfutil-home-how-should-be-used
How do you intend to use nrfutil from your local folder?

[quote user=""]From your expert point of view — do you think the system we’ve set up is scalable and reliable enough?[/quote]

What are your future plans with regard to scalability?
Do you have any specific concerns regarding reliability? What would be "reliable enough" in your case?

Best regards,
Dejan