• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 11 replies
  • Subscribers 64 subscribers
  • Views 5185 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 123651
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

lfclk, rtc issue on SDK13

fteng

I am trying to set up RTC2 by following an example github.com/.../saadc_low_power I ported it to my project which is running a softdevice on nRF52. It works perfectly fine on SDK11 but has problems on SDK13.0 / 13.1. Seems like nrf_drv_clock_init() or nrf_drv_rtc_init() has conflict with the BLE stack. Any idea what has changed from SDK11 to SDK13?

Parents
  • 0

    Thx, Jørgen. I used the method to check the error code. It is 0x1001 = NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION in function ble_stack_init() --> SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL); clock_lf_cfg is from NRF_CLOCK_LFCLKSRC -- default setting in pca10040.h I develop this on an nRF52 base Murata (which I work for) module and I have to port the project to eclipse/GCC due to code size limit in Keil. It doesn't look like a hardware or toolchain issue to me though, since SDK11 works fine on the same platform. Seems like softdevice in SDK13 takes over RTC and application can't access it anymore.

Reply
  • 0

    Thx, Jørgen. I used the method to check the error code. It is 0x1001 = NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION in function ble_stack_init() --> SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL); clock_lf_cfg is from NRF_CLOCK_LFCLKSRC -- default setting in pca10040.h I develop this on an nRF52 base Murata (which I work for) module and I have to port the project to eclipse/GCC due to code size limit in Keil. It doesn't look like a hardware or toolchain issue to me though, since SDK11 works fine on the same platform. Seems like softdevice in SDK13 takes over RTC and application can't access it anymore.

Children
No Data
Related