BLE Interrupts and Flash Operations

RE: BLE Interrupts and Flash Operations

Elfving — Fri, 12 Dec 2025 14:26:12 GMT

Are you using the bare-metal SDK, nRF 5 SDK, or plain bare-metal? I guess the solution is the same though, you need some sort of buffer or scheduler of tasks you can do outside the interrupt.

[quote user="cemile nur damnali"]But I am not sure about the problem's real cause though. [/quote]

I guess the actual fault depends on the situation, but generally, BLE tasks are very time-sensitive and need to be handled right away. You can study this further by looking at the error you've gotten, but I believe the answer will be the same. It is worth noting that if you have something else you need to do that is equally time-sensitive, we've developed multi-core SoCs for this very reason - you can eg. get the extra core on the 54L to do this flash writing.

Regards,

Elfving

RE: BLE Interrupts and Flash Operations

cemile nur damnali — Fri, 12 Dec 2025 12:58:45 GMT

Hi Elfving,

Unfortunately I cannot use RTOS in my project. I want to know the real cause of the conflict to produce a real solution. I remove all of the flash read functions in the BLE interrupts and as I see there is no problem no more. But I am not sure about the problem's real cause though.

For short, did this conflict happened because of this state or was it due to something else?

Sincerely,

RE: BLE Interrupts and Flash Operations

Elfving — Fri, 12 Dec 2025 12:24:51 GMT

Hi,

Like you say, the BLE interrupts are very important and time sensitive, and needs to be done quickly. That you want to store something from these are understandable as well though, but you should rather do this with a workqueue. For more on how to make workqueues, see here.

Regards,

Elfving