nrf52 disable interrupt below a certain level

RE: nrf52 disable interrupt below a certain level

Håkon Alseth — Tue, 10 Mar 2020 08:47:52 GMT

Hi,

Glad to hear that you found the source of the initial issue.

[quote user="kodama521"]I thought that the cause of the error handler is called is that some of the important interrupts of softdevice or anything else modules are disabled for a long time, is it correct?[/quote]

I know that you're already found this issue, but: this is a side-effect of when you're re-enabling interrupts again where you get many events triggered at the same time.

The softdevice has a predictive order of events, and when things happen out-of-order, it detects and asserts.

[quote user="kodama521"][/quote]

If so, I thought that disabling interrupts below a certain level is one of the best solution, but I couldn't find the corresponding API.

There is no API for this, you need to parse each interrupt and check manually.

[quote user="kodama521"]change current interrupt level[/quote]

Do you mean exit the interrupt handler? I am not sure I understand really what you want to obtain here.

Kind regards,

Håkon

RE: nrf52 disable interrupt below a certain level

k.k — Tue, 10 Mar 2020 08:10:58 GMT

The problem has solved, the cause is our software bug (SOFTDEVICE_PRESENT definition is disabled.).

Thanks to your advice, I tried to watch inside the CRITICAL_REGION_ENTER function and could find this bug. Thank you so much.

But I still want to know how to realize following 2 methods;

change current interrupt level
disable interrupt below a certain level

RE: nrf52 disable interrupt below a certain level

k.k — Tue, 10 Mar 2020 03:19:04 GMT

I found that the error handler is from `sd_softdevice_enable` (the second argument callback function is called). If CRITICAL_REGION_ENTER/EXIT is used and after a certain period of time in this region, the error handler is called.

I thought that the cause of the error handler is called is that some of the important interrupts of softdevice or anything else modules are disabled for a long time, is it correct?

If so, I thought that disabling interrupts below a certain level is one of the best solution, but I couldn't find the corresponding API.

RE: nrf52 disable interrupt below a certain level

k.k — Mon, 09 Mar 2020 13:05:13 GMT

When i used CRITICAL_REGION_ENTER/EXIT functions, and excecuted a little bit time consuming process in this region, an error handler from ble_stack was called. I want to do time consuming process without any interrups from peripherals.

RE: nrf52 disable interrupt below a certain level

Håkon Alseth — Mon, 09 Mar 2020 12:37:20 GMT

[quote user="kodama521"]but I want to allow only ble stack interrupt, so those functions can not be used.[/quote]

The functions will disable all interrupt vectors that belong to the application, and keep the softdevice owned vectors still enabled.

Isn't this what you want?

Kind regards,

Håkon

RE: nrf52 disable interrupt below a certain level

k.k — Mon, 09 Mar 2020 11:53:12 GMT

Thank you for your reply. And sorry for the lack of information, but I want to allow only ble stack interrupt, so those functions can not be used.

RE: nrf52 disable interrupt below a certain level

Håkon Alseth — Mon, 09 Mar 2020 11:45:49 GMT

Hi,

When the softdevice is present, you can use the macro's CRITICAL_REGION_ENTER and CRITICAL_REGION_EXIT to disable all application interrupts.

This macro will expand to call app_util_platform.c::app_util_critical_region_enter(), which will leave all softdevice interrupts still enabled.

Kind regards,

Håkon