Nus profile seems to cause system reset if the data length too long.

[Ted]

iphone5_b.psdm370_android6_b.psdlong_write_error.pngI using SDK11. I porting nus profile to my system and make a customer's UUID. I use Lightblue on iPhone 5 to connect my system. I sent a data through my customer's UUID. My system work fine when the data length is less than or equal 20 bytes. It will cause system reset if the data length is great than 20 bytes. Was the softdevice error, or I made something wrong?

[Petter Myhre]

The system is probably reset because APP_ERROR_CHECK() is called with something else than NRF_SUCCESS (0x00000000) somewhere. If you call ble_nus_string_send() with a longer length than 20 bytes it will return NRF_ERROR_INVALID_PARAM.

The maximum ATT MTU with the S130 v2 is 23 bytes, the header is 3 bytes, so up to 20 bytes of data is allowed.

[Ted]

Sorry, I have no good skill with Nordic platform. I follow your instrument to trace the code. I got an event of BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST if the data length is great than 20 bytes. (at APP_ERROR_CHECK)

But if the data length isn't great than 20 bytes I don't receive the event of LE_GATTS_EVT_RW_AUTHORIZE_REQUEST and system work fine.

Could you guide me how to trace it and fix this wrong I made?

static void on_ble_peripheral_evt(ble_evt_t * p_ble_evt)
{
    uint32_t err_code;
    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
...
             break; //BLE_GAP_EVT_CONNECTED
        case BLE_GAP_EVT_DISCONNECTED:
...
            break;//BLE_GAP_EVT_DISCONNECTED
        case BLE_EVT_USER_MEM_REQUEST:
...
            break;//BLE_EVT_USER_MEM_REQUEST
        case BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST:
        {
            ble_gatts_rw_authorize_reply_params_t auth_reply;
            if(p_ble_evt->evt.gatts_evt.params.authorize_request.type
               != BLE_GATTS_AUTHORIZE_TYPE_INVALID)
            {
                if ((p_ble_evt->evt.gatts_evt.params.authorize_request.request.write.op
                     == BLE_GATTS_OP_PREP_WRITE_REQ)
                    || (p_ble_evt->evt.gatts_evt.params.authorize_request.request.write.op
                     == BLE_GATTS_OP_EXEC_WRITE_REQ_NOW)
                    || (p_ble_evt->evt.gatts_evt.params.authorize_request.request.write.op
                     == BLE_GATTS_OP_EXEC_WRITE_REQ_CANCEL))
                {
                    if (p_ble_evt->evt.gatts_evt.params.authorize_request.type
                        == BLE_GATTS_AUTHORIZE_TYPE_WRITE)
                    {
                        auth_reply.type = BLE_GATTS_AUTHORIZE_TYPE_WRITE;
                    }
                    else
                    {
                        auth_reply.type = BLE_GATTS_AUTHORIZE_TYPE_READ;
                    }
                    auth_reply.params.write.gatt_status = APP_FEATURE_NOT_SUPPORTED;
                    err_code = ***sd_ble_gatts_rw_authorize_reply(p_ble_evt->evt.gap_evt.conn_handle,&auth_reply);
                    APP_ERROR_CHECK(err_code);  -->fail at here***
                }
            }
        }break;//BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST
        default:
            // No implementation needed.
            break;
    }
}