Hung up on advertising

RE: Hung up on advertising

Petter Myhre — Tue, 04 Aug 2015 07:49:14 GMT

Great! Could you maybe add an answer describing how you got it working?

RE: Hung up on advertising

Lee Daniel Crocker — Mon, 03 Aug 2015 18:19:14 GMT

Just FYI, I finally got it working with SDK 8.1 / SD 7.30. If I discover anything more, I'll let you know.

RE: Hung up on advertising

Petter Myhre — Fri, 31 Jul 2015 21:14:25 GMT

If you don't have a 32 kHz crystal you can't use NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, you need to tell the SoftDevice to use the 250 ppm RC oscillator.

RE: Hung up on advertising

Lee Daniel Crocker — Fri, 31 Jul 2015 16:16:22 GMT

Thanks. The crystal on the board is a 16MHz NX2520SA. I'll try moving back one SD level to see if that changes anything.

RE: Hung up on advertising

Petter Myhre — Fri, 31 Jul 2015 08:01:31 GMT

You can find CEAA in the Packet/Variant column in Table 2. You have a revision 2 WLCSP. By looking at Table 4 you can see that it is compatible with SoftDevice S110 8.0.0, if you enable mutual exclusion. The release notes are included in the zip together with the S110 hex file. SDKs after 6.1.0 haven't been tested on revision 2 chips, but this doesn't mean that it doesn't work, just that it is not testet. SDK 9.0.0 should be added to the matrix, I agree. It is not too new and buggy, most of what is included is the same as in SDK 8.0.0, with some added bugfixes/examples/libraries. Do you have an external 32 kHz crystal on your board? Since you initializing with the SoftDevice NRF_CLOCK_LFCLKSRC_XTAL_20_PPM?

RE: Hung up on advertising

Lee Daniel Crocker — Thu, 30 Jul 2015 20:52:17 GMT

Our BOM says "NRF51822-CEAA-R" Don't know how that translates into your "rev number". The compatibility matrix seems out of date--has no SDK 9 in it at all. Perhaps it's just too knew and buggy, and I should try downgrading a bit rather than trying the bleeding edge. The above code made no difference in my device. Also, I can find SD 8.0.0 docs and specification but not the "release notes" you speak of.

RE: Hung up on advertising

Petter Myhre — Thu, 30 Jul 2015 09:17:51 GMT

If you use SoftDevice S110 8.0.0 with a revision 2 chip you should enable mutual exclusion between the radio and the application. Please see the Changes section in the S110 8.0.0 release notes for more information.

uint32_t opt_id = BLE_COMMON_OPT_RADIO_CPU_MUTEX;
ble_opt_t cpu_blocking_enabled;
cpu_blocking_enabled.common_opt.radio_cpu_mutex.enable = 1;
ble_stack_init();
err_code = sd_ble_opt_set(opt_id, &cpu_blocking_enabled);

RE: Hung up on advertising

Petter Myhre — Thu, 30 Jul 2015 09:17:44 GMT

I'm sorry, I just assumed you had testet the unmodified example first. Are you using a custom board or PCA10001? Either way it depends on what chip revision of the nRF51 you have on them. You need to compare the device markings of your chip/chips with Table 1 or Table 2 in the nRF51 Series Compatibility Matrix to figure out what revision you have. Then you check Table 4 to see what SoftDevices and SDKs that are compatible with your chips. I just tested SoftDevice s110 8.0.0 with an unmodified ble_app_hids_keyboard from SDK 9.0.0 on a nRF51422 revision 2 chip, and it advertises.

RE: Hung up on advertising

Lee Daniel Crocker — Wed, 29 Jul 2015 16:56:18 GMT

I have a PCA10001. Would it run on that?

RE: Hung up on advertising

Petter Myhre — Wed, 29 Jul 2015 16:50:39 GMT

But are you able to run ble_app_hids_keyboard?

RE: Hung up on advertising

Lee Daniel Crocker — Wed, 29 Jul 2015 16:16:19 GMT

This is a custom board. But the board does work with the older software (Softdevice 5.2.1, nRF SDK 4.4.3). Yes, app_hids_keyboard was a model (because it uses the scheduler, and app_uart because ble_nus is the only service I need/use). I'll keep looking...

RE: Hung up on advertising

Petter Myhre — Wed, 29 Jul 2015 12:10:57 GMT

I understand. Not really. But if the API doesn't return an error it should work, i.e. start advertising. I'm not sure how to help you. You application seem similar to the ble_app_hids_keyboard, so if I were you I would start with that, and try to compare what is different. Are you using a nRF51 DK?

RE: Hung up on advertising

Lee Daniel Crocker — Tue, 28 Jul 2015 16:18:30 GMT

I removed the extra pstorage_init(). I appreciate the generous offer, but I'd be more interested in learning how to debug this myself. I can add traces to the C code for most of the library, but the softdevice is a black box. It's not sending me any events, but is there any other way to probe its state, or otherwise peek under the hood?

