Connecting a peripheral device to a central device

RE: Connecting a peripheral device to a central device

Jimmy — Mon, 28 Nov 2016 15:21:59 GMT

Ok, thanks I solved the problem with the error. It was because I had the wrong UUID placed for the RX characterisitics, but I changed it and the central is successfully connected to the peripheral device.

RE: Connecting a peripheral device to a central device

Sigurd — Thu, 24 Nov 2016 10:30:04 GMT

The function that is giving the error is ble_nus_c_rx_notif_enable() at line 207.

The two devices are connected, but this function tries to request the peripheral to start sending notification of RX characteristic. But the central has not discovered the NUS_RX_CHARACTERISTIC on the peripheral, and the function will return with NRF_ERROR_INVALID_STATE.

What kind of code are you running on the DELTA device?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 17:34:46 GMT

So no the error code is not 579 now.

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 17:03:07 GMT

Hi Sigurd, in the p_error_info, the error code is 0x00000008. The line num is 0x000000D0. The p_filename is 0x00020880 now. The NRF_FALUT_ID_SDK_ERROR is 0x00004001. Is that helpful?

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 16:04:57 GMT

But the error_code is still 579?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 16:03:56 GMT

Also, the NRF_FAULT_ID_SDK_ERROR within the app_error_handler method is 0x00004001

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 15:59:47 GMT

Actually, for the m_error_data struct the err_info is 0x00000000, the pc is 0x0001089E, and the fault ID is 0x00000001. I will check app_error_handler.

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 15:55:26 GMT

579 is not a valid error code. However, I'm not sure why it would get "corrupted". Is the err_code also 579 in the m_error_data struct and in the app_error_handler scope?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 15:42:50 GMT

The value of line_num is 0x0400. The p_file_name is 0x000008E5 . The error code is 0x00000579. Is that good?

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 15:40:20 GMT

In the p_error_info struct, you have line_num,p_file_name and err_code. What are the values of these 3?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 15:33:10 GMT

Hi Sigurd, I got the error code. Based off the m_error data the fault_id is 0x00000001. Also, the err_code from the p_error info is 0x00000579. Is that what you wanted?

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 15:16:56 GMT

Add the breakpoint at line 113( at while (loop); ) in app_error.c. Remeber to add DEBUG as a define in the C/C++ tab. Set the optimization to 0 in the C/C++ tab.

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 15:15:59 GMT

Actually please ignore my last comment. I found the error location, but it does not let me add a breakpoint here?

// The following variable helps Keil keep the call stack visible, in addition, it can be set to
// 0 in the debugger to continue executing code after the error check.
volatile bool loop = true;
UNUSED_VARIABLE(loop);

m_error_data.fault_id   = id;
m_error_data.pc         = pc;
m_error_data.error_info = info;

switch (id)
{
    case NRF_FAULT_ID_SDK_ASSERT:
        m_error_data.p_assert_info = (assert_info_t *)info;
        m_error_data.line_num      = m_error_data.p_assert_info->line_num;
        m_error_data.p_file_name   = m_error_data.p_assert_info->p_file_name;
        break;

    case NRF_FAULT_ID_SDK_ERROR:
        m_error_data.p_error_info = (error_info_t *)info;
        m_error_data.err_code     = m_error_data.p_error_info->err_code;
        m_error_data.line_num     = m_error_data.p_error_info->line_num;
        m_error_data.p_file_name  = m_error_data.p_error_info->p_file_name;
        break;
}

UNUSED_VARIABLE(m_error_data);

// If printing is disrupted, remove the irq calls, or set the loop variable to 0 in the debugger.
__disable_irq();
while (loop);

__enable_irq();

}

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 14:51:15 GMT

Where you able to read the err_code ?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 14:45:30 GMT

I am using softdevice 132 and the SDK version is nRF5_SDK_12.1.0_0d23e2a. So when I first started debugging, it placed a break point through (is_uuid_present(&m_nus_uuid, p_adv_report)). Then after that when stepping through, it goes to the method, is_uuid_present and successfully matches the UUID. However, I though that it would go through the BLE_GAP_EVT_CONNNECTED which is when the NRF52 board would be solid, but it is just blinking every 4 seconds and displaying the loop.

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 14:34:48 GMT

What you mean by "softdevice part"? What SDK version and SoftDevice version are you using?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 14:33:09 GMT

I have been trying to debug for a while by following the guide and the while debugging and stepping through it skips through the softdevice part, do you think wrong version of softdevice could cause this?

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 14:14:40 GMT

Try to read the error code. Follow this guide on how to debug and read the error code.

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 14:04:23 GMT

Also, I don't think the code is going through case BLE_GAP_EVT_CONNECTED:. Do you think that could be a reason? Should I keep the scan parameters m_scan_params as well?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 13:45:14 GMT

This is the nrf52 developer kit and is not a custom board. What do you think I should do? It gives me this

Connecting to target 98fa6b00e1d9 Uart_c Scan started Connecting to target 98fa6b00e1d9 Uart_c Scan started Connecting to target 98fa6b00e1d9 Uart_c Scan started

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 13:39:08 GMT

That means that the device is restarting. This happens because the function APP_ERROR_CHECK() has registered an error in err_code. Is this a custom board or the nRF52-DK ?

RE: Connecting a peripheral device to a central device

Jimmy — Wed, 23 Nov 2016 13:34:28 GMT

Yes it is printing UART c scan started also. Does that mean anything? There is a loop that continues with those two messages I mentioned.

RE: Connecting a peripheral device to a central device

Sigurd — Wed, 23 Nov 2016 08:28:12 GMT

It keeps printing only “Connected to target” ? Is it printing “Uart_c Scan started” also ?

RE: Connecting a peripheral device to a central device

Jimmy — Tue, 22 Nov 2016 22:35:38 GMT

Hi Sigurd, thank you it is connected. However, it keeps printing connecting to target in my terminal called Termite and did not go through this case listed below. What should I do?

case BLE_GAP_EVT_CONNECTED: //NRF_LOG_DEBUG("Connected to target\r\n"); err_code = bsp_indication_set(BSP_INDICATE_CONNECTED); APP_ERROR_CHECK(err_code);

RE: Connecting a peripheral device to a central device

Sigurd — Tue, 22 Nov 2016 09:51:25 GMT

The BLE_UUID_NUS_SERVICE is 0x0001. The NUS_SERVICE_UUID_TYPE is a BLE_UUID_TYPE_VENDOR_BEGIN, this is defined in ble_types.h as 0x02. I don’t believe you need to change the is_uuid_present(), the UUID gets decoded from the advertising data using the sd_ble_uuid_decode().

Also, If the goal is just to connect the devices, and you know what the extracted_uuid is, just add this as the target_uuid, and the central will connect to the device.