Multi advertising non connectable and connectable are blocking CPU on nrf52840

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Catalin — Thu, 04 Jul 2019 08:07:21 GMT

Hi,

We manage to work around this delay but again we hit and we need to resolve this, since we updated to nRF Mesh 3.1 and SDK 15.3

Here are the interrupt priority registers.

Timer1 has interrupt priority 1 and at each 415 us it toggles a pin. As you can see in the first message there are gaps that are around 15ms in toggling.

The problem as we talked is due to coexistence of SDK BLE and Mesh in the situation that they are both advertising.

Thanks,

Catalin

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Mttrinh — Mon, 10 Sep 2018 12:23:31 GMT

I have a couple of suggestions that you can try out and see if that solves your problem:

- It might be an irq priority issue, check out this.

- This might also help, Coexistence with nRF5 SDK BLE functionality.

- There is a new Mesh SDK out, v2.2.0. Try the coexistence example and see if it changes anything.

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Mttrinh — Fri, 07 Sep 2018 14:39:26 GMT

Hi,

Sorry for the late repsonse.

I have been sick and haven't been able to look further into the issue. I will have a look at it on Monday.

Sorry for the inconvenience.

Best Regards,

Martin

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Catalin — Thu, 30 Aug 2018 10:58:55 GMT

Hi,

I do not have any progress!

I have TIMER1 interrupt at 415us that is toggling a pin and this pin is monitored with a logic analyzer. And as you can see in the screen shots posted first time the interrupt is masked for too long. I do not have any other code just the 2 advertisings with GATT Softdevice (using ble_advertising.c module) and with Mesh.

/Catalin

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Mttrinh — Thu, 30 Aug 2018 10:39:47 GMT

Hi,

Have you had any progress with the issue?

How do you check that the CPU is blocked?

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Catalin — Mon, 27 Aug 2018 11:33:52 GMT

Hi Martin,

I have tried a few advertising connectable solutions, even the one from the proxy. In the attachment you can see the lastest inspired from the coexist examples available in NRF Mesh SDK 2.1.1,

/*
 * advert.c
 *
 *  Created on: Aug 24, 2018
 *      Author: Cata
 */

//#include "ble_advdata.h"
#include "ble_advertising.h"
#include "mesh_adv.h"
#include "timer_scheduler.h"
#include "gatt_util.h"
#include "dara.h"
#include "utils.h"

#include "nrf_sdh_ble.h"
#include "nrf_sdh_soc.h"

#include "log.h"

#define MESH_ADV_ADV_TYPE 					BLE_GAP_ADV_TYPE_CONNECTABLE_SCANNABLE_UNDIRECTED
#define MESH_ADV_DATA_SIZE_MAX 				BLE_GAP_ADV_SET_DATA_SIZE_MAX
#define ADV_NETWORK_ITERATE_INTERVAL_US     SEC_TO_US(10)

#define MIN_CONN_INTERVAL               MSEC_TO_UNITS(500, UNIT_1_25_MS)        /**< Minimum acceptable connection interval (0.5 seconds).  */
#define MAX_CONN_INTERVAL               MSEC_TO_UNITS(1000, UNIT_1_25_MS)       /**< Maximum acceptable connection interval (1 second). */
#define SLAVE_LATENCY                   0                                       /**< Slave latency. */
#define CONN_SUP_TIMEOUT                MSEC_TO_UNITS(4000, UNIT_10_MS)         /**< Connection supervisory timeout (4 seconds). */

#define APP_ADV_INTERVAL                800                                     /**< The advertising interval (in units of 0.625 ms. This value corresponds to 500 ms). */
#define APP_ADV_DURATION                BLE_GAP_ADV_TIMEOUT_GENERAL_UNLIMITED   /**< Disable advertising timeout. */

//#define APP_ADV_INTERVAL                	391                                     /**< The advertising interval (in units of 0.625 ms; this value corresponds to 40 ms). */
//#define APP_ADV_DURATION                	BLE_GAP_ADV_TIMEOUT_GENERAL_UNLIMITED   /**< The advertising time-out (in units of seconds). When set to 0, we will never time out. */

