• State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 88 subscribers
  • Views 909 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 281035
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BLE_GATTC_EVT_WRITE_RSP with gatt_status 0x01F2

pieterg

In our BLE connections we often receive a BLE_GATTC_EVT_WRITE_RSP event with gatt_status 0x01F2.

Looking at the list of GATT_STATUS values, this must be an error in the RFU #3 range?

#define BLE_GATT_STATUS_ATTERR_RFU_RANGE3_BEGIN           0x01E0  /**< ATT Error: Reserved for Future Use range #3 begin. */
#define BLE_GATT_STATUS_ATTERR_RFU_RANGE3_END             0x01FC  /**< ATT Error: Reserved for Future Use range #3 end. */

Is there any information about this particular gatt_status 0x01F2 which might help us to investigate this problem?

Parents
  • 0

    Hi,

    Do you have a sniffer log that shows this? https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE

    What devices are the central and peripheral?

  • 0 in reply to Sigurd

    Thanks for your reply.

    The peripheral is an iPhone7 (but I think I've seen it happens with other devices as well, i.e. android phones).

    The central is an nrf52840, in this case the devkit.

    I'll try to make a sniffer log with this situation, have to build a new test setup, because I'll need the devkit as a sniffer device.

  • 0 in reply to pieterg

    Ok,

    pieterg said:

    The peripheral is an iPhone7 (but I think I've seen it happens with other devices as well, i.e. android phones).

    The central is an nrf52840, in this case the devkit.

    Ok, I assume you are calling sd_ble_gattc_write() then, trying to write to some characteristic, or a value to a characteristic, that is not supported by the iPhone.

  • 0 in reply to Sigurd

    Yes indeed, I'm calling sd_ble_gattc_write on the handle of a characteristic value to which writing is allowed. (and in 99.99% of the attempts, writing succeeds)

    However, sometimes this error occurs.

    I'm assuming this is an error on the peripheral side, not the nRF, it's just that I was wondering whether the resulting 0x01f2 would give us any clues to find the cause of the error.

    I've now managed to sniff this situation, it turns out to be an error response with (unknown) error code 0xf2, please find the pcap file attached.

    Do you have any clue what might cause this error?

    1f2.pcapng

Reply
  • 0 in reply to Sigurd

    Yes indeed, I'm calling sd_ble_gattc_write on the handle of a characteristic value to which writing is allowed. (and in 99.99% of the attempts, writing succeeds)

    However, sometimes this error occurs.

    I'm assuming this is an error on the peripheral side, not the nRF, it's just that I was wondering whether the resulting 0x01f2 would give us any clues to find the cause of the error.

    I've now managed to sniff this situation, it turns out to be an error response with (unknown) error code 0xf2, please find the pcap file attached.

    Do you have any clue what might cause this error?

    1f2.pcapng

Children
Related