Hi,
1. In my last post, (https://devzone.nordicsemi.com/f/nordic-q-a/60300/questions-on-usbd_cdc_acm-example), in question #1 a nice explanation was given regarding the use of nrf_drv_clock.h in the usbd_cdc_acm example. In the usbd_ble_uart example though, the app_timer handles the low_frequency clock for the softdevice, so, why can't we use a second instance of app_timer for the usbd library to work and we have to add nrf_drv_clock_init()? Because if I undrstand correctly the app_timer will not stop if at least one instance of it is using it. Right?
2. I am confused with the purpose of the different timer and clock libraries and drivers in the SDK
I found this post ( https://devzone.nordicsemi.com/f/nordic-q-a/10952/timer-vs-app_timer/40933#40933) that clears out the relation between app_timer library and timer driver. But there are other drivers / libraries that I cannot understand their purpose and how/if they relate to each other.
For example,
- app_timer.h
- nrf_drv_clock.h
- nrf_drv_timer.h
Could you please give me a guideline or indicate me some post that explains the timer and clock drivers and libraries and how they relate (or not) to each other
Thank you for your time!