How to interpret the thread state in Call Stack in VS Code?

RE: How to interpret the thread state in Call Stack in VS Code?

Simon — Wed, 24 Aug 2022 14:10:51 GMT

Hmm, I would think that the MPSL thread would be the next to run, however I don't have too much expertise at this area so I'm not sure why it gets stuck at k_sleep for 8-9 minutes. Would you be able to upload a minimal reproducible sample, then I could try to reproduce it on my side and get a better overview and ask some experts internally what the cause might be.

Best regards,

Simon

RE: How to interpret the thread state in Call Stack in VS Code?

ant — Wed, 24 Aug 2022 08:39:35 GMT

I now figure that the Call Stack window treats the priority as unsigned.

sysworkq actually has a priority of -1, BT RX -8, BT TX -9, MPSL -10.

So is it the MPSL work thread holding up the processor?

RE: How to interpret the thread state in Call Stack in VS Code?

ant — Wed, 24 Aug 2022 00:59:51 GMT

My environment has dozen of BLE devices flooding with advertisements. The devices together can generate 200+ advertisements per second. Could this cause the BT threads busy enough to starve out other threads?

RE: How to interpret the thread state in Call Stack in VS Code?

Simon — Tue, 23 Aug 2022 10:06:15 GMT

Hello,

I'll take a look at this today/tomorrow

Best regards,

Simon