Issue about BLE_APP_UART and APP_TIMER

RE: Issue about BLE_APP_UART and APP_TIMER

davidz — Sun, 28 Jun 2020 21:38:07 GMT

Thank you Sigurd. I have solved the problem by moving the sensor data transmit to the main loop. It seems that the APP_timer interrupt does not work well with my sensor, which uses SPI bus to interface with the nrf52840.

RE: Issue about BLE_APP_UART and APP_TIMER

Sigurd — Fri, 26 Jun 2020 14:32:46 GMT

[quote user="davidz"]ERROR 13313 [/quote]

13313 is the same as BLE_ERROR_GATTS_SYS_ATTR_MISSING. You can read about this error code e.g. in this post

RE: Issue about BLE_APP_UART and APP_TIMER

davidz — Thu, 18 Jun 2020 21:15:55 GMT

Thanks. Here is the output "<error> app: ERROR 13313 [Unknown error code] at D:\nrf5sdk1600\workspace\test0\ble_app_uart\main.c:126
PC at: 0x0002FB77". It happened at the sensor_meas_timeout_handler(). Line 126 is where the program stopped. I actually used "NRF_LOG_INFO("Error code is %d\r\n",err_code);" to find out the error code before. I have a question: does ble_nus_data_send() function need to wait for something else after the BLE connection is re-established? It looks like the ble_nus_data_send() function caused the problem after the re-connection.

static void sensor_meas_timeout_handler(void * p_context)
{
UNUSED_PARAMETER(p_context);

static uint8_t data_array[BLE_NUS_MAX_DATA_LEN];
uint32_t err_code;
uint16_t length = 4;
static int i=0;
if(m_conn_handle!=BLE_CONN_HANDLE_INVALID)
{
i++;
data_array[0]=i;
data_array[1]=i+1;
data_array[2]=i+2;
data_array[3]=i+3;
err_code = ble_nus_data_send(&m_nus, data_array, &length, m_conn_handle);
if ((err_code != NRF_ERROR_INVALID_STATE) &&
(err_code != NRF_ERROR_RESOURCES) &&
(err_code != NRF_ERROR_NOT_FOUND))
{
APP_ERROR_CHECK(err_code); // Line 126
// NRF_LOG_INFO("Error code is %d\r\n",err_code);
}
else NRF_LOG_INFO("Sending out data %dth time. connection handle %d\r\n",i,m_conn_handle);

}
}

RE: Issue about BLE_APP_UART and APP_TIMER

Sigurd — Thu, 18 Jun 2020 13:39:40 GMT

Try to set your project to Debug configuration, if you are using SES, you can do it like this:

In sdk_config.h, make sure that these defines have these values:

NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0
NRF_LOG_BACKEND_RTT_ENABLED 1
NRF_LOG_ENABLED 1

In app_error_weak.c,

add NRF_LOG_FLUSH(); above NRF_BREAKPOINT_COND;

The error-code, filename and line-number should then be printed in the SES Debug Terminal.

RE: Issue about BLE_APP_UART and APP_TIMER

davidz — Thu, 18 Jun 2020 03:42:57 GMT

The NRF Connect desktop shows the error "Disconnected from device E4:A6:2D:DE:55:B3, reason: BLE_HCI_CONNECTION_TIMEOUT". The nRF52840 DK shows the error "void app_error_fault_handler(unsigned int id=0x00004001, unsigned int pc=0x0002fb6b, unsinged int info=0x200:0x00028D30", and "void app_error_handler(unsigned int error_code=0x00000000, unsigned int line_num=0x20002bec, const unint8_t*|0x00028BFA"

RE: Issue about BLE_APP_UART and APP_TIMER

Sigurd — Wed, 17 Jun 2020 15:00:23 GMT

Hi,

[quote userid="91194" url="~/f/nordic-q-a/62679/issue-about-ble_app_uart-and-app_timer"]After the NRF connect desktop disconnects and reconnects, it connects for a brief time and then disconnects. The NRF52840 DK runs into error. [/quote]

What disconnect reason did you get?

What error did you run into on the nRF52840 DK?