static void softdevice_init(void) {
    SOFTDEVICE_HANDLER_APPSH_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, true);

    ble_enable_params_t ble_enable_params = {
        .gatts_enable_params = {
            .service_changed = IS_SRVC_CHANGED_CHARACT_PRESENT,
            .attr_tab_size = BLE_GATTS_ATTR_TAB_SIZE_DEFAULT
        },
    };
    uint32_t err_code = sd_ble_enable(&ble_enable_params);
    APP_ERROR_CHECK(err_code);

    err_code = softdevice_ble_evt_handler_set(ble_event_dispatch);
    APP_ERROR_CHECK(err_code);

    err_code = softdevice_sys_evt_handler_set(sys_event_dispatch);
    APP_ERROR_CHECK(err_code);
}

RE: Hung up on advertising

Petter Myhre — Tue, 28 Jul 2015 10:39:02 GMT

Are you initializing pstorage twice? There is a pstorage_init() in device_manager_init() as well. Shouldn't matter though. I can't see anything wrong with your code. Could you include your softdevice_init() as well? Or maybe just include your complete project so I can test it here? If it is secret you could also open a private case on your MyPage.

RE: Hung up on advertising

Lee Daniel Crocker — Mon, 27 Jul 2015 15:49:39 GMT

Yes, everything returns success. Here's my ble_stack_init:

void bluetooth_init(void) {
    softdevice_init(); // does SOFTDEVICE_HANDLER_APPSH_INIT
    sd_ble_gap_tx_power_set(4);
    pstorage_init();
    device_manager_init(true);

    gap_params_init();
    services_init();
    advertising_init(); // does ble_advertising_init()
    conn_params_init();
    radio_notification_init();
}

and main():

int main(void) {
    hardware_init();
    scheduler_init();
    timers_init();

    bluetooth_init();
    timers_start();
    advertise(); // does sd_ble_gap_adv_start()

    TRACE("main_loop_start");
    while (1) {
        app_sched_execute();
        power_manage(); // does sd_app_evt_wait()
    }
}

RE: Hung up on advertising

Petter Myhre — Mon, 27 Jul 2015 10:38:13 GMT

I assume sd_ble_gap_adv_start() returns NRF_SUCCESS (0x00000000)? Could you include your main()? and ble_stack_init()?

RE: Hung up on advertising

Lee Daniel Crocker — Fri, 24 Jul 2015 20:18:10 GMT

Installed Master Control Panel. Old code shows up, connects, shows GAP, GATT, and NUS services as expected. New code never shows up in list, so it doesn't seem to be broadcasting at all.

RE: Hung up on advertising

Lee Daniel Crocker — Fri, 24 Jul 2015 16:56:25 GMT

I was not using any 0 timeouts as far as I could tell. Another difference I noticed is that my code, along with most of the examples, used ble_advertising_start(), while my older working code used sd_ble_gap_adv_start(). So I switched. I'm now using:

ble_gap_adv_params_t adv_params = {
    .type = BLE_GAP_ADV_TYPE_ADV_IND,
    .p_peer_addr = NULL,
    .fp = BLE_GAP_ADV_FP_ANY,
    .interval = APP_ADV_INTERVAL,           // 64
    .timeout = APP_ADV_TIMEOUT_IN_SECONDS   // 180
};
uint32_t err_code = sd_ble_gap_adv_start(&adv_params);

I am not getting any events at all. My main loop is running, but neither my ble_evt_dispatch() nor my on_adv_evt() are getting anything at all.

I'm not sure how to test whether or not there's any actual advertising going on. I'm trying to connect with my Nexus7 tablet (Android 5.1) using the nRF UART app.

RE: Hung up on advertising

Ulrich Myhre — Fri, 24 Jul 2015 14:55:30 GMT

SDK 9.0 has this release note for a bugfix: "Advertising module can be set to infinite time-out." Additionally, they added the option to use low duty-cycle directed advertisement. The underlying BLE stack has always supported infinite advertising.

RE: Hung up on advertising

Petter Myhre — Fri, 24 Jul 2015 13:58:13 GMT

Are you seeing any advertising at all?

RE: Hung up on advertising

ahmad — Fri, 24 Jul 2015 04:57:48 GMT

You don't have the option of infinite advertising anymore. There is an interval for advertising and after that you receive a BLE_ADV_FAST or SLOW and advertising stops. In initializing the advertising, you can enable to have fast or slow or both of the advertisings. If you have both, after passing the fast advertising interval, the device switches to slow advertising and at the end of slow advertising stops advertising. I think the maximum interval for slow advertising should be around 4 hours and for the fast one, few minutes. If you want to advertise infinitely, you should start advertising again when you receive the BLE_ADV_FAST or SLOW events.