getting gatts value with nRF51822

RE: getting gatts value with nRF51822

Pål Håland — Fri, 18 Dec 2015 10:06:27 GMT

Yes, updated the answer with pointer declaration

RE: getting gatts value with nRF51822

Maz Shar — Fri, 18 Dec 2015 09:58:14 GMT

p_data definition should be like this right?

uint8_t * p_data = p_ble_evt->evt.gatts_evt.params.write.data;

RE: getting gatts value with nRF51822

Pål Håland — Thu, 09 Jan 2014 08:29:02 GMT

Hi Morgan,

I'm not completely sure of why the chip resets, but it could be because of an assert returned from the stack.

Instead of resetting the chip in the assert handler, could you place a breakpoint there and provide information about file and line number where it is failing?

One of the reasons it could assert is if you do a lot of processing inside the event interrupt, this would be processed in high priority interrupt, and when the stack receive an interrupt it won't start that one until the processing of the application is done. The best thing is to do is calling the sd_ble_evt_get() in the main context of the application, and only read out events when you have one ready. (like setting a flag in the event interrupt) when there is no event available and no processing to be done you put your application to sleep.

BR Pål

RE: getting gatts value with nRF51822

Morgan Redfield — Wed, 08 Jan 2014 18:38:55 GMT

Hi Pal,

I made a service called ble_hex for my application, which is based around the battery measurement service. So ble_hex_evt_t and ble_hex_t are very similar to ble_bas_evt_t and ble_bas_t.

Thanks for your input about getting the value when receiving the ble_evt_t. I'll switch to that method of doing things.

I'm still wondering why the sd_ble_gatts_value_get() call was causing a crash. Any ideas about that?

RE: getting gatts value with nRF51822

Pål Håland — Wed, 08 Jan 2014 08:10:02 GMT

Hi Morgan,

I don't know what the ble_hex_evt_t and ble_hex_t is.

The best way to get the data from the write event is doing this when receiving the ble_evt_t

switch (p_ble_evt->header.evt_id)
{
    case BLE_GATTS_EVT_WRITE:
        {
            uint8_t * p_data = p_ble_evt->evt.gatts_evt.params.write.data;
            uint16_t length = p_ble_evt->evt.gatts_evt.params.write.len;

            new_hex_status = p_data[0];
        }
        break;
    default:
        break;
}

Update 18.12.2015: Added pointer declaration to the p_data