RE: Interrupt seems to be starving main loop, but timing doesn't agree.

Susheel Nuguru — Wed, 28 Aug 2024 10:20:52 GMT

It is not clear where (which context) you are printing those logs. It is not clear what other contexts exist in your application.

If k_sleep helped you in your case, then it could be that where ever you introduced the k_sleep will invoke the RTOS scheduler to possible make other contexts run.

It looks like you do not have good control on which contexts are running when. To be able to calibrate the thread priorities and timing, I strongly recommend you to run your application with Tracing using SystemView

You will get a nice visual view of what thread is blocking which thread like below and this helps you calibrate your thread priorities.

RE: Interrupt seems to be starving main loop, but timing doesn't agree.

coder123 — Tue, 27 Aug 2024 22:41:04 GMT

Apparently adding a

k_sleep(K_NSEC(1));

to the bottom of the while loop makes it work. Not exactly sure why but good enough.