RE: app timer and scheduler issues and enhancements

Phil Young — Thu, 24 Jan 2019 16:58:23 GMT

What might be a useful implementation is to allow a timer object to contain a pointer to a scheduler, and to define a structure for a scheduler so that multiple schedulers can be instantiated.

Then when a timer expires the timer could schedule the asynchronous callback on a scheduler specified by the user allowing for flexibility in scheduling, for example I would then define schedulers for fast events and events that might take some time to execute, or simply assign schedulers to different priorities.

my system currently uses a co-operative scheduling system to avoid using an RTOS and this is effectively what I do using a scheduler class, but in order to use the system timer I have to use a second callback that acts as a proxy and re-schedules events from the app_scheduler to different schedulers so that low priority events can be deferred.

It works but it's not as clean as it could be with the above suggestion.

RE: app timer and scheduler issues and enhancements

Kenneth — Thu, 24 Jan 2019 16:47:56 GMT

Hi,

As you have already identified, the scheduler in the nRF5 SDK is very simple, there is no priority, just a simple fifo queue. The only thing I can say is that there will be changes coming that will address your input.

Best regards,
Kenneth