Developing with BL652 -- Not advertising after successful BLE example download

RE: Developing with BL652 -- Not advertising after successful BLE example download

Liam — Thu, 07 Jun 2018 16:47:11 GMT

I just got it! My problem had been, when I was flashing the soft device I was using the "Soft Device Erase" programming algorithm, and then switching to the nrf52xxx algorithm for loading code. Just using the nrf52xxx for both did the trick. Thanks to everyone for your prompt replies and help with this.

RE: Developing with BL652 -- Not advertising after successful BLE example download

Liam — Thu, 07 Jun 2018 15:44:24 GMT

Depending on the SDK version I am using, I believe this may be found in the nrf_sdh.c, per https://assets.lairdtech.com/home/brandworld/files/Using%20the%20DVK-BL652%20and%20Nordic%20SDK%20v14.0.0%20with%20Eclipse%20and%20GCC%20v1_0.pdf, but it still has no effect on the problem, when I change it per that doc.

RE: Developing with BL652 -- Not advertising after successful BLE example download

Liam — Thu, 07 Jun 2018 01:42:06 GMT

I changed this in the pca10040.h file, but am still having the described problem.

RE: Developing with BL652 -- Not advertising after successful BLE example download

Liam — Thu, 07 Jun 2018 01:40:26 GMT

I have huge trouble doing this for some reason. When I attempt to flash with OpenOCD I get "image.base_address option value ('EclipseOpenOCD') is not valid" errors.

Looking at this post: https://devzone.nordicsemi.com/b/blog/posts/flashing-softdevice-directly-from-arm-keil-uvision

Is this still valid? Keil flashed successfully using the same debug settings for both, but I still get no indication of advertisement.

RE: Developing with BL652 -- Not advertising after successful BLE example download

Andre — Wed, 06 Jun 2018 19:26:00 GMT

Before flashing the application from the nordic sdk, you'll need to flash the softdevice.

This can be done with OpenOCD, something like

openocd -f "interface/stlink.cfg" -f "target/nrf52.cfg" -c "init" -c "halt" -c "nrf5 mass_erase 0" -c "program /path/to/softdevice.hex" -c "exit"

Please note you'll need a build of the git version of OpenOCD. The latest release version (0.10) still lacks support for nRF52 flashing.

RE: Developing with BL652 -- Not advertising after successful BLE example download

Richard D. — Wed, 06 Jun 2018 18:55:22 GMT

The BL652 uses a different low frequency clock source than the Nordic dev kit. In main.c, ble_stack_init you'll see something like

    nrf_clock_lf_cfg_t clock_lf_cfg = NRF_CLOCK_LFCLKSRC;

    // Initialize SoftDevice.
    SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL);

and in one of the headers

#define NRF_CLOCK_LFCLKSRC      {.source        = NRF_CLOCK_LF_SRC_XTAL,            \
                                 .rc_ctiv       = 0,                                \
                                 .rc_temp_ctiv  = 0,                                \
                                 .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_20_PPM}

For BL652, you need to set .source = NRF_CLOCK_LF_SRC_RC instead