MPSL thread being blocked due to application threads

[Ubaid_M]

Hi,

With reference to the below image:

As you can see I have 2 UART threads running on priorities 14, at baud 115200, which are I believe blocking the MPSL signal thread, due to which my BLE Mesh models are responding to OPCODES with a delay of 9 mins & at time getting stuck without progressing. Further I also observed BT APIs reaching maximum retries.

I need your help with 2 things:

1. How can I get this to work whilst retaining my application & UART threads..?

2. How can I probe the CPU utilization further to find out what is happening or what is the issue leading to MPSL thread being blocked..?

Thanks,

Ubaid

[Sigurd]

Hi,

Looking at the documentation here, I don't really see how your application threads are causing issues:

The scheduler distinguishes between two classes of threads, based on each thread’s priority.

• A cooperative thread has a negative priority value. Once it becomes the current thread, a cooperative thread remains the current thread until it performs an action that makes it unready.

• A preemptible thread has a non-negative priority value. Once it becomes the current thread, a preemptible thread may be supplanted at any time if a cooperative thread, or a preemptible thread of higher or equal priority, becomes ready.

2. How can I probe the CPU utilization further to find out what is happening or what is the issue leading to MPSL thread being blocked..?

You can try to use the CPU load measurement module: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.2/nrf/libraries/debug/cpu_load.html

It's expected that these MPSL threads are 'blocked' most of the time, they are waiting for semaphore in the mpsl irq handler. https://github.com/nrfconnect/sdk-nrf/blob/v1.9.2/subsys/mpsl/init/mpsl_init.c#L53

Q: Does your application work as expected when you don't have these UART threads? If yes, could you post how these threads looks like ?

[Ubaid_M]

Hello Sigurd,

Sigurd said:

You can try to use the CPU load measurement

1. Can you please suggest any tool or add on that gives me thread wise details on CPU occupancy..?
Any live monitoring would help.

Sigurd said:

I don't really see how your application threads are causing issues

This is what I felt as well, But as soon as I comment out the two UART threads & one application threads, my mesh models behave completely fine and response to OPCODES is instantaneous.

Sigurd said:

Does your application work as expected when you don't have these UART threads?

Yes, as soon as I comment out the two UART threads & one application threads, my mesh models behave completely fine.
2. I also observed that by reducing UART baud rate from 115200 to 9600, there was some improvement. Hence I suspect any interrupts are occupying the CPU or any dependent resource like semaphore is unavailable to MPSL thread...?

Sigurd said:

could you post how these threads looks like ?

Will get back on this.

Thanks,

[Ubaid_M]

Hi,

Meanwhile please support me on this..

Ubaid_M said:

1. Can you please suggest any tool or add on that gives me thread wise details on CPU occupancy..?

[Sigurd]

Sigurd said:

You can try to use the CPU load measurement module: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.2/nrf/libraries/debug/cpu_load.html

Also Thread analyzer might be useful.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/services/debugging/thread-analyzer.html#thread-analyzer

[Ubaid_M]

Hi,

Sigurd said:

Also Thread analyzer might be useful.

I am trying to use thread analyzer, can you please help me with a sample program demonstrating the use of Thread analyzer..?

[Ubaid_M]

Hi,

As soon as I am running the analyzer I am getting these logs:

I just called "thread_analyzer_print( );" in my main application thread. Inside the while loop.

Thanks

[Sigurd]

Hi,

Ubaid_M said:

I just called "thread_analyzer_print( );" in my main application thread. Inside the while loop.

You don't need to do that. You can just set CONFIG_THREAD_ANALYZER_AUTO=y

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.0.2/kconfig/index.html#CONFIG_THREAD_ANALYZER_AUTO