Thingy 52 twi_manager current_int_priority_get quandary.

RE: Thingy 52 twi_manager current_int_priority_get quandary.

Jared — Thu, 03 May 2018 18:56:09 GMT

Turns out that when I was porting the Thingy to the latest SDK (at the time) I had failed to copy over the config exactly. In this case APP_TIMER_CONFIG_USE_SCHEDULER was set to 0 where as it should have been set to 1. When the timer interrupts were firing they were firing in a higher interrupt context thus causing my issues above.

RE: Thingy 52 twi_manager current_int_priority_get quandary.

jublin — Tue, 13 Mar 2018 17:44:51 GMT

s_context_limit may not be what you expect. Look at what is calling twi_manager_init.

In the thingy app:

err_code = twi_manager_init(APP_IRQ_PRIORITY_THREAD);

uint32_t twi_manager_init(app_irq_priority_t context_limit)
{
    s_context_limit = context_limit;
    s_collisions    = 0;

    return NRF_SUCCESS;
}

So APP_IRQ_PRIORITY_HIGHEST means nothing.

Prio_thread would be either 4 or 15, from the app_util_platform.h

I just spent two hours tracking this crap down for a project of my own that suddenly stopped working.

RE: Thingy 52 twi_manager current_int_priority_get quandary.

Jared — Fri, 16 Feb 2018 21:15:25 GMT

Hey Ketil,

Hope you are well and thanks for the response. I ended up changing the default 15 down to 7 and it seems to have fixed what I was seeing without any adverse effects since I wrote this.

Jared

RE: Thingy 52 twi_manager current_int_priority_get quandary.

ketil — Mon, 12 Feb 2018 10:30:27 GMT

Hi Jared,

Which Thingy:52 example are you referring to? If this is related to the Thingy:52 firmware i recommend you file an issue in the Thingy:52 GitHub repository as the devs will answer you directly.

Ketil

RE: Thingy 52 twi_manager current_int_priority_get quandary.

Jared — Thu, 08 Feb 2018 20:40:50 GMT

One weirdness is APP_IRQ_PRIORITY_HIGHEST should be 2 not 15 according to app_util_platform.h. Basically this function is preventing any calls from SD callbacks?