Failure in ble_stack_init during startup

[SteveHx]

We are trying to bring up a new run of an existing PCB design. No changes in the area of the processor, but a different assembly house. The first call inside ble_stack_init, a call to nrf_sdh_enable_request(), fails and returns an error code of 8. No reference anywhere gives a usable explanation.

Strangely, if started by "copying" the hex file onto the Jlink "drive" (the nRF52832 DevKit), it succeeds.

What should we be looking for?

[Vidar Berg]

Hello,

It seems like the issue might be with how the firmware is programmed since it appears to work when you use drag&drop programming. How are you programming the device when it fails? Is the same error also returned after a reset? Note that the "SoftDevice enable" function may return NRF_ERROR_INVALID_STATE (8) if the debugger forces execution to start from the application start address instead of address 0x0. This prevents the softdevice's reset handler from running on startup.

Best regards,

Vidar

[SteveHx]

I was starting it from SES (Segger) just as I have on dozens of previous nRF52832 projects, and indeed successfully on previous runs of this board. So there's something different in the hardware, and I'm asking where to look. What sort of "invalid state" is likely?

[Vidar Berg]

It looks like you may have an old version of nrfutil installed with an outdated package index. Please try to run "nrfutil self-upgrade" before attempting to run "nrfutil install device" again.

When testing this, please remember to temporarily remove the code that clears the RESETREAS register in your application.

[SteveHx]

If it's an outdated package, the website needs to be updated. I just downloaded the latest. I also tried your self-upgrade suggestion, which failed the same way.

2026-06-19  8:34:20.53 d:\Download>nrfutil self-upgrade
Uninstalled nrfutil
Error: Failed to install nrfutil

Caused by:
    0: Could not download package
    1: failed to download from `developer.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-7.11.1.tar.gz`
    2: failed to get 200 response from `developer.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-7.11.1.tar.gz`, got 410

I also attempted to manually download the device add-on, and got

Gone

The requested resource is no longer available on this server and there is no forwarding address. Please remove all references to this resource.

Next?

[Vidar Berg]

That is strange. Can you post a link to the page you downloaded the executable from? Also, try to run "where nrfutil" to make sure are calling the executable you just downloaded and not one you may have downloaded earlier.

[SteveHx]

Right from the Nordic website:

https://www.nordicsemi.com/Products/Development-tools/nRF-Util

[SteveHx]

And yes, where shows exactly the one I downloaded. I was running it from within the directory where I downloaded it, so no sneaky hidden paths to it.

[SteveHx]

I'm not sure if you fixed something on the website, or my poking around and installing some other commands first fixed it, but it seems to have worked. Now I need to go back to your previous instructions and try again.

2026-06-19  8:57:44.36 d:\Download>nrfutil install toolchain-manager
[00:00:03] ###### 100% [Install packages] Install packages
2026-06-19  8:58:17.81 d:\Download>nrfutil install trace
[00:00:06] ###### 100% [Install packages] Install packages
2026-06-19  8:58:35.05 d:\Download>nrfutil install device
[00:00:05] ###### 100% [Install packages] Install packages
2

[SteveHx]

2026-06-19  9:01:12.66 d:\Download>nrfjprog --memrd 0x40000400
0x40000400: 00000000                              |....|

2026-06-19  9:03:16.55 d:\Download>nrfutil device read --address 0x40000400 --direct
682528135
0x40000400: 00000000                              |....|

So, this reports RESETREAS as all zero, just as my code did. I'm not sure what the second line does, but I think that's the startup value of the stack pointer.

Next?

[Vidar Berg]

Please confirm whether you changed your code so that it is no longer clearing the RESETREAS register. This step is essential for this test. The second line there is the serial number of the debugger and is not a valid memory address.

[SteveHx]

Yes, and I deleted all extraneous code prior to the BLE initialization. It still crashes in the same place and resets.