This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Where to define NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM

Dear every body,

some days before, i raise an issue relate my fault at here: https://devzone.nordicsemi.com/f/nordic-q-a/68010/nrf52810-issue-with-32mhz-external-clock

During waiting for some recommend, i check more by myself on devzone.

And i see that my issue relate to external clock but not HFXO(32Mhz).

It may be is LFXO(32Khz).

I make the board base on NRF52810 chip set and SDK 17.

My board working normal for radiation(range connection distance is ok 25-30m).

But i have issue, when connect with NRF Blinky app on Iphone it time out after 5-7 seconds as image on top.

I also check with NRF Connect on desktop it time out by:

BLE_HCI_CONNECTION_TIMEOUT

And here is thread can be fix this issue

https://devzone.nordicsemi.com/f/nordic-q-a/29786/ble_hci_connection_timeout-and-nrf_clock_lf_xtal_accuracy_xx_ppm

But i can't fine where to define NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM to NRF_CLOCK_LF_XTAL_ACCURACY_500_PPM on SDK17

Could you please help me??

Thank so much!!

Parents
  • Hello,

    The clock accuracy can be adjusted in the sdk_config.h header through the NRF_SDH_CLOCK_LF_ACCURACY option.  As you can see from the code comments, 'NRF_SDH_CLOCK_LF_ACCURACY 1' translates to NRF_CLOCK_LF_ACCURACY_500_PPM

    Best regards,

    Vidar

  • thank you Mr Vidar Berg.

    I check as your suggestion and find that on new SDK17 it rename to NRF_CLOCK_LF_ACCURACY_***

    // <0=> NRF_CLOCK_LF_ACCURACY_250_PPM
    // <1=> NRF_CLOCK_LF_ACCURACY_500_PPM
    // <2=> NRF_CLOCK_LF_ACCURACY_150_PPM
    // <3=> NRF_CLOCK_LF_ACCURACY_100_PPM
    // <4=> NRF_CLOCK_LF_ACCURACY_75_PPM
    // <5=> NRF_CLOCK_LF_ACCURACY_50_PPM
    // <6=> NRF_CLOCK_LF_ACCURACY_30_PPM
    // <7=> NRF_CLOCK_LF_ACCURACY_20_PPM
    // <8=> NRF_CLOCK_LF_ACCURACY_10_PPM
    // <9=> NRF_CLOCK_LF_ACCURACY_5_PPM
    // <10=> NRF_CLOCK_LF_ACCURACY_2_PPM
    // <11=> NRF_CLOCK_LF_ACCURACY_1_PPM

    #ifndef NRF_SDH_CLOCK_LF_ACCURACY
    #define NRF_SDH_CLOCK_LF_ACCURACY 7
    #endif

    I will check range from 0 to 11  on Monday when i comeback office Slight smile

    Have good time at weekend!!

Reply
  • thank you Mr Vidar Berg.

    I check as your suggestion and find that on new SDK17 it rename to NRF_CLOCK_LF_ACCURACY_***

    // <0=> NRF_CLOCK_LF_ACCURACY_250_PPM
    // <1=> NRF_CLOCK_LF_ACCURACY_500_PPM
    // <2=> NRF_CLOCK_LF_ACCURACY_150_PPM
    // <3=> NRF_CLOCK_LF_ACCURACY_100_PPM
    // <4=> NRF_CLOCK_LF_ACCURACY_75_PPM
    // <5=> NRF_CLOCK_LF_ACCURACY_50_PPM
    // <6=> NRF_CLOCK_LF_ACCURACY_30_PPM
    // <7=> NRF_CLOCK_LF_ACCURACY_20_PPM
    // <8=> NRF_CLOCK_LF_ACCURACY_10_PPM
    // <9=> NRF_CLOCK_LF_ACCURACY_5_PPM
    // <10=> NRF_CLOCK_LF_ACCURACY_2_PPM
    // <11=> NRF_CLOCK_LF_ACCURACY_1_PPM

    #ifndef NRF_SDH_CLOCK_LF_ACCURACY
    #define NRF_SDH_CLOCK_LF_ACCURACY 7
    #endif

    I will check range from 0 to 11  on Monday when i comeback office Slight smile

    Have good time at weekend!!

Children
No Data
Related