BLUETOOTH CONNECTION ISSUE

RE: BLUETOOTH CONNECTION ISSUE

Edvin — Tue, 14 Jul 2020 12:45:37 GMT

Glad to hear, Nandhu.

Please check this before creating a ticket the next time. It has been the solution to quite a few of your tickets so far. It would be quicker for you if you check this instead of waiting for our reply.

Best regards,

Edvin

RE: BLUETOOTH CONNECTION ISSUE

NANDHU — Tue, 14 Jul 2020 10:04:54 GMT

Hi Edvin,

[quote user="Edvin Holmseth"]I guess you already know all the tricks, but does the log say anything? It may be an APP_ERROR_CHECK(err_code) or a hardfault.[/quote]

Edvin you are absolutely right .The issue is due "APP_ERROR_CHECK(err_code)" .

If we call "ble_hids_inp_rep_send" while BLE events taking place this function will return error. we removed the APP_ERROR_CHECK(err_code) from there, now every thing is working fine without any timer delay.

Thanks a lot for your support.

RE: BLUETOOTH CONNECTION ISSUE

Edvin — Mon, 13 Jul 2020 13:02:15 GMT

Well, I assumed that the trace named PC_WITH_CONNECTION_ISSUE contained the issue. Apparently it did not.

So from the last sniffer trace, that actually shows the issue, you can see that the peripheral (nRF) stops responsing. There is your issue.

I guess you already know all the tricks, but does the log say anything? It may be an APP_ERROR_CHECK(err_code) or a hardfault.

Are you able to reproduce this while debugging? does the log say anything? Does the execution stop, or is the application still running?

Possibly right after you receive the encryption event.

BR,
Edvin

RE: BLUETOOTH CONNECTION ISSUE

NANDHU — Mon, 13 Jul 2020 09:19:53 GMT

Hi Edvin,

[quote user="Edvin Holmseth"]I have checked the sniffer trace. I can't see any obvious reasons for why the PC disconnects.[/quote]

I already told you that after we changed the timer interrupt delay to 5sec connection issue was not showing . Both the traces i posted to you have this change that is why you can't see any issue but did you notice the time difference to complete the BLE softdevice events(Service discovery, MTU update, data length update, PHY update, etc) in both trace.

If you want a sniffer trace with PC is disconnecting . Please refer the below trace (from number 2800).In this trace two times our device shows the connection problem.

devzone.nordicsemi.com/.../CONNECTION_5F00_PROBLEM.pcapng

[quote user="Edvin Holmseth"]You say that the issue goes away if you delay the peripheral initialization with 5 seconds instead of 1 second, is that correct?[/quote]

yes.

[quote user="Edvin Holmseth"]what IRQ is your app_timer running?[/quote]

Inside the "ble_evt_handler" . Now peripherals_enable() is used to start the timer . Please refer the below code for better clarification.

/**@brief Function for enabling all peripherals.
 *
 * @details This function will be called after 1s in the device connected to the host pc.
 *
 * @param[in]   p_context   Pointer used for passing some arbitrary information (context) from the
 *                          app_start_timer() call to the timeout handler.
 * void peripherals_enable_timeout_handler(void * p_event_data, uint16_t event_size)  
 **/
 
 
static void peripherals_enable_timeout_handler(void * p_context)  
{
     
     ret_code_t err_code;
     
     nrf_gpio_pin_set(BSP_LED_2);       /* Green led will off */
     
     err_code = app_spi_enable();       /* Enabling  2D movement */
     APP_ERROR_CHECK(err_code); 

     motion_3d_module_enable();         /* Enabling  3D movement */ 

     saadc_timer_enable();              /* SAADC timer will enable so the saadc conversion will start */
     
     if (nrf_gpio_pin_read(PIN_BASE_SENSE) == false)   /* Docked Event*/
     {
           DOCKED   = true;
           touchpad_disable();  /* Disable touchpad   */
     }
     else                                              /* Un_docked Event */
     {  
           DOCKED   = false;
           touchpad_enable();  /* Enable touchpad     */
     }


}




