• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 657 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HCI Reference guide not matching operation w/ ATT_ErrorRsp

gary schumacher
Prodigy 225 points

I am seeing some differences between the HCI Reference Guide V 1.2.1 and the operation of the HostTestRelease (1.2.1).  If my host sends an incorrect write command I get a ATT_ErrorRsp command and the guide states that these are not generated on a write command? 

Which is correct?

Is there updated code/documentation and/or an errata document?

  • 0
    TI__Guru 57865 points

    Hi Gary,

    Certain commands will respond with ATT_ErrorRsp, for example GATT_WriteCharValue and GATT_WriteLongCharValue. GATT_WriteNoRsp will not respond with anything.

    What write command do you issue which error code do you get with the ATT_ErrorRsp?

    Best Regards

  • 0 in reply to J Lindh
    Prodigy 225 points

    I was using the GATT_WriteCharValue.  So it sounds like the reference guide needs to be updated as it states "The Write Command does not generate an Error Response".  Thanks

  • 0 in reply to gary schumacher
    TI__Guru 57865 points

    Hi Gary,

    You are correct and we will update the document for the next release.

    Thanks.

  • 0 in reply to J Lindh
    TI__Guru 57865 points

    Actually,

    The TI BLE Vendor Specific HCI Reference Guide document looks ok when it comes to the ATT Write Command. We need to distinguish the difference between the ATT Write Request and the ATT Write Command. The document states that the ATT Write Command does not generate an Error Response, which is a correct statement. It’s only the ATT Write Request that can generate an Error Response. The GATT_WriteCharValue maps to the ATT Write Request (and not the Command), which generates an Error Response when something is wrong with the request itself.

    Best Regards