extern st_Dara_t g_stDara;
extern ble_util_t m_util;

BLE_ADVERTISING_DEF(m_advertising);                     /**< Advertising module instance. */

/**@brief Function for handling advertising events.
 *
 * @param[in] ble_adv_evt  Advertising event.
 */
static void on_adv_evt(ble_adv_evt_t ble_adv_evt)
{
    ret_code_t err_code;

    switch (ble_adv_evt)
    {
        case BLE_ADV_EVT_FAST:
            break; // BLE_ADV_EVT_FAST

        case BLE_ADV_EVT_IDLE:
            break; // BLE_ADV_EVT_IDLE

        default:
            break;
    }
}

void advertising_init(void)
{
	ret_code_t             err_code;
	ble_advertising_init_t init;
    ble_advdata_t srdata;
    ble_advdata_manuf_data_t manufdata;
    ble_gap_addr_t addr;

    uint8_t mandata[6] = {0, 0, 0, 0, 0, 0};
    ble_uuid_t m_adv_uuids[] = {{UTIL_UUID_SERVICE, m_util.uuid_type}};

	memset(&init, 0, sizeof(init));

 	memset(&init.srdata, 0, sizeof(init.srdata));
 	init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
 	init.srdata.uuids_complete.p_uuids  = m_adv_uuids;

	init.advdata.name_type               = BLE_ADVDATA_SHORT_NAME;
	init.advdata.short_name_len     = 4;

	//init.advdata.include_appearance      = false;
	//init.advdata.flags                   = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;
	//init.advdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
	//init.advdata.uuids_complete.p_uuids  = m_adv_uuids;

	init.advdata.p_manuf_specific_data = &manufdata;

    manufdata.company_identifier = ACCESS_COMPANY_ID_DARA;
    manufdata.data.size = 6;

	g_stDara.m_uiNodeid = (uint16_t)((*(uint32_t*) &NRF_FICR->DEVICEID[0]) & 0x3FFF);
    mandata[4] = g_stDara.m_uiNodeid;
    mandata[5] = (uint8_t)(g_stDara.m_uiNodeid >> 8);

	manufdata.data.p_data =  mandata;

	init.config.ble_adv_fast_enabled  = true;
	init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
	init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;

	init.evt_handler = on_adv_evt;

	err_code = ble_advertising_init(&m_advertising, &init);
	APP_ERROR_CHECK(err_code);

	ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

/**@brief Function for starting advertising.
 */
void advertising_start(bool erase_bonds)
{
    uint32_t err_code = ble_advertising_start(&m_advertising, BLE_ADV_MODE_FAST);
}

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Mttrinh — Fri, 24 Aug 2018 13:42:33 GMT

Hi,

How are you using both Mesh and connectable advertising for GATT connections at the same time? Are you using the timeslot API?

If TIMESLOT_REQ_EARLIEST_TIMEOUT_US matches the blocked interval, I suspect that the request of the earliest timeslot isn't handled somewhere in your application. Can you see if this is the case?

Also which Mesh example are you running?

Best Regards,

Martin

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Catalin — Wed, 22 Aug 2018 15:35:50 GMT

Hi Martin,

The blocking interval and the TIMESLOT_REQ_EARLIEST_TIMEOUT_US (mesh-SDK/mesh/core/src/timeslot.c) definition (15ms) are in directed connection. Setting the TIMESLOT_REQ_EARLIEST_TIMEOUT_US to a different value the blocking interval goes to that defined value.

Can you give me some hints regarding of what is happening in this timeslot and why the mesh without the gatt advertising does not get this blocking CPU period?

Our custom advertising is connectable and it has

#define APP_ADV_INTERVAL 400
#define APP_ADV_DURATION BLE_GAP_ADV_TIMEOUT_GENERAL_UNLIMITED

Thanks,

Catalin

RE: Multi advertising non connectable and connectable are blocking CPU on nrf52840

Mttrinh — Wed, 22 Aug 2018 10:51:01 GMT

Hi,

It seems high with 15.3ms. I'm not sure what is causing this, but you can start by debugging the code and see where it hangs?

Best Regards,

Martin