Using the Scheduler (8051 OSAL system to nRF51822)

[Locky]

Hi all,

I just had some general questions regarding events and timers on the nRF51822. I'm coming from a Ti CC2540 8051 which used an OSAL system. This made it quite easy to create events and sub-tasks, and handlers for each event and task. This allowed one class to trigger an event handler in another class quite easily. I'm trying to figure out how to perform equivalent custom event/task handling on the nRF51822. Case in point:

I used the Button Handler to catch button presses/releases. I use this to trigger timers in a Button_Timer.c class which monitor how long a button has been press. While pressed, the duration triggers different LED's to turn on (i.e. if 2sec has elasped, turn on Red led. After 3secs turn off LED, after 5secs trigger a buzzer...etc). I know I can do this by simply using app_timers, but I'd rather avoid using many many timers to handle tasks.

I can't seem to find any example code where the application creates its own events and at certain trigger points pushes them to the scheduler to execute via app_sched_event_put. I may be looking at this all wrong with how the Scheduler is supposed to work, so any advise on the matter is greatly appreciated. Thank you

[Locky]

Thank you for the response. I actually had coded something quite similar to your suggestion. But I have a few issues:

1. I believe the 2nd Scheduler implementation example you showed is what I am trying to do. I have a button_timer.c class similar to the 1sec timer you suggested, which could "put" events in the queue. The handler of for this event in main.c could then handle toggling LEDs. I don't need sub msec timing for execution as its controlling LED events.

2. I'm not entirely clear what advantage there is to enabling the Scheduler parameter of a timer. I understand how it will execute from the main loop rather then have the timer handler run as an interrupt. But I don't see how that really makes a difference.

3. I am trying to code things in a modular way. So all my peripheral timers are coded in separate classes. The button_timer class which handles the 1 second timing is controlled from main.c. But on timeout in button_timer.c I don't have a way to trigger main.c to toggle LEDs. I could have another timer with a handler residing in main.c which I start from button_timer to execute LED toggles on timeout. I just give it a very short timeout parameter. But now things would get quite messy having to code timers just to simulate real-time event handling.

Can anyone else who has migrated from the CC2540/2541 comment on this? Thanks

p.s. Again I don't need greater than 10msec timing accuracy for this as it is reacting to a user pressing a button.

EDIT: Just to tie off this thread, I found an answer in the post.
devzone.nordicsemi.com/.../

Thanks guys

[scytulip]

For question 3: I didn't get your idea. Can't you use one timer for toggling LED? You don't need another timer to detect button status, as app_button will tell you when button is pushed or released. It might be helpful if you can share your code snippet.