Migration from SDK 11 alpha to 11 final, advertising problem

[Fabien Comte]

Hello,

This morning i did migration of my code from SDK 11 alpha 2 to 11 final on nRF52 and i have a big problem.

Nor bootloader or application do advertising. Am I alone ?

(i possibly not checked bootloader in 11 alpha but it worked with SDK 9 on nRF51)

What can I do as test ?

[Fabien Comte]

I found.

Very strange but HF Crystal don't start with 11 final.

If i use NRF_CLOCK_LF_SRC_SYNTH in place of NRF_CLOCK_LF_SRC_RC, it works !!!

Question does NRF_CLOCK_LF_SRC_SYNTH need parameters (PPM ?)

[RK]

Do you mean that or do you mean does NRF_CLOCK_LF_SRC_RC need parameters? You say it works with SYNTH but not LF

here's min

static 	nrf_clock_lf_cfg_t CLOCK_CFG = 
{
    .source = NRF_CLOCK_LF_SRC_RC
    .rc_ctiv = 4,      // Check temperature every 4 * 250ms
    .rc_temp_ctiv = 0, // Always calibrate
    .xtal_accuracy = 0
};

that works fine for me under SD132v2 and SD130v2

[Fabien Comte]

static nrf_clock_lf_cfg_t CLOCK_CFG =

    {
        .source = NRF_CLOCK_LF_SRC_SYNTH
        .xtal_accuracy = xx // what tu use here as xx
    };

[Fabien Comte]

i have not set .xtal_accuracy = 0 in structure for RC, i will test

[RK]

I usually use C++ and if you turn warnings up you get a useful warning about uninitialised struct members and I turned on the equivalent for C too, not that I remember what it is. It's a bit annoying sometimes but can be rather useful. I would think however that field is ignored totally in the RC case. I don't really understand where your problem likely lies, the bootloader isn't special, it's just another BLE service which runs out of a different piece of flash, if BLE works in general on that device with the S132 softdevice, there's no particular reason the bootloader wouldn't.

You could try sticking a breakpoint in the softdevice fault handler, see if it's going there (as opposed to the usual error handler) although I'd think you'd notice.