You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2022/03/17 05:08:02 UTC

[GitHub] [mynewt-nimble] StarGate01 commented on issue #1207: NRF52: Use with MCU_LFCLK_SOURCE: LFRC

StarGate01 commented on issue #1207:
URL: https://github.com/apache/mynewt-nimble/issues/1207#issuecomment-1070331296


   Thank you for the help. I configured the ppm parameter to be 500, and implemented a simple calibration loop:
   
   ```
   void calibrate_loop(nrf_drv_clock_evt_type_t event) {
     // 16 * 0.25s = 4s calibration cycle
     nrf_drv_clock_calibration_start(16, calibrate_loop);
   }
   ...
   nrf_drv_clock_lfclk_request(NULL);
   nrfx_clock_lfclk_start();
   #if(CLOCK_CONFIG_LF_SRC == NRF_CLOCK_LFCLK_RC)
       nrf_drv_clock_calibration_start(0, calibrate_loop);
   #endif
   ```
   I have confirmed the LFRC clock to be running by inspecting the registers, and the Nimble BLE link layer seems to be receiving IRQ events from the LPRC associated RTC0 (I think TIMER5 is used) as well.
   
   However, connecting via Bluetooth still fails. Are there any other options I have to configure? Is it possible to somehow validate or debug the timing requirements? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@mynewt.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org