maxikrie commented on issue #16829: URL: https://github.com/apache/nuttx/issues/16829#issuecomment-3180902189
I think I found the root cause of the issue, but I am not sure I can yet make much sense of it. The issue seems to be related to `CONFIG_RR_INTERVAL=200`, which was enabled for no specific reason, but rather carried over from the nsh example of this board. When this configuration parameter is greater 0, ` sched_next_time = nxsched_process_scheduler(ticks, elapsed, noswitches); (sched_timerexpiration.c:365) ` returns 1. If the configuration parameter is 0, then the function also returns 0. When `sched_next_time` is 1, the wrong interval is set in `nxsched_timer_start` and as a result the the timer interrupt never fires, which should wake up `usleep`. For me, I can resolve my issue by removing the round-robin configuration parameter - but I am not sure if there is a bigger underlying issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
