Custom board issue

RE: Custom board issue

FormerMember — Thu, 07 Apr 2016 11:17:12 GMT

sd_softdevice_enable(..) will hang if there is a problem with the low frequency clock source. Could you try to configure the lfclk with the example from the S13x migration document, and check if it works?

// Example configuration equivalent to the old NRF_CLOCK_LFCLKSRC_RC_250_PPM_TEMP_1000MS_CALIBRATION:

nrf_clock_lf_cfg_t rc_cfg = {
.source = NRF_CLOCK_LF_SRC_RC,
.rc_ctiv = 4, // Check temperature every 4 * 250ms
.rc_temp_ctiv = 1, // Only calibrate if temperature has changed.
};

RE: Custom board issue

Juba Belgaid — Wed, 06 Apr 2016 09:23:16 GMT

i am using sdk Ble Uart

RE: Custom board issue

FormerMember — Wed, 06 Apr 2016 09:15:36 GMT

Do you use one of the SDK examples? If not, could you test with an SDK example?

RE: Custom board issue

Juba Belgaid — Mon, 04 Apr 2016 16:04:55 GMT

Now, i have issue when i try enabling soft device.

sd_softdevice_enable(p_clock_lf_cfg, softdevice_fault_handler);

never returns.

I need help please.

RE: Custom board issue

Juba Belgaid — Thu, 31 Mar 2016 13:45:29 GMT

I have used the programm found here and solved my issue. it calibrate the internal HFCLK

Thank you for your help

RE: Custom board issue

Juba Belgaid — Thu, 31 Mar 2016 12:09:20 GMT

So I didn't use external HFCLK

RE: Custom board issue

Juba Belgaid — Thu, 31 Mar 2016 11:17:47 GMT

I get HFCLKSTAT = 0x00010000

SRC 0 :RC = 64MHz internal oscillator (HFINT)

STATE 1: Running = HFCLK running

RE: Custom board issue

RK — Thu, 31 Mar 2016 10:53:32 GMT

Look in section 19.3 of the manual. You start it with the TASKS_HFCLKSTART, know when it's started with the EVENTS_HFCLKSTARTED and you can check the status in the HFCLKSTAT register.

RE: Custom board issue

Juba Belgaid — Thu, 31 Mar 2016 10:51:07 GMT

How can i read the CLOCK register?

How explicitly start the HF oscillator ?

RE: Custom board issue

RK — Thu, 31 Mar 2016 10:32:12 GMT

Actually that's a very good question because .. I assumed the 32MHz crystal oscillator was running but looking at the code, unless the app_simple_timer.. starts it, it may actually not be at all and you are already getting the internal 64MHz RC oscillator (it's 64MHz on the nrf52).

So perhaps you want to explicitly start the HF oscillator and wait for it to start, to ensure you are using the crystal and not the internal RC. You can also break in the code and check the CLOCK register to see if it says the HF oscillator is running.

The internal RC has a tolerance of 6% max, so you shouldn't get anything worse than 18.5us even if it's at the edge of the range.

So perhaps I got it the wrong way around, and you need to force the HF crystal oscillator ON in your test

RE: Custom board issue

Juba Belgaid — Thu, 31 Mar 2016 10:19:01 GMT

Hi,

Thank you for reply. I will check this. How can i use Internal 16 MHz RC oscillator ?

RE: Custom board issue

RK — Thu, 31 Mar 2016 10:07:11 GMT

I would say most likely your crystal isn't running at 32MHz but something faster, which would usually suggest increasing the load capacitors. Did you use the same 9pF crystal as the development board, if you used something higher, that would need correspondingly higher load capacitors. eg if the crystal is a 12pF one, you'd need capacitors more like 20pF than 12pF.

Are you sure the correct capacitors were installed?