Access to UICR

RE: Access to UICR

Andreas — Mon, 07 Jan 2019 14:06:46 GMT

Hi,

[quote user="SteveHx"]It appears I can get away with a null for the first parameter.[/quote]

The first parameter is the LFCLOCK source information, I suppose you mean the second one? I suggest you use the same call or function to enable it, as when it was enabled before you disable it. It should be something like sd_softdevice_enable(&clock_lf_cfg, app_error_fault_handler);

Best regards,

Andreas

RE: Access to UICR

SteveHx — Fri, 04 Jan 2019 13:42:32 GMT

Okay, that's the best tip I've had so far. Too bad the documentation doesn't mention what header file is needed for each function.

Now I need to figure out what to pass to the enable function. It appears I can get away with a null for the first parameter. I just want to temporarily disable and re-enable the softdevice, obviously, for this use. But what's the standard error function I should be passing as the second parameter?

RE: Access to UICR

Turbo J — Fri, 04 Jan 2019 13:33:27 GMT

You forgot to

#include "nrf_sdm.h"

RE: Access to UICR

SteveHx — Fri, 04 Jan 2019 13:09:46 GMT

I've already tried that. The compiler can't find either the enable or disable functions, and I can't find them either, anywhere in the softdevice files. I'm working with an application that I started from one of the BLE example projects.

RE: Access to UICR

Andreas — Fri, 04 Jan 2019 12:59:41 GMT

Hi,

UICR is protected when the Softdevice is enabled, to write/erase UICR you need to the Softdevice before, and enable it after. You can use sd_softdevice_disable() for this.

Best regards,

Andreas