Migrating SDK 6.1 - SDK 10

Question

I just needed some clarification as I'm migrating from SDK 6.1 to SDK10: 
 
 
 app_button: There's no way to have the Button function thru the Scheduler anymore. I would have in effect have to write my own app_button_with_scheduler module 
 
 
 If I handle app_button events as is (GPIOTE interrupt context), it is safe to start app_timers within the event_handler? 
 
 
 With the new file structure I cannot find any implemented use of the examples config/nrf_drv_config.h? I understand what the code means in these files, but I don't see where it is ever used. My applications use of TIMERs was always handled in the context in which it was used: SPI Master, External interrupt (GPIOTE), custom PWM code, ADC, Temperature. So I don't feel like I would need the nrf_drv_config.h in my project, unless it serves a purpose I don't see? Please advise. 
 
 
 Since Nordic has differentiate the modules, now I would have to use app_timer_appsh if I want to have my app_timers use the Scheduler. Correct? 
 
 
 Just as a comment: The old SDK online documentation (6.1) was much much easy to browse through. Also searching was much easier then the new infocenter version. I cannot search for anything only within a specific SDK. i.e. search for app_timer only in SDK 10. 
 
 
 Thanks in advanced for your advisement on these issues. 
 -DC

Stefan Birnir Sverrisson · Accepted Answer

Hi Dave 
 
 The option of letting the app_button call the scheduler was apparently removed in nRF51 SDK 8.0.0. I am not sure for the reason for it, but if you still want to use scheduler for app_button, you should need to add that functionality manually. 
 
 In fact, the app_button handler is not executed in app_gpiote interrupt context. What happens is the following: 
 
 App_button is initialized and registers gpiote user and callback, creates app_timer and callback 
 When button is pushed, the APP_IRQ_PRIORITY_HIGH app_gpiote handler is executed which starts an app_timer. 
 When the app_timer expires, APP_IRQ_PRIORITY_LOW interrupt handler is executed which calls app_button interrupt handler. If scheduler was chosen when initializing the app_timer library, the app_button is also called with in main context. So it seems you control the context of the app_button handler by choosing to use scheduler or not for app_timer. 
 
 
 
 I see no problem in starting a timer in app_button handler 
 
 
 I would recommend to use the drivers and the nrf_drv_config.h driver configuration file for SDK 10.0.0. All implementation is tailored around the drivers and I find it much easier to use them for SDK 8.0.0+. All peripheral examples in SDK 10.0.0 should use the peripheral drivers, e.g. spi_master, uart, etc. You can not use the peripherals unless you enable them in nrf_drv_config.h

Migrating SDK 6.1 -> SDK 10