Migration from SDK 11 alpha to 11 final, advertising problem

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Tue, 28 Jun 2016 19:28:02 GMT

Have you checked the return code ?

RE: Migration from SDK 11 alpha to 11 final, advertising problem

kevray — Fri, 24 Jun 2016 13:58:23 GMT

Have not. Only moved it. Calling TIMER2 (systick_init) prior to ble_init() or calling systick_init() immediately after ble_init() and there is no BLE Advertising. Removing the call to systick_init() or adding a delay of 50ms following ble_init() and BLE Advertising works, a connection can be made, and then disconnect occurs within 3 seconds.

This is code that has worked flawlessly for several months. Only started getting wonky with the update from SDK9 -> SDK11 and s130 v2.0.1. No hardware change. nRF51822 xxAC with LFCLKSRC = RC.

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Fri, 24 Jun 2016 08:22:41 GMT

Hello Kevray, did you fixed it ?

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 22 Jun 2016 11:57:25 GMT

Hello, i fixed it but i don't remember exactly how (too much things since). Can you check the return code value for ble_advertising_start ? If i am right it was returning NRF_ERROR_INVALID_STATE if called too soon, i had to retry later until it was ok.

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Ole Bauck — Wed, 22 Jun 2016 11:00:29 GMT

I don't think so. What version of the chip are you using? Check the markings on the chip with this or this table.

RE: Migration from SDK 11 alpha to 11 final, advertising problem

kevray — Tue, 21 Jun 2016 19:45:41 GMT

Was a solution to this ever found? We're experiencing the same issue after upgrading to SDK11.

RE: Migration from SDK 11 alpha to 11 final, advertising problem

RK — Thu, 17 Mar 2016 00:53:51 GMT

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.

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 16 Mar 2016 17:18:48 GMT

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

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 16 Mar 2016 17:17:42 GMT

static nrf_clock_lf_cfg_t CLOCK_CFG =

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

RE: Migration from SDK 11 alpha to 11 final, advertising problem

RK — Wed, 16 Mar 2016 15:06:58 GMT

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

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 16 Mar 2016 13:56:26 GMT

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 ?)

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 16 Mar 2016 09:01:44 GMT

for APP, on_adv_evt is just called once then nothing

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 16 Mar 2016 08:45:10 GMT

i did tome history digging and tests about if advertising is operational.

                             BL             APP
SDK 9, nRF51                 OK             OK
SDK 11 alpha 2, nRF52        OK             KO
SDK 11 final, nRF52          KO             KO

RE: Migration from SDK 11 alpha to 11 final, advertising problem

RK — Wed, 16 Mar 2016 08:28:12 GMT

its' the LF RC clock I'm using - I don't have a crystal on this board

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 16 Mar 2016 08:27:44 GMT

and yes, SD is programmed (i checked if file is the good one and i use verify after programming).

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Wed, 16 Mar 2016 08:26:35 GMT

@RK could you try with RC LF clock please ?

#define NRF_CLOCK_LFCLKSRC      {.source        =  NRF_CLOCK_LF_SRC_RC,            \
                                 .rc_ctiv       = 4,                                \
                                .rc_temp_ctiv  = 1,                            \
                                 }

RE: Migration from SDK 11 alpha to 11 final, advertising problem

RK — Tue, 15 Mar 2016 14:04:39 GMT

Mine works fine. I recompiled for 11 final when it came out, removed all the bits of code I'd ported whilst waiting to migrate to SD 132V2 and reverted to the ones in the final SDK release which are now updated, worked first time. S130 worked on my nRF51s as well. Sure you have the release softdevice programmed?

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Tue, 15 Mar 2016 13:50:53 GMT

Ok but before could you just test if bootloader is advertising on an nRF52 rev C. (i have few modifications in bootloader and it works with 11 alpha but not with 11 final)

RE: Migration from SDK 11 alpha to 11 final, advertising problem

FormerMember — Tue, 15 Mar 2016 13:48:03 GMT

Could you create a new support case in myPage from https://www.nordicsemi.com, upload your code there, and refer to this thread? By doing so, I will be able to test your code without sharing it here.

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Tue, 15 Mar 2016 13:43:17 GMT

that's for application (bootloader don't use ble_advertising.c)

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Tue, 15 Mar 2016 13:42:04 GMT

ble_advertising_init => OK ble_advertising_start => NRF_SUCCESS

RE: Migration from SDK 11 alpha to 11 final, advertising problem

FormerMember — Tue, 15 Mar 2016 13:41:43 GMT

And advertising_start(..) doesn't return any error?

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Tue, 15 Mar 2016 13:38:57 GMT

Yes i can, i did it and no found fail...

RE: Migration from SDK 11 alpha to 11 final, advertising problem

FormerMember — Tue, 15 Mar 2016 13:35:21 GMT

Could you run the chip in debug mode and check where in the code it fails?

It can also be useful to take a look at the migration document that comes with the S130 v. 2.0.0 softdevice. It describes migration from S130 v.1.0.0, but it may still be worth taking a look.

RE: Migration from SDK 11 alpha to 11 final, advertising problem

Fabien Comte — Tue, 15 Mar 2016 13:21:46 GMT

Confirmed bootloader works with 11 alpha. Detail i run with NRF_CLOCK_LF_SRC_RC. And power consumption is divided by 2.5 Under bootloader with 11 final.