Last BLE_GATTC_EVT_WRITE_RSP does not contain handle

[hathach]

Hi,

I am working on with nrf52 with SD132 v2 SDK11 since we need serial bootloader.

I tried a gattc long write sequence to write 22 bytes. Everything works well, peer got data and response correctly. However, the last BLE_GATTC_EVT_WRITE_RSP for BLE_GATT_OP_EXEC_WRITE_REQ does not contain the characteristic's handle in ble_gattc_evt_write_rsp_t like those responses for BLE_GATT_OP_PREP_WRITE_REQ. Is this a bug in SD v2 or I misunderstand the flowchart ??

here is my write sequence

1. op = BLE_GATT_OP_PREP_WRITE_REQ, offset = 0, len =18, handle = 37

   --> [BLE_GATTC_EVT_WRITE_RSP] handle = 37 ( op = BLE_GATT_OP_PREP_WRITE_REQ)

2. op = BLE_GATT_OP_PREP_WRITE_REQ, offset = 18, len =4, handle = 37

   --> [BLE_GATTC_EVT_WRITE_RSP] handle = 37 ( op = BLE_GATT_OP_PREP_WRITE_REQ)

3. op = BLE_GATT_OP_EXEC_WRITE_REQ, flag = BLE_GATT_EXEC_WRITE_FLAG_PREPARED_WRITE, offset = len = 0, handle = 37

   --> [BLE_GATTC_EVT_WRITE_RSP] handle = 0 ?? ( op = BLE_GATT_OP_EXEC_WRITE_REQ)

[bjorn-spockeli]

FYI: The lastest SDK v13.0.0 added support for Secure Serial DFU, I do recommend switching to the latest SDK if the only reason for choosing SDk v11.0.0 was serial DFU. Could you provide a link to the flow chart you're referring to?

[hathach]

in sdk 13, it is still listed under experimental. We will wait until it is more stable. The flow chart is what I got when submitting an long write. You should be able to reproduce it if writing > 20 byte data with gattc. The above example write 22 bytes.