RTC calendar

[steven]

Hi, I need a RTC calendar ble stack on nrf51822 . (turn on the RTC0 on ble stack and get the count, how to setting the rtc wakeup )

which calendar need follow : track of the time (hours, minutes and seconds) and date (day, week,month, year)

i want to do list: 1.setting(every sec) and turn on the RTC0 interrupt 2.when the rtc0 trigger convert the RTC0 count to time. 3.configure the rtc0 wakeup when it is going to system off. 4.write to flash when system goto system off. 5.if wakeup by rtc0 or i/o, read the data from flash . and add rtc0 count ,update the timing and write back to flash. if it wake by rtc0, Then the system go into system off .

Can you give a hint about every steps of RTC calendar?

[Håkon Alseth]

Hi Steven,

This can be achieved by using the app_timer library. If you have alook at any of the ble-examples, all of these use the app_timer library. What you need to adjust is this define: #define APP_TIMER_MAX_TIMERS

This define must be equal or greater to the amount of times "app_timer_create" function is called. If this is not done, the library will not allocate the sufficient amount of RAM to run the added timer function. You create like this: app_timer_create(&m_my_timer_id, APP_TIMER_MODE_REPEATED, my_timeout_handler);

my_timeout_handler is your RTC timer function which is called based on the interval that you set when starting this.

You start the timer by running this function: app_timer_start(m_my_timer_id, INTERVAL, NULL);

For storing information to flash, you can use one of these libraries:

• ble_flash
• nrf_nvmc

Best regards Håkon

[cocoa]

Hi Håkon, seizing upon the answer, I would ask you how exactly is , in APP_TIMER_INIT macro, the OP_QUEUES_SIZE parameter. Is a timer operation like a ObjC block passed to a thread ? How can I set the right size for it ? Can you show me an example ? (best if with and without Scheduler)

Thank you.

-cocoa

[Håkon Alseth]

Hi,

First of I have to say that I have no experience with objc (I'm more of a firmware guy), so I cannot comment on that.

Most of the ble_* examples uses app_timer, mostly without scheduler. "ble_app_template" uses the scheduler, and is more or less a empty shell. Look at that project, and how HRM sets it up to see the difference.

The "OP_QUEUE_SIZE" defines how many operations you can have queued. Lets say you have a situation where you get events are are queueing up (starting a one-time timer) then this define says how many you can have queued before corruption will happen.

BR Håkon

[Håkon Alseth]

Forgot to mention; The latter define is application specific and based on the timing of all of your running tasks, and if you are using scheduler or not. You will have to run tests and see what number works for your application

-H

[cocoa]

Thank you, but I've not so sure to have understood . Supposing that there are ten events that want to start a timer , OP_QUEUES_SIZE = 10, MAZ_TIMER= 1, softdevice will store all events in a queue, but if the events will be 11, the queue will be corrupted ? (Will be raised an exception or an assert?) Again, with a max timer = 10 and a queue = 11, the 12th event will raise a corruption if all 10 timers are working and nobody of them can accept the 12th event ?