Using die temp interrupt causes BLE cannot be initialized

RE: Using die temp interrupt causes BLE cannot be initialized

Turbo J — Sun, 11 May 2025 06:33:49 GMT

You code failed because you MUST NOT use/enable any interrupts for restricted or blocked peripherials at all.

Also I wonder if you ever tried to measure you code power usage. With a measurement time <100µs I don't expect much power savings with interrupt usage.

Especially when you consider that one measurement per second is plenty (read: too much for most applications) there is not that much power usage in the first place.

RE: Using die temp interrupt causes BLE cannot be initialized

Xander To — Sat, 10 May 2025 19:31:59 GMT

I still don't understand.

Firstly, why did my code fail when it only uses Priority 3, which follows the requirement > 2 priority level by SoftDevice?

Secondly, does sd_temp_get uses an interrupt to get the data? I want to save as much power as possible that's quite I wrote my own library file to use the interrupt for getting data. Hope the sd_temp_get also uses the interrupt.

Best regards,

Xander

RE: Using die temp interrupt causes BLE cannot be initialized

Sigurd — Mon, 28 Apr 2025 07:40:00 GMT

Hi!

[quote user=""]

After I add this library code into my BLE code, the BLE cannot be initialized anymore. I traced back and error originated from

nrf_sdh_enable_request() fails to enable soft device with error code 4097. I don't understand why. Can you please help?

[/quote]

See this case: What is error_code 4097 in sd_softdevice_enable?

When using the SoftDevice, you should use the function sd_temp_get() to get the temperature