RTT repeats output that is meant to be sent only once

RE: RTT repeats output that is meant to be sent only once

muhkuhns — Thu, 07 May 2015 13:47:07 GMT

Looks like

static void on_ble_evt(ble_evt_t * p_ble_evt)
{
    switch (p_ble_evt->header.evt_id)
    {       
        case BLE_GAP_EVT_DISCONNECTED:
            m_conn_handle = BLE_CONN_HANDLE_INVALID;
	    app_timer_stop(m_test_timer_id);
            advertising_start();		<- THIS		
            break;

is causing the reset. Maybe because

static uint32_t device_manager_evt_handler(dm_handle_t const * p_handle,
                                           dm_event_t const  * p_event,
                                           ret_code_t        event_result)
{

    switch(p_event->event_id)
    {
        case DM_EVT_DISCONNECTION:
            m_conn_handle = BLE_CONN_HANDLE_INVALID;
            advertising_start();         <- It is here also.
            break;

But this is both from the example?

If it outcomment one everything works as expected... but which one and why?

When I connect and disconnect from MCP it seems like DM is called before GAP on both actions. (Doesn't matter If I delete bond before or not). Of course I looked them up in the DOC but I don't get why the advertising_start() and also the m_conn_handle = BLE_CONN_HANDLE_INVALID; were duplicated from the beginning?

In the unchanged multilink_peripheral example of course no systemreset is caused. But I only removed the LED stuff... Maybe it now calls the advertising_start()-function too quickly and it is in defect a mistake? I will edit this answer if someone points it out.

RE: RTT repeats output that is meant to be sent only once

muhkuhns — Thu, 07 May 2015 13:09:07 GMT

Thanks for your answer, it helped me a lot finding the problem! See my answer.

RE: RTT repeats output that is meant to be sent only once

Susheel Nuguru — Thu, 07 May 2015 12:43:55 GMT

When you said you tried to debug in the error handler, which error handler did you mean? After Disconnection, it seems that one of your APP_ERROR_CHECK has failed. check component\libraries\util\app_error.c ->app_error_handler

I think RK has explained you once in depth, if my memory serves me well. I would recommend you to overwrite app_error_handler function now so that we can rule out this problem in the future references.