BLE + ADC + Timer

RE: BLE + ADC + Timer

Petter Myhre — Fri, 06 Jan 2017 09:18:06 GMT

The potential error codes are listed in the API documentation, see for example sd_ble_gatts_hvx(). See the definition of these to see the value.

RE: BLE + ADC + Timer

IlyaM — Thu, 05 Jan 2017 18:19:18 GMT

Thank you! Could you tell me where can I find all descriptions of error codes like this?

RE: BLE + ADC + Timer

Petter Myhre — Thu, 05 Jan 2017 14:12:42 GMT

13313 = 0x3401 = BLE_ERROR_GATTS_SYS_ATTR_MISSING which is probably returned from sd_ble_gatts_hvx() inside ble_hts_measurement_send().

See this for how to handle it. This MSC may also be of interest.

RE: BLE + ADC + Timer

IlyaM — Thu, 05 Jan 2017 13:57:07 GMT

yes, I put breakpoint and got error:

error_code: 13313
in this code

if (!m_hts_meas_ind_conf_pending)
    {
        hts_sim_measurement(&simulated_meas, value);
        NRF_LOG_INFO("hts_sim_measurement\r\n");
        err_code = ble_hts_measurement_send(&m_hts, &simulated_meas);

        switch (err_code)
        {
            case NRF_SUCCESS:
                // Measurement was successfully sent, wait for confirmation.
                NRF_LOG_INFO("Measurement was successfully sent, wait for confirmation.\r\n");
                m_hts_meas_ind_conf_pending = true;
                break;

            case NRF_ERROR_INVALID_STATE:
                // Ignore error.
                NRF_LOG_INFO("Measurement has invalid state.\r\n");
                break;

            default:
                **APP_ERROR_HANDLER(err_code);**
                break;
        }
    }

highlighted the error with **

It seems to me I fixed this error.

I use adc to measure the temperature and I have a variable which has boolean values isConnected. I set true in this case

case BLE_GAP_EVT_CONNECTED:
isConnected = true;

And every time when my data from adc is ready I check this variable, if it's true, I send the new value.

I guess I would send it before my services are initiated, and this error has come. I remove setting the value from line above and set it in this line

case BLE_HTS_EVT_INDICATION_ENABLED:
isConnected = true;

And now it works!

RE: BLE + ADC + Timer

Petter Myhre — Mon, 02 Jan 2017 07:58:16 GMT

Ok. Have you been able to put a breakpoint in app_error_handler()? What is the line number, file name and error code?

RE: BLE + ADC + Timer

IlyaM — Fri, 30 Dec 2016 11:00:53 GMT

I changed adc interrupt priority to 3 (the lowest priority) and It didn't help, if I connect to ble in the same time when adc handler is activated I get error, if I connect earlier or later then adc is activated then everything is ok. I thought softdevice has the highest priority

RE: BLE + ADC + Timer

Petter Myhre — Fri, 30 Dec 2016 09:35:29 GMT

I see that you are using interrupt priority 0, this is reserved for the SoftDevice and shouldn't used. The application can use interrupt priority 1 or 3.

RE: BLE + ADC + Timer

IlyaM — Thu, 29 Dec 2016 14:56:37 GMT

it returns NRF_SUCCESS and I see the value of conversion

It seems adc interrupt correlates with BLE interrupts, cause when I increased the timer and connected to ble device before my adc handler interrupted I got working device

RE: BLE + ADC + Timer

Petter Myhre — Thu, 29 Dec 2016 14:22:47 GMT

What does nrf_drv_adc_buffer_convert() return? NRF_SUCCESS (0x00000000)? Or an error? (PS. When using the SoftDevice you can use sd_app_evt_wait() instead of

    __SEV();
    __WFE();
    __WFE();

RE: BLE + ADC + Timer

IlyaM — Thu, 29 Dec 2016 14:07:24 GMT

I found the problem with this block

static void lmt70_timeout_handler(void * p_context)
{
    UNUSED_PARAMETER(p_context);
    NRF_LOG_INFO("lmt70_timeout_handler\r\n");
    /*APP_ERROR_CHECK(nrf_drv_adc_buffer_convert(adc_buffer, ADC_BUFFER_SIZE));
    for (uint32_t i = 0; i < ADC_BUFFER_SIZE; i++)
    {
        // manually trigger ADC conversion
        nrf_drv_adc_sample();
        // enter into sleep mode
        __SEV();
        __WFE();
        __WFE();
        nrf_delay_ms(100);
        NRF_LOG_FLUSH();
    }*/
}

If I leave this code commented, ble and timer work fine, if I remove comments I get this problem which described above.

my ADC is:

ret_code_t ret_code;
    nrf_drv_adc_config_t config = NRF_DRV_ADC_DEFAULT_CONFIG;
    config.interrupt_priority = 0;

    ret_code = nrf_drv_adc_init(&config, lmt70_event_handler);
    APP_ERROR_CHECK(ret_code);

    channel1.config.config.input = NRF_ADC_CONFIG_SCALING_INPUT_FULL_SCALE;
    channel1.config.config.resolution = NRF_ADC_CONFIG_RES_10BIT;
    channel1.config.config.reference = NRF_ADC_CONFIG_REF_VBG;

    nrf_drv_adc_channel_enable(&channel1);
    timer_init();

RE: BLE + ADC + Timer

Petter Myhre — Thu, 29 Dec 2016 12:17:04 GMT

Not app_error_save_and_stop(), but app_error_handler():

void app_error_handler(ret_code_t error_code, uint32_t line_num, const uint8_t * p_file_name)
{
    error_info_t error_info =
    {
        .line_num    = line_num,
        .p_file_name = p_file_name,
        .err_code    = error_code,
    };
    app_error_fault_handler(NRF_FAULT_ID_SDK_ERROR, 0, (uint32_t)(&error_info));

    UNUSED_VARIABLE(error_info);
}

RE: BLE + ADC + Timer

IlyaM — Wed, 28 Dec 2016 14:28:21 GMT

I use 12.2.0

what I got via gdb

(gdb) bt
#0  0x0001bd6a in app_error_save_and_stop (id=1, pc=63332, info=0)
    at /Users/im/Dropbox/nRF51822/Unzipped/SDK/12.2.0/components/libraries/util/app_error.c:113
#1  0x0001bdaa in app_error_fault_handler (id=1, pc=63332, info=0)
    at /Users/im/Dropbox/nRF51822/Unzipped/SDK/12.2.0/components/libraries/util/app_error_weak.c:32
#2  0x000299c8 in softdevice_fault_handler (id=1, pc=63332, info=0)
    at /Users/im/Dropbox/nRF51822/Unzipped/SDK/12.2.0/components/softdevice/common/softdevice_handler/softdevice_handler.c:90
#3  <signal handler called>
#4  0x0000f766 in ?? ()
#5  0x0000f71c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

RE: BLE + ADC + Timer

Petter Myhre — Wed, 28 Dec 2016 14:18:49 GMT

What SDK are you using? If you define DEBUG and put a breakpoint in app_error_handler(), what is the line number, file name and error code? You should turn of optimizations.