/**@brief Function for the Timer initialization.
 *
 * @details Initializes the timer module.
 */
static void peripherals_enable_timer_init(void)
{
        ret_code_t err_code;

        // Create battery timer.
        err_code = app_timer_create(&peripherals_enable_timer_id,
                                    APP_TIMER_MODE_SINGLE_SHOT,
                                    peripherals_enable_timeout_handler);
        APP_ERROR_CHECK(err_code);
}

/** Function for enabling the peripherals_enable timer**/
static void  peripherals_enable(void)
{
    ret_code_t err_code;
    err_code = app_timer_start(peripherals_enable_timer_id, PERIPHERALS_ENABLE_DELAY_INTERVAL, NULL);
    APP_ERROR_CHECK(err_code);   
 
}




/** Function for disabling the peripherals_enable timer **/
static void  peripherals_enable_stop(void)
{
    uint32_t err_code;  
    err_code = app_timer_stop(peripherals_enable_timer_id);
    APP_ERROR_CHECK(err_code); 
 
}

[quote user="Edvin Holmseth"] What is APP_TIMER_CONFIG_IRQ_PRIORITY in your sdk_config.h?[/quote]

APP_TIMER_CONFIG_IRQ_PRIORITY = 6

[quote user="Edvin Holmseth"]Just for testing, can you try something like this:[/quote]

We did the test but same issue was showing . The connection was not establishing with PC.

[quote user="Edvin Holmseth"]So does any of the peripherals you initialize use the priority below 5?[/quote]

No. The peripherals are only using gpio and timer interrupts and both of its priority level is 6.

RE: BLUETOOTH CONNECTION ISSUE

Edvin — Mon, 13 Jul 2020 07:46:45 GMT

I am fine thank you 🙂

I have checked the sniffer trace. I can't see any obvious reasons for why the PC disconnects. Since the PC sends the LL_TERMINATE_IND packet, the connection is not timing out. It should have said that there was a timeout reason if there was something that wasn't replied to, but since it says "Remote User Terminated Connection", that suggests that there is no timeout. However, I checked the usual suspects (5 seconds and 30 seconds before the timeout), and there is nothing that isn't replied to, as far as I can tell.

You say that the issue goes away if you delay the peripheral initialization with 5 seconds instead of 1 second, is that correct?

If you are using an app_timer to trigger this, what IRQ is your app_timer running? What is APP_TIMER_CONFIG_IRQ_PRIORITY in your sdk_config.h?

Just for testing, can you try something like this:

volatile bool m_init_periph = false;


...


static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    switch()
        case BLE_GAP_EVT_CONNECTED:
            NRF_LOG_INFO("connected");
            //peripherals_enable();
            m_init_periph = true;
            ...
            break;
        ...
        
        
}


int main(void)
{
    ...
    
    for(;;)
    {
        if(m_init_periph)
        {
            m_init_periph = false;
            peripherals_enable();
        }
        idle_state_handle();
    }
}

This will move the peripheral initialization to the main context, allowing all other incoming events to interrupt this.

What IRQ are your peripherals running? Is it possible that any of these can delay the softdevice? In S132 interrupt priorities 5, 6 and 7 should be fine to use. 4 is reserved for the softdevice, while 2 and 3 can be used for time critical peripherals, but you should not spend too much time in these interrupts. anything below 1 is off limits.

So does any of the peripherals you initialize use the priority below 5?

RE: BLUETOOTH CONNECTION ISSUE

NANDHU — Sat, 11 Jul 2020 07:36:30 GMT

Hi Edvin,

I am doing well what about you?. Thanks for the quick reply .

RE: BLUETOOTH CONNECTION ISSUE

Edvin — Fri, 10 Jul 2020 16:29:23 GMT

Hello Nandhu,

Hope you are doing fine.

We are very low on capacity due to low staffing because of summer holidays in Norway. I will try to look into this as soon as I can, hopefully in the beginning of next week.